I had a conversation with Daniel.  From what I can tell the current Logging web site is maintained at https://svn.apache.org/repos/asf/logging/site/trunk/docs.  I've never maintained the logging web site but some of the sub projects there, such as log4j, were definitely built by Maven. What daniel is telling me is that as far as Infra is concerned we can continue to use that same location with svnpubsub.  However, editing the main site only would either require checking out all the subproject sites too or using svn checkout --depth=immediates.

My question is, how has the web site been maintained in the past?  


On Apr 20, 2012, at 11:14 AM, Christian Grobmeier wrote:

thank you Ralph!

On Fri, Apr 20, 2012 at 7:27 PM, Ralph Goers <ralph.goers@dslextreme.com> wrote:
I've created https://issues.apache.org/jira/browse/INFRA-4699 and modeled it
after Ant. That was the only project I know of that has sub sites.


On Apr 19, 2012, at 1:10 AM, Ivan Habunek wrote:

Sounds good to me. Having a separate folder (/site/main) for the main site
is great. Currently it's in root and I'm not sure how I would go about
updating it.


On 19 April 2012 09:11, Ralph Goers <ralph.goers@dslextreme.com> wrote:

Does anyone else have any other thoughts before I open an infra ticket?


On Apr 18, 2012, at 10:20 PM, Christian Grobmeier wrote:

On Tue, Apr 17, 2012 at 9:47 PM, Ralph Goers
<ralph.goers@dslextreme.com> wrote:
I'm OK with this, but I'm not sure if infra is OK with that structure.
Based on that I think what we want to request is the following be added to
the rules.

/x1/www/www.apache.org/dist/logging: %(DIST)s/release/logging

/x1/www/logging.apache.org: %(ASF)s/logging/site/main
/x1/www/logging.apache.org/log4j: %(ASF)s/logging/site/log4j
/x1/www/logging.apache.org/log4j2: %(ASF)s/logging/site/log4j2
/x1/www/logging.apache.org/log4php: %(ASF)s/logging/site/log4php
/x1/www/logging.apache.org/log4cxx: %(ASF)s/logging/site/log4cxx
/x1/www/logging.apache.org/log4net: %(ASF)s/logging/site/log4net

great, didn't know it is possible.

chainsaw and log4j companions also show up on the main site. Do we also
want those?

I think so. Imho we should start treat Chainsaw more as a product on
its own. Companions is small but we should treat it the same way. That
would ease things I think. But thats just my 2 cents.



On Apr 16, 2012, at 12:37 AM, Christian Grobmeier wrote:

On Mon, Apr 16, 2012 at 9:31 AM, Ralph Goers
<ralph.goers@dslextreme.com> wrote:
I'm actually more concerned with us having to use svnpubsub
(see http://www.apache.org/dev/project-site.html).  The maven team
created a
plugin -
http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/  to
aid in this but I haven't tired it. I also understand that it
requires the
main website to have something done to it first.

didn't know about the mvn plug - thanks!

Log4j2 uses the Maven site plugin so I guess I really need to know is
the location of the svn directory would be to pass to

What about:

For example:
http://svn.apache.org/repos/asf/logging/site/pubsub/main (start site)

and so on


On Apr 16, 2012, at 12:14 AM, Christian Grobmeier wrote:

On Mon, Apr 16, 2012 at 6:38 AM, Ralph Goers

Do we have a process in place for updating the web site?  I'm trying
to go
through any issues that might exist with doing a release of Log4j2
and this
is one of them.

I am not aware of a specific process (old timers might want to
correct me).
So far I know we have updated the website whenever the release has
been published. I am not a huge fan of restricting website updates to
releases and think we should be able to update at any time we want.

This again touches the question with pubsub. We need to make a
decision if we move to mvn site:deploy or do something else.