straightening out the website infra

[Joe Schaefer <jo...@yahoo.com>]

It's been a while since the website situation has been
discussed, but I feel like it's time to have that conversation
again since there hasn't been any progress on that front.

The Infrastructure Team has a goal of migrating all websites
to either the new CMS or to svnpubsub by year's end.  There's
currently almost 100 tlp's that will need to make the needed
changes to their website infra.

I'd like to get Thrift sorted soon so I can move on to other
projects that will need assistance in migrating.  Looking over
your existing solution, if you wish to keep things pretty much
as-is the simplest thing to do is to adopt svnpubsub.  Commits
to the build portion of your tree will appear automatically
on the live site- no more waiting an hour or two to rsync after
manually svn upping the thrift dir on people.apache.org.

If you want to use the CMS instead, you'll get instant publication,
automated builds, and an easy-to-use web interface for editing,
without giving up the fact that the site sources will be in svn.
The downside is that there would be work involved for someone to
port the existing content to django templates and markdown content,
tho even that is negotiable.

So those are the options.  More information on the CMS and svnpubsub
is available at http://www.apache.org/dev/cms.html and 
http://www.apache.org/dev/cmsref.html .

HTH