On 12/11/2012 3:30 AM, Jörn Kottmann wrote: > Should we switch to the new CMS with markdown? We currently use a fairly old system for our site generation. It has a significant degree of automation (in the form of Velocity macros) that do things like handle the hard-to-update pages, such as the download page. It also makes use of css for "styling" the web pages consistently.
See for instance: https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/xdocs/stylesheets/project.xml and https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/stylesheets/base.css I think to move to CMS might align us better with where many sites are going, but I'm not sure how much effort it would take to bring over these capabilities into that approach. I also don't (personally) feel the current approach is that difficult to continue with, at least for now. So I'm inclined to work on other things :-) . > Any opinions on how we should migrate the website? I put in a Jira for fixing the website (no "migration" is needed - we're already using svnpubsub (mostly). It should be pretty easy. -Marshall > > Jörn > > On 12/10/2012 11:13 AM, Thilo Goetz wrote: >> FYI. I thought we were using svnpubsub? >> >> --Thilo >> >> >> -------- Original Message -------- >> Subject: The bitter end of rsync-backed site management is coming Jan 1. >> Date: Sun, 9 Dec 2012 18:17:48 -0800 (PST) >> From: Joe Schaefer <[email protected]> >> Reply-To: Joe Schaefer <[email protected]> >> To: Apache Infrastructure <[email protected]> >> >> >> >> NOTE: If your project's site is using the CMS or svnpubsub >> right now you may disregard this note. >> >> If you project is listed below, you have yet to migrate your >> site to either the CMS or svnpubsub, which becomes mandatory >> starting January 1. This note will serve as your FINAL reminder >> to start the process of filing a JIRA ticket with INFRA to >> request a migration to one of those two options prior to >> January 1, or face a hasty unannounced withdrawal of support >> for your website during the month of January upon processing >> of all remaining timely outstanding requests filed before Jan 1. >> >> Thanks for your diligence in this matter, further questions >> may be addressed to [email protected]. >> >> SANTA'S NAUGHTY LIST: >> activemq.apache.org >> apr.apache.org >> archive.apache.org >> buildr.apache.org >> click.apache.org >> commons.apache.org >> db.apache.org >> directory.apache.org >> favicon.ico >> felix.apache.org >> forrest.apache.org >> geronimo.apache.org >> hadoop.apache.org >> hbase.apache.org >> hc.apache.org >> hive.apache.org >> jackrabbit.apache.org >> jmeter.apache.org >> juddi.apache.org >> karaf.apache.org >> lenya.apache.org >> maven.apache.org >> ode.apache.org >> openjpa.apache.org >> openwebbeans.apache.org >> perl.apache.org >> pig.apache.org >> poi.apache.org >> portals.apache.org >> roller.apache.org >> santuario.apache.org >> shiro.apache.org >> sling.apache.org >> spamassassin.apache.org >> struts.apache.org >> synapse.apache.org >> tapestry.apache.org >> tcl.apache.org >> tiles.apache.org >> turbine.apache.org >> tuscany.apache.org >> uima.apache.org >> velocity.apache.org >> whirr.apache.org >> wiki.apache.org >> ws.apache.org >> xerce s.apache.org >> xml.apache.org >> xmlbeans.apache.org >> >> >> > >
