You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Ralph Goers <ra...@dslextreme.com> on 2012/08/04 21:59:37 UTC
Commons web site
Infra has mandated that all projects move to the Apache CMS (or svnpubsub) by the end of the year. We also must change from distributing releases from people.apache.org to https://dist.apache.org/repos/dist/commons. Changing the second item is fairly trivial but migrating the web site is a pretty large effort.
The Logging project is also an umbrella project, albeit much smaller, and recently made the migration. I recommend that commons use the same (or similar) mechanism that Logging is using - the main site uses the CMS directly and sub projects can either use the CMS or be manually committed. See (http://wiki.apache.org/logging/ManagingTheWebSite).
To summarize,
1. The main Commons site would be managed at https://svn.apache.org/repos/asf/commons/site/trunk.
2. Each subproject would reside at https://svn.apache.org/repos/infra/websites/production/commons/content/projectname.
3. If the subproject does not use the CMS it would be specified in extpaths.txt and would follow guidelines similar to the wiki link above.
4. If the project uses the CMS it would not be specified in extpaths.txt and would commit its files into the svn area in item 1.
FWIW, I've also built the Flume website using this model. They use maven to build the main site (the CMS will run "mvn site" when any content is changed). Logging is using a tool called Twig.
I'm not necessarily volunteering to build the site as I don't have a lot of time at the moment, but I am willing to help since I've done it for two projects now.
Comments?
Ralph
Re: Commons web site
Posted by Luc Maisonobe <Lu...@free.fr>.
Hi,
Le 05/08/2012 05:05, Matt Benson a écrit :
> Hi Ralph--thanks for opening this up and offering a concrete
> direction. This sounds like a good approach and I will try to read up
> on the link you provided in the next couple of days.
I agree with the proposal. We really need to move forward on this, as
infra will need time to configure our project among the large number of
other Apache projects. Let's be fair with their time and not rush when
the deadline approaches.
Any volunteer to do the work?
Luc
>
> Matt
>
> On Sat, Aug 4, 2012 at 2:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> Infra has mandated that all projects move to the Apache CMS (or svnpubsub) by the end of the year. We also must change from distributing releases from people.apache.org to https://dist.apache.org/repos/dist/commons. Changing the second item is fairly trivial but migrating the web site is a pretty large effort.
>>
>> The Logging project is also an umbrella project, albeit much smaller, and recently made the migration. I recommend that commons use the same (or similar) mechanism that Logging is using - the main site uses the CMS directly and sub projects can either use the CMS or be manually committed. See (http://wiki.apache.org/logging/ManagingTheWebSite).
>>
>> To summarize,
>> 1. The main Commons site would be managed at https://svn.apache.org/repos/asf/commons/site/trunk.
>> 2. Each subproject would reside at https://svn.apache.org/repos/infra/websites/production/commons/content/projectname.
>> 3. If the subproject does not use the CMS it would be specified in extpaths.txt and would follow guidelines similar to the wiki link above.
>> 4. If the project uses the CMS it would not be specified in extpaths.txt and would commit its files into the svn area in item 1.
>>
>> FWIW, I've also built the Flume website using this model. They use maven to build the main site (the CMS will run "mvn site" when any content is changed). Logging is using a tool called Twig.
>>
>> I'm not necessarily volunteering to build the site as I don't have a lot of time at the moment, but I am willing to help since I've done it for two projects now.
>>
>> Comments?
>>
>> Ralph
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Commons web site
Posted by Matt Benson <gu...@gmail.com>.
Hi Ralph--thanks for opening this up and offering a concrete
direction. This sounds like a good approach and I will try to read up
on the link you provided in the next couple of days.
Matt
On Sat, Aug 4, 2012 at 2:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> Infra has mandated that all projects move to the Apache CMS (or svnpubsub) by the end of the year. We also must change from distributing releases from people.apache.org to https://dist.apache.org/repos/dist/commons. Changing the second item is fairly trivial but migrating the web site is a pretty large effort.
>
> The Logging project is also an umbrella project, albeit much smaller, and recently made the migration. I recommend that commons use the same (or similar) mechanism that Logging is using - the main site uses the CMS directly and sub projects can either use the CMS or be manually committed. See (http://wiki.apache.org/logging/ManagingTheWebSite).
>
> To summarize,
> 1. The main Commons site would be managed at https://svn.apache.org/repos/asf/commons/site/trunk.
> 2. Each subproject would reside at https://svn.apache.org/repos/infra/websites/production/commons/content/projectname.
> 3. If the subproject does not use the CMS it would be specified in extpaths.txt and would follow guidelines similar to the wiki link above.
> 4. If the project uses the CMS it would not be specified in extpaths.txt and would commit its files into the svn area in item 1.
>
> FWIW, I've also built the Flume website using this model. They use maven to build the main site (the CMS will run "mvn site" when any content is changed). Logging is using a tool called Twig.
>
> I'm not necessarily volunteering to build the site as I don't have a lot of time at the moment, but I am willing to help since I've done it for two projects now.
>
> Comments?
>
> Ralph
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org