Another follow-up. After a discussion on Slack with infra I determined that using GitHub pages isn’t what we want to do. I then modified the site to work with the normal “pub/sub” that infra supports via the .asf.yaml files. The documentation for that says it supports having sub-projects be hosted in separate repos so I followed those instructions. Unfortunately, those sites are not deploying. I have opened https://issues.apache.org/jira/browse/INFRA-20792 <https://issues.apache.org/jira/browse/INFRA-20792> to try to get this addressed but have not gotten a response to this yet nor to the questions I asked on Slack. Not surprising since it was a Sunday afternoon.
I have not documented the process yet since I am not sure I did everything correctly. FWIW, I plan to hold off starting the log4j release process until this is resolve since trying to commit a new Log4j web site using svn has been taking at least 30 minutes. My experience in committing the preview site to my personal GitHub site has shown that it is significantly faster. Ralph > On Aug 30, 2020, at 11:29 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > I have created the logging site in git at > https://github.com/apache/logging-site > <https://github.com/apache/logging-site>. I used jbake to generate the CMS > portion of the site. It is pretty easy. All you have to do is > > cd sources > Make the required changes > mvn install > > You will then have a viewable site in the /docs directory and can view it by > opening docs/index.html in the browser. > > I created a .asf.yaml file with the intention of having a preview site on the > asf-staging branch and the live site at master. However, the instructions for > the staging site seem to imply using pypubsub where I am attempting to use > GitHub Pages for the live site. These seem to conflict as GitHub pages wants > the site in the /docs directory while pypubsub seems to imply it needs to be > in the root directory. > > I am able to get a site up at https://apache.github.io/logging-site > <https://apache.github.io/logging-site> but it is not being reflected at > https://logging.apache.org <https://logging.apache.org/>. > > At this point without clearer instructions from infra I am not sure where to > go to make the site live. > > I have started a confluence page to document managing the site but it seems > much easier than using the CMS. > > Ralph > > > >> On Aug 5, 2020, at 5:30 AM, Andrew Wetmore <andr...@apache.org> 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&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
