You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Robert Middleton <os...@gmail.com> on 2020/09/01 01:24:50 UTC
Re: Your project website
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 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>>
> >
> >
>