You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Andrew Wetmore <an...@apache.org> on 2020/08/05 12:30:39 UTC
Your 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*
andreww@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>
Re: GitHub Pages (Was: Your project website)
Posted by Christopher <ct...@apache.org>.
For what it's worth, GitHub Pages is simply a Jekyll-based site. If
you want something convenient like that, I highly recommend doing
something like Apache Accumulo and Apache Fluo did, to take advantage
of the ASF infrastructure, rather than rely on GitHub Pages to
generate the Jekyll.
See the Jekyll configuration at:
https://github.com/apache/fluo-website/blob/main/.asf.yaml
See the publishing instructions at:
https://github.com/apache/fluo-website#publishing
And, the rest of the content of that repo is the Jekyll-based site.
(Accumulo's site is basically the same setup, but depends on Jekyll
gem directly, rather than transitively via the GitHub Pages gem, and
added some custom ruby plugins to make writing links to issues easier
in our docs.)
On Tue, Sep 1, 2020 at 11:58 AM Ralph Goers <ra...@dslextreme.com> wrote:
>
> Apache doesn’t support using GitHub pages for the live site. They do allow it to be used for the staging site, but the details of how they work aren’t the same. To define a GitHub Pages site you have to specify
>
> github:
> ghp_branch: master
> ghp_path: /docs
>
> where the ghp_path has to be either null or “/docs”. The ASF support requires that the site be at the root, “/output”, or “/content”. We do not want to generate our site to a subdirectory so using GitHub Pages would require a different directory layout than the ASF site. Also, the web site would be generated under apache.github.io/ <http://apache.github.io/> while the staging site generated by the ASF is at logging.staged.apache.com <http://logging.staged.apache.com/>. Having an apache.org <http://apache.org/> staging site might be a bit easier to remember than a github.io <http://github.io/> site.
>
> Ralph
>
> > On Sep 1, 2020, at 8:08 AM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Part of it is because Apache offers an equivalent service for
> > publishing sites to apache.org directly rather than to github.io.
> >
> > On Tue, 1 Sep 2020 at 09:21, Volkan Yazıcı <vo...@gmail.com> wrote:
> >>
> >> Ralph, regarding your "after a discussion on Slack with infra I determined
> >> that using GitHub pages isn’t what we want to do." remark... I am curious
> >> to know about the details. Can we use GitHub pages in some way? Or why one
> >> should prefer one over another?
> >>
> >> On Mon, Aug 31, 2020 at 7:21 AM Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>
> >>> 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 <ra...@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 <an...@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*
> >>>>> andreww@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>
> >>>>
> >>>
> >>>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
Re: GitHub Pages (Was: Your project website)
Posted by Ralph Goers <ra...@dslextreme.com>.
Apache doesn’t support using GitHub pages for the live site. They do allow it to be used for the staging site, but the details of how they work aren’t the same. To define a GitHub Pages site you have to specify
github:
ghp_branch: master
ghp_path: /docs
where the ghp_path has to be either null or “/docs”. The ASF support requires that the site be at the root, “/output”, or “/content”. We do not want to generate our site to a subdirectory so using GitHub Pages would require a different directory layout than the ASF site. Also, the web site would be generated under apache.github.io/ <http://apache.github.io/> while the staging site generated by the ASF is at logging.staged.apache.com <http://logging.staged.apache.com/>. Having an apache.org <http://apache.org/> staging site might be a bit easier to remember than a github.io <http://github.io/> site.
Ralph
> On Sep 1, 2020, at 8:08 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> Part of it is because Apache offers an equivalent service for
> publishing sites to apache.org directly rather than to github.io.
>
> On Tue, 1 Sep 2020 at 09:21, Volkan Yazıcı <vo...@gmail.com> wrote:
>>
>> Ralph, regarding your "after a discussion on Slack with infra I determined
>> that using GitHub pages isn’t what we want to do." remark... I am curious
>> to know about the details. Can we use GitHub pages in some way? Or why one
>> should prefer one over another?
>>
>> On Mon, Aug 31, 2020 at 7:21 AM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>
>>> 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 <ra...@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 <an...@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*
>>>>> andreww@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>
>>>>
>>>
>>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: GitHub Pages (Was: Your project website)
Posted by Matt Sicker <bo...@gmail.com>.
Part of it is because Apache offers an equivalent service for
publishing sites to apache.org directly rather than to github.io.
On Tue, 1 Sep 2020 at 09:21, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Ralph, regarding your "after a discussion on Slack with infra I determined
> that using GitHub pages isn’t what we want to do." remark... I am curious
> to know about the details. Can we use GitHub pages in some way? Or why one
> should prefer one over another?
>
> On Mon, Aug 31, 2020 at 7:21 AM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
> > 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 <ra...@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 <an...@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*
> > >> andreww@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>
> > >
> >
> >
--
Matt Sicker <bo...@gmail.com>
GitHub Pages (Was: Your project website)
Posted by Volkan Yazıcı <vo...@gmail.com>.
Ralph, regarding your "after a discussion on Slack with infra I determined
that using GitHub pages isn’t what we want to do." remark... I am curious
to know about the details. Can we use GitHub pages in some way? Or why one
should prefer one over another?
On Mon, Aug 31, 2020 at 7:21 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> 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 <ra...@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 <an...@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*
> >> andreww@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>
> >
>
>
Re: Your project website
Posted by Matt Sicker <bo...@gmail.com>.
You can make direct links to the file on downloads.a.o nowadays as that's
the expected method. The mirror select is now a backend detail of the
download site itself.
On Tue, 1 Sep 2020 at 10:04, Davyd McColl <da...@gmail.com> wrote:
> Matt
> I don't mind doing so - I'd just have to update the base download html
> file, if that's ok (and the download link on the main page as it points to
> the .cgi).
>
> Most of the download page exists "as-is", but I can see that there's
> placeholders for selecting mirrors. If I can simply replace those with
> direct linking (and probably take out the drop-down that allows selecting a
> different mirror), then that's no problem -- is that ok?
>
> -d
>
> On 2020/09/01 16:50:05, Matt Sicker <bo...@gmail.com> wrote:
> You can link directly to
> https://downloads.apache.org/ as that site handles mirror redirects or CDN
> or whatever it’s implemented as right now. That CGI script is ancient and
> is no longer necessary as of, oh, many years I think? 😉
>
> On Tue, Sep 1, 2020 at 01:17 Davyd McColl wrote:
>
> > Ralph, the log4net download link points to a cgi script; I've updated the
> > associated download_log4net.html as I think would be correct, but I'll
> only
> > know once it's run through the cgi script (which simply refers to an
> > external script, so doesn't really tell me what it does or expects). I
> > gather this is for setting up the mirror links.
> >
> >
> >
> > The latest download html is commited to subversion -- please try again?
> >
> >
> >
> > -d
> >
> >
> >
> > On 2020/09/01 05:01:45, Ralph Goers wrote:
> >
> > Yes, I thought I had checked them but I can confirm those 2 sites are
> > getting a 404. I have created
> > https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799 to get
> > some help determining what the problem might be.
> >
> >
> >
> > I have also created
> >
> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site
> > to document editing the site and sub-projects.
> >
> >
> >
> > Ralph
> >
> >
> >
> > > On Aug 31, 2020, at 6:24 PM, Robert Middleton wrote:
> >
> > >
> >
> > > Something is funny with logging.apache.org - the links for log4cxx and
> >
> > > chainsaw lead to a 404 at the moment. I'm not sure if that's because
> >
> > > things are changing or if something else is messed up.
> >
> > >
> >
> > > I assume this means now that the site will be committed to git instead
> of
> >
> > > svn?
> >
> > >
> >
> > > -Robert Middleton
> >
> > >
> >
> > > On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers
> >
> > > wrote:
> >
> > >
> >
> > >> The download link for Log4net is wrong even for the live site. For
> some
> >
> > >> reason it doesn’t seem it was updated during the release process.
> >
> > >>
> >
> > >> Ralph
> >
> > >>
> >
> > >>> On Aug 31, 2020, at 11:47 AM, Matt Sicker wrote:
> >
> > >>>
> >
> > >>> Looks good to me. The download link on the log4net page is broken,
> but
> >
> > >>> everything else looks good.
> >
> > >>>
> >
> > >>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers
> >
> > >> > wrote:
> >
> > >>>>
> >
> > >>>> The logging site is now working properly. Please look at
> >
> > >> http://logging.staged.apache.org <
> >
> > >> http://logging.staged.apache.org/ >.
> >
> > >> I will not work on documenting this in Confluence. I know that not all
> > of
> >
> > >> the past log4j releases are in git yet. I will be taking care of that
> > soon.
> >
> > >> Please let me know if you see any other problems.
> >
> > >>>>
> >
> > >>>> Ralph
> >
> > >>>>
> >
> > >>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers
> >
> > >> wrote:
> >
> > >>>>>
> >
> > >>>>> 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
> >
> > >> 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 .
> >
> > >>>>>>
> >
> > >>>>>> 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
> >
> > >> 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*
> >
> > >>>>>>> andreww@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>
> >
> > >>>>>>
> >
> > >>>>>
> >
> > >>>>
> >
> > >>>
> >
> > >>>
> >
> > >>> --
> >
> > >>> Matt Sicker >
> >
> > >>
> >
> > >>
> >
> >
> >
> > --
> Matt Sicker
>
--
Matt Sicker <bo...@gmail.com>
Re: Your project website
Posted by Davyd McColl <da...@gmail.com>.
Matt
I don't mind doing so - I'd just have to update the base download html file, if that's ok (and the download link on the main page as it points to the .cgi).
Most of the download page exists "as-is", but I can see that there's placeholders for selecting mirrors. If I can simply replace those with direct linking (and probably take out the drop-down that allows selecting a different mirror), then that's no problem -- is that ok?
-d
On 2020/09/01 16:50:05, Matt Sicker <bo...@gmail.com> wrote:
You can link directly to
https://downloads.apache.org/ as that site handles mirror redirects or CDN
or whatever it’s implemented as right now. That CGI script is ancient and
is no longer necessary as of, oh, many years I think? 😉
On Tue, Sep 1, 2020 at 01:17 Davyd McColl wrote:
> Ralph, the log4net download link points to a cgi script; I've updated the
> associated download_log4net.html as I think would be correct, but I'll only
> know once it's run through the cgi script (which simply refers to an
> external script, so doesn't really tell me what it does or expects). I
> gather this is for setting up the mirror links.
>
>
>
> The latest download html is commited to subversion -- please try again?
>
>
>
> -d
>
>
>
> On 2020/09/01 05:01:45, Ralph Goers wrote:
>
> Yes, I thought I had checked them but I can confirm those 2 sites are
> getting a 404. I have created
> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799 to get
> some help determining what the problem might be.
>
>
>
> I have also created
> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site
> to document editing the site and sub-projects.
>
>
>
> Ralph
>
>
>
> > On Aug 31, 2020, at 6:24 PM, Robert Middleton wrote:
>
> >
>
> > Something is funny with logging.apache.org - the links for log4cxx and
>
> > chainsaw lead to a 404 at the moment. I'm not sure if that's because
>
> > things are changing or if something else is messed up.
>
> >
>
> > I assume this means now that the site will be committed to git instead of
>
> > svn?
>
> >
>
> > -Robert Middleton
>
> >
>
> > On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers
>
> > wrote:
>
> >
>
> >> The download link for Log4net is wrong even for the live site. For some
>
> >> reason it doesn’t seem it was updated during the release process.
>
> >>
>
> >> Ralph
>
> >>
>
> >>> On Aug 31, 2020, at 11:47 AM, Matt Sicker wrote:
>
> >>>
>
> >>> Looks good to me. The download link on the log4net page is broken, but
>
> >>> everything else looks good.
>
> >>>
>
> >>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers
>
> >> > wrote:
>
> >>>>
>
> >>>> The logging site is now working properly. Please look at
>
> >> http://logging.staged.apache.org <
>
> >> http://logging.staged.apache.org/ >.
>
> >> I will not work on documenting this in Confluence. I know that not all
> of
>
> >> the past log4j releases are in git yet. I will be taking care of that
> soon.
>
> >> Please let me know if you see any other problems.
>
> >>>>
>
> >>>> Ralph
>
> >>>>
>
> >>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers
>
> >> wrote:
>
> >>>>>
>
> >>>>> 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
>
> >> 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 .
>
> >>>>>>
>
> >>>>>> 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
>
> >> 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*
>
> >>>>>>> andreww@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>
>
> >>>>>>
>
> >>>>>
>
> >>>>
>
> >>>
>
> >>>
>
> >>> --
>
> >>> Matt Sicker >
>
> >>
>
> >>
>
>
>
> --
Matt Sicker
Re: Your project website
Posted by Matt Sicker <bo...@gmail.com>.
You can link directly to
https://downloads.apache.org/ as that site handles mirror redirects or CDN
or whatever it’s implemented as right now. That CGI script is ancient and
is no longer necessary as of, oh, many years I think? 😉
On Tue, Sep 1, 2020 at 01:17 Davyd McColl <da...@gmail.com> wrote:
> Ralph, the log4net download link points to a cgi script; I've updated the
> associated download_log4net.html as I think would be correct, but I'll only
> know once it's run through the cgi script (which simply refers to an
> external script, so doesn't really tell me what it does or expects). I
> gather this is for setting up the mirror links.
>
>
>
> The latest download html is commited to subversion -- please try again?
>
>
>
> -d
>
>
>
> On 2020/09/01 05:01:45, Ralph Goers <ra...@dslextreme.com> wrote:
>
> Yes, I thought I had checked them but I can confirm those 2 sites are
> getting a 404. I have created
> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799 to get
> some help determining what the problem might be.
>
>
>
> I have also created
> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site
> to document editing the site and sub-projects.
>
>
>
> Ralph
>
>
>
> > On Aug 31, 2020, at 6:24 PM, Robert Middleton wrote:
>
> >
>
> > Something is funny with logging.apache.org - the links for log4cxx and
>
> > chainsaw lead to a 404 at the moment. I'm not sure if that's because
>
> > things are changing or if something else is messed up.
>
> >
>
> > I assume this means now that the site will be committed to git instead of
>
> > svn?
>
> >
>
> > -Robert Middleton
>
> >
>
> > On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers
>
> > wrote:
>
> >
>
> >> The download link for Log4net is wrong even for the live site. For some
>
> >> reason it doesn’t seem it was updated during the release process.
>
> >>
>
> >> Ralph
>
> >>
>
> >>> On Aug 31, 2020, at 11:47 AM, Matt Sicker wrote:
>
> >>>
>
> >>> Looks good to me. The download link on the log4net page is broken, but
>
> >>> everything else looks good.
>
> >>>
>
> >>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers
>
> >> > wrote:
>
> >>>>
>
> >>>> The logging site is now working properly. Please look at
>
> >> http://logging.staged.apache.org <
>
> >> http://logging.staged.apache.org/ >.
>
> >> I will not work on documenting this in Confluence. I know that not all
> of
>
> >> the past log4j releases are in git yet. I will be taking care of that
> soon.
>
> >> Please let me know if you see any other problems.
>
> >>>>
>
> >>>> Ralph
>
> >>>>
>
> >>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers
>
> >> wrote:
>
> >>>>>
>
> >>>>> 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
>
> >> 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 .
>
> >>>>>>
>
> >>>>>> 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
>
> >> 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*
>
> >>>>>>> andreww@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>
>
> >>>>>>
>
> >>>>>
>
> >>>>
>
> >>>
>
> >>>
>
> >>> --
>
> >>> Matt Sicker >
>
> >>
>
> >>
>
>
>
> --
Matt Sicker <bo...@gmail.com>
Re: Your project website
Posted by Davyd McColl <da...@gmail.com>.
Ralph, the log4net download link points to a cgi script; I've updated the associated download_log4net.html as I think would be correct, but I'll only know once it's run through the cgi script (which simply refers to an external script, so doesn't really tell me what it does or expects). I gather this is for setting up the mirror links.
The latest download html is commited to subversion -- please try again?
-d
On 2020/09/01 05:01:45, Ralph Goers <ra...@dslextreme.com> wrote:
Yes, I thought I had checked them but I can confirm those 2 sites are getting a 404. I have created https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799 to get some help determining what the problem might be.
I have also created https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site to document editing the site and sub-projects.
Ralph
> On Aug 31, 2020, at 6:24 PM, Robert Middleton wrote:
>
> Something is funny with logging.apache.org - the links for log4cxx and
> chainsaw lead to a 404 at the moment. I'm not sure if that's because
> things are changing or if something else is messed up.
>
> I assume this means now that the site will be committed to git instead of
> svn?
>
> -Robert Middleton
>
> On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers
> wrote:
>
>> The download link for Log4net is wrong even for the live site. For some
>> reason it doesn’t seem it was updated during the release process.
>>
>> Ralph
>>
>>> On Aug 31, 2020, at 11:47 AM, Matt Sicker wrote:
>>>
>>> Looks good to me. The download link on the log4net page is broken, but
>>> everything else looks good.
>>>
>>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers
>> > wrote:
>>>>
>>>> The logging site is now working properly. Please look at
>> http://logging.staged.apache.org <
>> http://logging.staged.apache.org/ >.
>> I will not work on documenting this in Confluence. I know that not all of
>> the past log4j releases are in git yet. I will be taking care of that soon.
>> Please let me know if you see any other problems.
>>>>
>>>> Ralph
>>>>
>>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers
>> wrote:
>>>>>
>>>>> 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
>> 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 .
>>>>>>
>>>>>> 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
>> 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*
>>>>>>> andreww@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>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker >
>>
>>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, I thought I had checked them but I can confirm those 2 sites are getting a 404. I have created https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799 <https://issues.apache.org/jira/projects/INFRA/issues/INFRA-20799> to get some help determining what the problem might be.
I have also created https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site <https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Git+Hosted+Web+Site> to document editing the site and sub-projects.
Ralph
> On Aug 31, 2020, at 6:24 PM, Robert Middleton <os...@gmail.com> wrote:
>
> Something is funny with logging.apache.org - the links for log4cxx and
> chainsaw lead to a 404 at the moment. I'm not sure if that's because
> things are changing or if something else is messed up.
>
> I assume this means now that the site will be committed to git instead of
> svn?
>
> -Robert Middleton
>
> On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> The download link for Log4net is wrong even for the live site. For some
>> reason it doesn’t seem it was updated during the release process.
>>
>> Ralph
>>
>>> On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> Looks good to me. The download link on the log4net page is broken, but
>>> everything else looks good.
>>>
>>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com
>> <ma...@dslextreme.com>> wrote:
>>>>
>>>> The logging site is now working properly. Please look at
>> http://logging.staged.apache.org <http://logging.staged.apache.org/> <
>> http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>.
>> I will not work on documenting this in Confluence. I know that not all of
>> the past log4j releases are in git yet. I will be taking care of that soon.
>> Please let me know if you see any other problems.
>>>>
>>>> Ralph
>>>>
>>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>>>
>>>>> 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 <ra...@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 <an...@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*
>>>>>>> andreww@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>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>>
>>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
All the sites should now be online.
Ralph
> On Sep 1, 2020, at 8:57 AM, Christian Grobmeier <gr...@apache.org> wrote:
>
> Hi,
>
> I see there is some activity on the site - I discovered log4php and the audit component are currently 404.
> the links look correct, it seems as the sites are not at their location.
>
> Christian
>
> On Tue, Sep 1, 2020, at 03:24, Robert Middleton wrote:
>> Something is funny with logging.apache.org - the links for log4cxx and
>> chainsaw lead to a 404 at the moment. I'm not sure if that's because
>> things are changing or if something else is messed up.
>>
>> I assume this means now that the site will be committed to git instead of
>> svn?
>>
>> -Robert Middleton
>>
>> On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>
>>> The download link for Log4net is wrong even for the live site. For some
>>> reason it doesn’t seem it was updated during the release process.
>>>
>>> Ralph
>>>
>>>> On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> Looks good to me. The download link on the log4net page is broken, but
>>>> everything else looks good.
>>>>
>>>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com
>>> <ma...@dslextreme.com>> wrote:
>>>>>
>>>>> The logging site is now working properly. Please look at
>>> http://logging.staged.apache.org <http://logging.staged.apache.org/> <
>>> http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>.
>>> I will not work on documenting this in Confluence. I know that not all of
>>> the past log4j releases are in git yet. I will be taking care of that soon.
>>> Please let me know if you see any other problems.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>>>>
>>>>>> 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 <ra...@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 <an...@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*
>>>>>>>> andreww@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>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>>>
>>>
>>
>
Re: Your project website
Posted by Christian Grobmeier <gr...@apache.org>.
Hi,
I see there is some activity on the site - I discovered log4php and the audit component are currently 404.
the links look correct, it seems as the sites are not at their location.
Christian
On Tue, Sep 1, 2020, at 03:24, Robert Middleton wrote:
> Something is funny with logging.apache.org - the links for log4cxx and
> chainsaw lead to a 404 at the moment. I'm not sure if that's because
> things are changing or if something else is messed up.
>
> I assume this means now that the site will be committed to git instead of
> svn?
>
> -Robert Middleton
>
> On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
> > The download link for Log4net is wrong even for the live site. For some
> > reason it doesn’t seem it was updated during the release process.
> >
> > Ralph
> >
> > > On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > Looks good to me. The download link on the log4net page is broken, but
> > > everything else looks good.
> > >
> > > On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com
> > <ma...@dslextreme.com>> wrote:
> > >>
> > >> The logging site is now working properly. Please look at
> > http://logging.staged.apache.org <http://logging.staged.apache.org/> <
> > http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>.
> > I will not work on documenting this in Confluence. I know that not all of
> > the past log4j releases are in git yet. I will be taking care of that soon.
> > Please let me know if you see any other problems.
> > >>
> > >> Ralph
> > >>
> > >>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com>
> > wrote:
> > >>>
> > >>> 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 <ra...@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 <an...@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*
> > >>>>> andreww@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>
> > >>>>
> > >>>
> > >>
> > >
> > >
> > > --
> > > Matt Sicker <boards@gmail.com <ma...@gmail.com>>
> >
> >
>
Re: Your project website
Posted by Robert Middleton <os...@gmail.com>.
Something is funny with logging.apache.org - the links for log4cxx and
chainsaw lead to a 404 at the moment. I'm not sure if that's because
things are changing or if something else is messed up.
I assume this means now that the site will be committed to git instead of
svn?
-Robert Middleton
On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers <ra...@dslextreme.com>
wrote:
> The download link for Log4net is wrong even for the live site. For some
> reason it doesn’t seem it was updated during the release process.
>
> Ralph
>
> > On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Looks good to me. The download link on the log4net page is broken, but
> > everything else looks good.
> >
> > On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com
> <ma...@dslextreme.com>> wrote:
> >>
> >> The logging site is now working properly. Please look at
> http://logging.staged.apache.org <http://logging.staged.apache.org/> <
> http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>.
> I will not work on documenting this in Confluence. I know that not all of
> the past log4j releases are in git yet. I will be taking care of that soon.
> Please let me know if you see any other problems.
> >>
> >> Ralph
> >>
> >>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>>
> >>> 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 <ra...@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 <an...@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*
> >>>>> andreww@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>
> >>>>
> >>>
> >>
> >
> >
> > --
> > Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
> On Aug 31, 2020, at 1:15 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> The download link for Log4net is wrong even for the live site. For some reason it doesn’t seem it was updated during the release process.
>
> Ralph
>
>> On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> Looks good to me. The download link on the log4net page is broken, but
>> everything else looks good.
>>
>> On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>>>
>>> The logging site is now working properly. Please look at http://logging.staged.apache.org <http://logging.staged.apache.org/> <http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>. I will not work on documenting this in Confluence. I know that not all of the past log4j releases are in git yet. I will be taking care of that soon. Please let me know if you see any other problems.
>>>
>>> Ralph
>>>
>>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>>>
>>>> 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 <ra...@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 <an...@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*
>>>>>> andreww@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>
>>>>>
>>>>
>>>
>>
>>
>> --
>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
The download link for Log4net is wrong even for the live site. For some reason it doesn’t seem it was updated during the release process.
Ralph
> On Aug 31, 2020, at 11:47 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> Looks good to me. The download link on the log4net page is broken, but
> everything else looks good.
>
> On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>>
>> The logging site is now working properly. Please look at http://logging.staged.apache.org <http://logging.staged.apache.org/> <http://logging.staged.apache.org/ <http://logging.staged.apache.org/>>. I will not work on documenting this in Confluence. I know that not all of the past log4j releases are in git yet. I will be taking care of that soon. Please let me know if you see any other problems.
>>
>> Ralph
>>
>>> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>>
>>> 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 <ra...@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 <an...@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*
>>>>> andreww@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>
>>>>
>>>
>>
>
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
Re: Your project website
Posted by Matt Sicker <bo...@gmail.com>.
Looks good to me. The download link on the log4net page is broken, but
everything else looks good.
On Mon, 31 Aug 2020 at 13:31, Ralph Goers <ra...@dslextreme.com> wrote:
>
> The logging site is now working properly. Please look at http://logging.staged.apache.org <http://logging.staged.apache.org/>. I will not work on documenting this in Confluence. I know that not all of the past log4j releases are in git yet. I will be taking care of that soon. Please let me know if you see any other problems.
>
> Ralph
>
> > On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> >
> > 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 <ra...@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 <an...@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*
> >>> andreww@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>
> >>
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
The logging site is now working properly. Please look at http://logging.staged.apache.org <http://logging.staged.apache.org/>. I will not work on documenting this in Confluence. I know that not all of the past log4j releases are in git yet. I will be taking care of that soon. Please let me know if you see any other problems.
Ralph
> On Aug 30, 2020, at 10:21 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> 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 <ra...@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 <an...@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*
>>> andreww@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>
>>
>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
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 <ra...@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 <an...@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*
>> andreww@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>
>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
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 <an...@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*
> andreww@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>
Re: Your project website
Posted by Andrew Wetmore <an...@apache.org>.
Hi, all:
Yes, the migration of your CMS pages should not be too troublesome, whether
you want to stay on Subversion or move over to Git.
Someone said this was the first time they had heard of the requirement to
move off the CMS. The first emails went out about a year ago, long before I
joined Infra, and the majority of projects have completed their migrations.
When the move is complete, please let us know, with a PMC statement
approving our removal of project artifacts from the CMS.
Thanks!
Andrew
On Wed, Aug 5, 2020 at 9:30 AM Andrew Wetmore <an...@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*
> andreww@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>
> <#m_363820154960497046_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
--
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andreww@apache.org
Re: Your project website
Posted by sebb <se...@gmail.com>.
On Wed, 5 Aug 2020 at 19:45, Gary Gregory <ga...@gmail.com> 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 <ch...@gmail.com> 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 <ra...@dslextreme.com>
> > > Subject: Re: Your project website
> > > Date: August 5, 2020 at 12:09:49 PM EDT
> > > To: dev@logging.apache.org
> > > Reply-To: dev@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 <bo...@gmail.com> 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 <an...@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*
> > >>> andreww@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>
> > >>
> > >>
> > >>
> > >> --
> > >> Matt Sicker <bo...@gmail.com>
> > >>
> > >
> > >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Your project website
Posted by Gary Gregory <ga...@gmail.com>.
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 <ch...@gmail.com> 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 <ra...@dslextreme.com>
> > Subject: Re: Your project website
> > Date: August 5, 2020 at 12:09:49 PM EDT
> > To: dev@logging.apache.org
> > Reply-To: dev@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 <bo...@gmail.com> 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 <an...@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*
> >>> andreww@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>
> >>
> >>
> >>
> >> --
> >> Matt Sicker <bo...@gmail.com>
> >>
> >
> >
>
>
Fwd: Your project website
Posted by Rob Tompkins <ch...@gmail.com>.
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 <ra...@dslextreme.com>
> Subject: Re: Your project website
> Date: August 5, 2020 at 12:09:49 PM EDT
> To: dev@logging.apache.org
> Reply-To: dev@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 <bo...@gmail.com> 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 <an...@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*
>>> andreww@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>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
Re: Your project website
Posted by Rob Tompkins <ch...@gmail.com>.
> On Aug 5, 2020, at 12:30 PM, Matt Sicker <bo...@gmail.com> 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 <ra...@dslextreme.com> 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 <bo...@gmail.com> 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 <an...@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*
>>>> andreww@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>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Your project website
Posted by Rob Tompkins <ch...@gmail.com>.
> On Aug 5, 2020, at 12:30 PM, Matt Sicker <bo...@gmail.com> 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 <ra...@dslextreme.com> 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 <bo...@gmail.com> 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 <an...@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*
>>>> andreww@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>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: Your project website
Posted by Matt Sicker <bo...@gmail.com>.
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.
On Wed, 5 Aug 2020 at 11:10, Ralph Goers <ra...@dslextreme.com> 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 <bo...@gmail.com> 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 <an...@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*
> >> andreww@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>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
>
--
Matt Sicker <bo...@gmail.com>
Re: Your project website
Posted by Ralph Goers <ra...@dslextreme.com>.
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 <bo...@gmail.com> 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 <an...@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*
>> andreww@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>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Your project website
Posted by Matt Sicker <bo...@gmail.com>.
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 <an...@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*
> andreww@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>
--
Matt Sicker <bo...@gmail.com>