Re: The project website
AFAICT Commons no longer uses CMS to build, so nothing needs to be done. Sebb. On Wed, 6 Jan 2021 at 12:51, Andrew Wetmore wrote: > > > Hi, and happy New Year. > > Checking in on the migration of your project website from the Apache CMS to a > different tech. Has there been progress? Have you opened a Jira ticket to > track it? Is there anything Infra can help with? > > A > > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: The project website
Hi, and happy New Year. Checking in on the migration of your project website from the Apache CMS to a different tech. Has there been progress? Have you opened a Jira ticket to track it? Is there anything Infra can help with? A Andrew Wetmore Technical Writer-Editor Infra *Apache Software Foundation* andr...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: The project website
The main Commons site does not need any special processing. It just needs a script to run Maven and publish the generated site. Can we use svnpubsub, Maven and Buildbot? If so, is there any info on how to set up Buildbot? Buildbot is mentioned in the Pelican+Buildbot page, but there are no details on how to set it up. I think that would be the least work overall. On Mon, 17 Aug 2020 at 13:15, Andrew Wetmore wrote: > Hi: > > I am glad to see the project is moving forward with migration from the > CMS. Do you have a formal PMC agreement on the move, and have you opened a > Jira ticket for INFRA so we can track what we need to do? > > Thanks! > > Andrew > > On Tue, Aug 4, 2020 at 10:40 AM Andrew Wetmore wrote: > >> Hi: >> >> I am part of the Infrastructure team, and am writing to ask whether your >> project is still using the Apache CMS for your project website. As you >> know, the CMS is reaching end-of-life, and we need projects to move their >> websites onto a different option within the next few weeks. >> >> There are several alternatives available, including those listed on this >> page [1] on managing project websites. Infra is assembling a Wiki page [2] >> on migrating a website from the CMS, and is looking forward to helping >> projects with this transition. >> >> Please let me know whether your site is still on the Apache CMS and, if >> so, who will be the project point-of-contact with Infra for the migration. >> >> Thank you! >> >> >> >> >> [1] https://infra.apache.org/project-site.html >> >> [2] >> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS >> >> >> -- >> Andrew Wetmore >> Technical Writer-Editor >> Infra >> *Apache Software Foundation* >> andr...@apache.org >> >> >> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >> <#m_-8976911250694450596_m_-8370763572039288743_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> > > > -- > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org >
Re: The project website
The main commons site does not need any special processing. It just needs a script to run maven and publish the generated site. What is the Infra-recommended replacement for such sites? On Mon, 17 Aug 2020 at 14:05, Gary Gregory wrote: > > Hi Andrew, > > There is no formal agreement from the PMC but it feels to me (with my > PMC hat on) that we can move forward since the underlying tool is coming to > EOL. > > My components in Commons have their own Maven generated site they upload > directly. > > We just need someone to step up and the main site. > > Gary > > > > On Mon, Aug 17, 2020 at 8:15 AM Andrew Wetmore wrote: > > > Hi: > > > > I am glad to see the project is moving forward with migration from the CMS. > > Do you have a formal PMC agreement on the move, and have you opened a Jira > > ticket for INFRA so we can track what we need to do? > > > > Thanks! > > > > Andrew > > > > On Tue, Aug 4, 2020 at 10:40 AM Andrew Wetmore wrote: > > > > > Hi: > > > > > > I am part of the Infrastructure team, and am writing to ask whether your > > > project is still using the Apache CMS for your project website. As you > > > know, the CMS is reaching end-of-life, and we need projects to move their > > > websites onto a different option within the next few weeks. > > > > > > There are several alternatives available, including those listed on this > > > page [1] on managing project websites. Infra is assembling a Wiki page > > [2] > > > on migrating a website from the CMS, and is looking forward to helping > > > projects with this transition. > > > > > > Please let me know whether your site is still on the Apache CMS and, if > > > so, who will be the project point-of-contact with Infra for the > > migration. > > > > > > Thank you! > > > > > > > > > > > > > > > [1] https://infra.apache.org/project-site.html > > > > > > [2] > > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > > > > -- > > > Andrew Wetmore > > > Technical Writer-Editor > > > Infra > > > *Apache Software Foundation* > > > andr...@apache.org > > > > > > > > > < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > > Virus-free. > > > www.avast.com > > > < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > > <#m_-8370763572039288743_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > > > > > > -- > > Andrew Wetmore > > Technical Writer-Editor > > Infra > > *Apache Software Foundation* > > andr...@apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: The project website
Hi Andrew, There is no formal agreement from the PMC but it feels to me (with my PMC hat on) that we can move forward since the underlying tool is coming to EOL. My components in Commons have their own Maven generated site they upload directly. We just need someone to step up and the main site. Gary On Mon, Aug 17, 2020 at 8:15 AM Andrew Wetmore wrote: > Hi: > > I am glad to see the project is moving forward with migration from the CMS. > Do you have a formal PMC agreement on the move, and have you opened a Jira > ticket for INFRA so we can track what we need to do? > > Thanks! > > Andrew > > On Tue, Aug 4, 2020 at 10:40 AM Andrew Wetmore wrote: > > > Hi: > > > > I am part of the Infrastructure team, and am writing to ask whether your > > project is still using the Apache CMS for your project website. As you > > know, the CMS is reaching end-of-life, and we need projects to move their > > websites onto a different option within the next few weeks. > > > > There are several alternatives available, including those listed on this > > page [1] on managing project websites. Infra is assembling a Wiki page > [2] > > on migrating a website from the CMS, and is looking forward to helping > > projects with this transition. > > > > Please let me know whether your site is still on the Apache CMS and, if > > so, who will be the project point-of-contact with Infra for the > migration. > > > > Thank you! > > > > > > > > > > [1] https://infra.apache.org/project-site.html > > > > [2] > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > -- > > Andrew Wetmore > > Technical Writer-Editor > > Infra > > *Apache Software Foundation* > > andr...@apache.org > > > > > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > > www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > <#m_-8370763572039288743_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > > -- > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org >
Re: The project website
Hi: I am glad to see the project is moving forward with migration from the CMS. Do you have a formal PMC agreement on the move, and have you opened a Jira ticket for INFRA so we can track what we need to do? Thanks! Andrew On Tue, Aug 4, 2020 at 10:40 AM Andrew Wetmore wrote: > Hi: > > I am part of the Infrastructure team, and am writing to ask whether your > project is still using the Apache CMS for your project website. As you > know, the CMS is reaching end-of-life, and we need projects to move their > websites onto a different option within the next few weeks. > > There are several alternatives available, including those listed on this > page [1] on managing project websites. Infra is assembling a Wiki page [2] > on migrating a website from the CMS, and is looking forward to helping > projects with this transition. > > Please let me know whether your site is still on the Apache CMS and, if > so, who will be the project point-of-contact with Infra for the migration. > > Thank you! > > > > > [1] https://infra.apache.org/project-site.html > > [2] > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > -- > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_-8370763572039288743_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Andrew Wetmore Technical Writer-Editor Infra *Apache Software Foundation* andr...@apache.org
Re: Your project website
On Wed, 5 Aug 2020 at 19:45, Gary Gregory wrote: > > The only site under CMS is the Commons site, not each site generated by RMs > for each component. Also AFAICT Commons site does not use any of the CMS special features, so it at most needs a script to build and publish it. > Gary > > On Wed, Aug 5, 2020, 12:23 Rob Tompkins wrote: > > > Does this apply to Commons as well? If so we have a considerable amount of > > work to accomplish in a very little amount of time. > > > > -Rob > > > > > Begin forwarded message: > > > > > > From: Ralph Goers > > > Subject: Re: Your project website > > > Date: August 5, 2020 at 12:09:49 PM EDT > > > To: d...@logging.apache.org > > > Reply-To: d...@logging.apache.org > > > > > > Yes, the main landing pages are all in the CMS. I was always under the > > impression that even the Maven generated projects are considered to be part > > of the CMS since it provides a way to link to them via the external > > definitions and they have to be published to a specific location in svn. > > > > > > This is the first time I have heard that the CMS was reaching > > end-of-life. Giving us a couple of weeks to move to something else is > > unrealistic. > > > > > > Ralph > > > > > >> On Aug 5, 2020, at 7:36 AM, Matt Sicker wrote: > > >> > > >> From what I can tell, we have a few pages that use the CMS on > > >> logging.apache.org, though most of the site is generated from Maven > > >> and committed to Subversion. > > >> > > >> For the root site, I'd imagine we can migrate to Pelican or whatever. > > >> This could be an opportunity to switch over to Git for publishing the > > >> site (which might take less time to upload), too, but I think that's > > >> unrelated. > > >> > > >> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote: > > >>> > > >>> Hi: > > >>> > > >>> I am part of the Infrastructure team, and am writing to ask whether > > your > > >>> project is still using the Apache CMS for your project website. As you > > >>> know, the CMS is reaching end-of-life, and we need projects to move > > their > > >>> websites onto a different option within the next few weeks. > > >>> > > >>> There are several alternatives available, including those listed on > > this > > >>> page [1] on managing project websites. Infra is assembling a Wiki page > > [2] > > >>> on migrating a website from the CMS, and is looking forward to helping > > >>> projects with this transition. > > >>> > > >>> Please let me know whether your site is still on the Apache CMS and, > > if so, > > >>> who will be the project point-of-contact with Infra for the migration. > > >>> > > >>> Thank you! > > >>> > > >>> > > >>> > > >>> > > >>> [1] https://infra.apache.org/project-site.html > > >>> > > >>> [2] > > >>> > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > >>> > > >>> > > >>> > > >>> -- > > >>> Andrew Wetmore > > >>> Technical Writer-Editor > > >>> Infra > > >>> *Apache Software Foundation* > > >>> andr...@apache.org > > >>> > > >>> < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > >>> Virus-free. > > >>> www.avast.com > > >>> < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > >> > > >> > > >> > > >> -- > > >> Matt Sicker > > >> > > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Your project website
The only site under CMS is the Commons site, not each site generated by RMs for each component. Gary On Wed, Aug 5, 2020, 12:23 Rob Tompkins wrote: > Does this apply to Commons as well? If so we have a considerable amount of > work to accomplish in a very little amount of time. > > -Rob > > > Begin forwarded message: > > > > From: Ralph Goers > > Subject: Re: Your project website > > Date: August 5, 2020 at 12:09:49 PM EDT > > To: d...@logging.apache.org > > Reply-To: d...@logging.apache.org > > > > Yes, the main landing pages are all in the CMS. I was always under the > impression that even the Maven generated projects are considered to be part > of the CMS since it provides a way to link to them via the external > definitions and they have to be published to a specific location in svn. > > > > This is the first time I have heard that the CMS was reaching > end-of-life. Giving us a couple of weeks to move to something else is > unrealistic. > > > > Ralph > > > >> On Aug 5, 2020, at 7:36 AM, Matt Sicker wrote: > >> > >> From what I can tell, we have a few pages that use the CMS on > >> logging.apache.org, though most of the site is generated from Maven > >> and committed to Subversion. > >> > >> For the root site, I'd imagine we can migrate to Pelican or whatever. > >> This could be an opportunity to switch over to Git for publishing the > >> site (which might take less time to upload), too, but I think that's > >> unrelated. > >> > >> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote: > >>> > >>> Hi: > >>> > >>> I am part of the Infrastructure team, and am writing to ask whether > your > >>> project is still using the Apache CMS for your project website. As you > >>> know, the CMS is reaching end-of-life, and we need projects to move > their > >>> websites onto a different option within the next few weeks. > >>> > >>> There are several alternatives available, including those listed on > this > >>> page [1] on managing project websites. Infra is assembling a Wiki page > [2] > >>> on migrating a website from the CMS, and is looking forward to helping > >>> projects with this transition. > >>> > >>> Please let me know whether your site is still on the Apache CMS and, > if so, > >>> who will be the project point-of-contact with Infra for the migration. > >>> > >>> Thank you! > >>> > >>> > >>> > >>> > >>> [1] https://infra.apache.org/project-site.html > >>> > >>> [2] > >>> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > >>> > >>> > >>> > >>> -- > >>> Andrew Wetmore > >>> Technical Writer-Editor > >>> Infra > >>> *Apache Software Foundation* > >>> andr...@apache.org > >>> > >>> < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > >>> Virus-free. > >>> www.avast.com > >>> < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >> > >> > >> > >> -- > >> Matt Sicker > >> > > > > > >
Re: Your project website
> On Aug 5, 2020, at 12:30 PM, Matt Sicker wrote: > > The CMS is the transformation system itself from my understanding. I > don't believe svnpubsub is being deprecated here. Our landing page > templates may need to be converted, but that's about it. Thanks Matt for that clarification. -Rob > > On Wed, 5 Aug 2020 at 11:10, Ralph Goers wrote: >> >> Yes, the main landing pages are all in the CMS. I was always under the >> impression that even the Maven generated projects are considered to be part >> of the CMS since it provides a way to link to them via the external >> definitions and they have to be published to a specific location in svn. >> >> This is the first time I have heard that the CMS was reaching end-of-life. >> Giving us a couple of weeks to move to something else is unrealistic. >> >> Ralph >> >>> On Aug 5, 2020, at 7:36 AM, Matt Sicker wrote: >>> >>> From what I can tell, we have a few pages that use the CMS on >>> logging.apache.org, though most of the site is generated from Maven >>> and committed to Subversion. >>> >>> For the root site, I'd imagine we can migrate to Pelican or whatever. >>> This could be an opportunity to switch over to Git for publishing the >>> site (which might take less time to upload), too, but I think that's >>> unrelated. >>> >>> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote: >>>> >>>> Hi: >>>> >>>> I am part of the Infrastructure team, and am writing to ask whether your >>>> project is still using the Apache CMS for your project website. As you >>>> know, the CMS is reaching end-of-life, and we need projects to move their >>>> websites onto a different option within the next few weeks. >>>> >>>> There are several alternatives available, including those listed on this >>>> page [1] on managing project websites. Infra is assembling a Wiki page [2] >>>> on migrating a website from the CMS, and is looking forward to helping >>>> projects with this transition. >>>> >>>> Please let me know whether your site is still on the Apache CMS and, if so, >>>> who will be the project point-of-contact with Infra for the migration. >>>> >>>> Thank you! >>>> >>>> >>>> >>>> >>>> [1] https://infra.apache.org/project-site.html >>>> >>>> [2] >>>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS >>>> >>>> >>>> >>>> -- >>>> Andrew Wetmore >>>> Technical Writer-Editor >>>> Infra >>>> *Apache Software Foundation* >>>> andr...@apache.org >>>> >>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>>> Virus-free. >>>> www.avast.com >>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> >>> >>> -- >>> Matt Sicker >>> >> >> > > > -- > Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Fwd: Your project website
Does this apply to Commons as well? If so we have a considerable amount of work to accomplish in a very little amount of time. -Rob > Begin forwarded message: > > From: Ralph Goers > Subject: Re: Your project website > Date: August 5, 2020 at 12:09:49 PM EDT > To: d...@logging.apache.org > Reply-To: d...@logging.apache.org > > Yes, the main landing pages are all in the CMS. I was always under the > impression that even the Maven generated projects are considered to be part > of the CMS since it provides a way to link to them via the external > definitions and they have to be published to a specific location in svn. > > This is the first time I have heard that the CMS was reaching end-of-life. > Giving us a couple of weeks to move to something else is unrealistic. > > Ralph > >> On Aug 5, 2020, at 7:36 AM, Matt Sicker wrote: >> >> From what I can tell, we have a few pages that use the CMS on >> logging.apache.org, though most of the site is generated from Maven >> and committed to Subversion. >> >> For the root site, I'd imagine we can migrate to Pelican or whatever. >> This could be an opportunity to switch over to Git for publishing the >> site (which might take less time to upload), too, but I think that's >> unrelated. >> >> On Wed, 5 Aug 2020 at 07:31, Andrew Wetmore wrote: >>> >>> Hi: >>> >>> I am part of the Infrastructure team, and am writing to ask whether your >>> project is still using the Apache CMS for your project website. As you >>> know, the CMS is reaching end-of-life, and we need projects to move their >>> websites onto a different option within the next few weeks. >>> >>> There are several alternatives available, including those listed on this >>> page [1] on managing project websites. Infra is assembling a Wiki page [2] >>> on migrating a website from the CMS, and is looking forward to helping >>> projects with this transition. >>> >>> Please let me know whether your site is still on the Apache CMS and, if so, >>> who will be the project point-of-contact with Infra for the migration. >>> >>> Thank you! >>> >>> >>> >>> >>> [1] https://infra.apache.org/project-site.html >>> >>> [2] >>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS >>> >>> >>> >>> -- >>> Andrew Wetmore >>> Technical Writer-Editor >>> Infra >>> *Apache Software Foundation* >>> andr...@apache.org >>> >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> >> >> -- >> Matt Sicker >> > >
Re: The project website
I meant they support building your site from source automatically via Pelican similar to how GitHub supports Jekyll sources to generate the HTML from. Since we generate the HTML manually from Maven, you can use either service as they both support static contents. It's only a difference if we were using another system for generating the site. On Tue, 4 Aug 2020 at 10:00, Gary Gregory wrote: > > On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker wrote: > > > See also the asf-site and asf-staging branches for an Infra-supported > > site publishing system: > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features > > > > Seems to work fairly similar to a gh-pages branch, though they offer > > Pelican instead of Jekyll. Though since Commons sites are all > > statically generated from Maven, it doesn't matter which you use as > > you can simply commit the output files to one of those special > > branches. > > > > Hi Matt, > > I was not planning on changing how we deal with component sites, just the > Commons site itself. Or am I missing something? > > Personally, I also don't want to use Jekyl/Pelican, I'd prefer to go > straight to GitHub. > > Gary > > > > > > On Tue, 4 Aug 2020 at 08:57, Gary Gregory wrote: > > > > > > HI Andrew, > > > > > > I think we use both CMS and Buildbot if that makes any sense [1], but > > > whatever it is, it's no longer working [2][3], so I'm happy to switch. > > > > > > I see GitHub pages as an option, so why not go with that. > > > > > > Commons its own site obviously but it also has a lot of components each > > > with their own site. Each component site does not use CMS, it is > > published > > > manually as part of a release. > > > > > > So this migration should only apply to the Commons site and not component > > > sites, right? > > > > > > Gary > > > > > > [1] https://commons.apache.org/site-publish.html > > > [2] https://ci.apache.org/builders/commons-site-staging > > > [3] https://issues.apache.org/jira/browse/INFRA-20632 > > > > > > > > > > > > > > > > > > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore > > wrote: > > > > > > > Hi: > > > > > > > > I am part of the Infrastructure team, and am writing to ask whether > > your > > > > project is still using the Apache CMS for your project website. As you > > > > know, the CMS is reaching end-of-life, and we need projects to move > > their > > > > websites onto a different option within the next few weeks. > > > > > > > > There are several alternatives available, including those listed on > > this > > > > page [1] on managing project websites. Infra is assembling a Wiki page > > [2] > > > > on migrating a website from the CMS, and is looking forward to helping > > > > projects with this transition. > > > > > > > > Please let me know whether your site is still on the Apache CMS and, > > if so, > > > > who will be the project point-of-contact with Infra for the migration. > > > > > > > > Thank you! > > > > > > > > > > > > > > > > > > > > [1] https://infra.apache.org/project-site.html > > > > > > > > [2] > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > > > > > > > -- > > > > Andrew Wetmore > > > > Technical Writer-Editor > > > > Infra > > > > *Apache Software Foundation* > > > > andr...@apache.org > > > > > > > > < > > > > > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > > > > > Virus-free. > > > > www.avast.com > > > > < > > > > > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > > > > > > > > > -- > > Matt Sicker > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: The project website
On Tue, Aug 4, 2020 at 10:56 AM Matt Sicker wrote: > See also the asf-site and asf-staging branches for an Infra-supported > site publishing system: > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features > > Seems to work fairly similar to a gh-pages branch, though they offer > Pelican instead of Jekyll. Though since Commons sites are all > statically generated from Maven, it doesn't matter which you use as > you can simply commit the output files to one of those special > branches. > Hi Matt, I was not planning on changing how we deal with component sites, just the Commons site itself. Or am I missing something? Personally, I also don't want to use Jekyl/Pelican, I'd prefer to go straight to GitHub. Gary > > On Tue, 4 Aug 2020 at 08:57, Gary Gregory wrote: > > > > HI Andrew, > > > > I think we use both CMS and Buildbot if that makes any sense [1], but > > whatever it is, it's no longer working [2][3], so I'm happy to switch. > > > > I see GitHub pages as an option, so why not go with that. > > > > Commons its own site obviously but it also has a lot of components each > > with their own site. Each component site does not use CMS, it is > published > > manually as part of a release. > > > > So this migration should only apply to the Commons site and not component > > sites, right? > > > > Gary > > > > [1] https://commons.apache.org/site-publish.html > > [2] https://ci.apache.org/builders/commons-site-staging > > [3] https://issues.apache.org/jira/browse/INFRA-20632 > > > > > > > > > > > > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore > wrote: > > > > > Hi: > > > > > > I am part of the Infrastructure team, and am writing to ask whether > your > > > project is still using the Apache CMS for your project website. As you > > > know, the CMS is reaching end-of-life, and we need projects to move > their > > > websites onto a different option within the next few weeks. > > > > > > There are several alternatives available, including those listed on > this > > > page [1] on managing project websites. Infra is assembling a Wiki page > [2] > > > on migrating a website from the CMS, and is looking forward to helping > > > projects with this transition. > > > > > > Please let me know whether your site is still on the Apache CMS and, > if so, > > > who will be the project point-of-contact with Infra for the migration. > > > > > > Thank you! > > > > > > > > > > > > > > > [1] https://infra.apache.org/project-site.html > > > > > > [2] > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > > > > -- > > > Andrew Wetmore > > > Technical Writer-Editor > > > Infra > > > *Apache Software Foundation* > > > andr...@apache.org > > > > > > < > > > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > > > Virus-free. > > > www.avast.com > > > < > > > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > > > > -- > Matt Sicker > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: The project website
See also the asf-site and asf-staging branches for an Infra-supported site publishing system: https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features Seems to work fairly similar to a gh-pages branch, though they offer Pelican instead of Jekyll. Though since Commons sites are all statically generated from Maven, it doesn't matter which you use as you can simply commit the output files to one of those special branches. On Tue, 4 Aug 2020 at 08:57, Gary Gregory wrote: > > HI Andrew, > > I think we use both CMS and Buildbot if that makes any sense [1], but > whatever it is, it's no longer working [2][3], so I'm happy to switch. > > I see GitHub pages as an option, so why not go with that. > > Commons its own site obviously but it also has a lot of components each > with their own site. Each component site does not use CMS, it is published > manually as part of a release. > > So this migration should only apply to the Commons site and not component > sites, right? > > Gary > > [1] https://commons.apache.org/site-publish.html > [2] https://ci.apache.org/builders/commons-site-staging > [3] https://issues.apache.org/jira/browse/INFRA-20632 > > > > > > On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore wrote: > > > Hi: > > > > I am part of the Infrastructure team, and am writing to ask whether your > > project is still using the Apache CMS for your project website. As you > > know, the CMS is reaching end-of-life, and we need projects to move their > > websites onto a different option within the next few weeks. > > > > There are several alternatives available, including those listed on this > > page [1] on managing project websites. Infra is assembling a Wiki page [2] > > on migrating a website from the CMS, and is looking forward to helping > > projects with this transition. > > > > Please let me know whether your site is still on the Apache CMS and, if so, > > who will be the project point-of-contact with Infra for the migration. > > > > Thank you! > > > > > > > > > > [1] https://infra.apache.org/project-site.html > > > > [2] > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > -- > > Andrew Wetmore > > Technical Writer-Editor > > Infra > > *Apache Software Foundation* > > andr...@apache.org > > > > < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > Virus-free. > > www.avast.com > > < > > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > -- Matt Sicker - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: The project website
HI Andrew, I think we use both CMS and Buildbot if that makes any sense [1], but whatever it is, it's no longer working [2][3], so I'm happy to switch. I see GitHub pages as an option, so why not go with that. Commons its own site obviously but it also has a lot of components each with their own site. Each component site does not use CMS, it is published manually as part of a release. So this migration should only apply to the Commons site and not component sites, right? Gary [1] https://commons.apache.org/site-publish.html [2] https://ci.apache.org/builders/commons-site-staging [3] https://issues.apache.org/jira/browse/INFRA-20632 On Tue, Aug 4, 2020 at 9:40 AM Andrew Wetmore wrote: > Hi: > > I am part of the Infrastructure team, and am writing to ask whether your > project is still using the Apache CMS for your project website. As you > know, the CMS is reaching end-of-life, and we need projects to move their > websites onto a different option within the next few weeks. > > There are several alternatives available, including those listed on this > page [1] on managing project websites. Infra is assembling a Wiki page [2] > on migrating a website from the CMS, and is looking forward to helping > projects with this transition. > > Please let me know whether your site is still on the Apache CMS and, if so, > who will be the project point-of-contact with Infra for the migration. > > Thank you! > > > > > [1] https://infra.apache.org/project-site.html > > [2] > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > -- > Andrew Wetmore > Technical Writer-Editor > Infra > *Apache Software Foundation* > andr...@apache.org > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free. > www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
The project website
Hi: I am part of the Infrastructure team, and am writing to ask whether your project is still using the Apache CMS for your project website. As you know, the CMS is reaching end-of-life, and we need projects to move their websites onto a different option within the next few weeks. There are several alternatives available, including those listed on this page [1] on managing project websites. Infra is assembling a Wiki page [2] on migrating a website from the CMS, and is looking forward to helping projects with this transition. Please let me know whether your site is still on the Apache CMS and, if so, who will be the project point-of-contact with Infra for the migration. Thank you! [1] https://infra.apache.org/project-site.html [2] https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS -- Andrew Wetmore Technical Writer-Editor Infra *Apache Software Foundation* andr...@apache.org <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
