There's a thread starting on [email protected] about the requirements for a CMS for the ASF. Here's a snippet from Paul:
On Sun, May 24, 2009 at 9:44 AM, Paul Querna <[email protected]> wrote: > > Yeah, so, here is the kicker. We run *.apache.org on a single > t2000. Granted, it is a beefy machine, 32 cpu/32gigs of RAM etc. > However, it by itself could not cope with us switching to *any* CMS > right now. > > I talked to the mozilla.org guys -- they run 10 machines behind a > caching load balancer for drupal -- we have nothing like that (nor the > budget, heh, heh). Performance is all relative. > > I think the hardest semi-requirement for any CMS we could use, is the > ability to generate static file exports. > > We either need something that does cross-datacenter replication (eu & > us), or something that generates static files that we can rsync to eu > & us. If it does replication and not static exports -- whatever is > running on the edge servers needs to be doing _really_ good caching. > > I believe for the foundation and service to projects, we do need some > kind of WYSIWYG type CMS -- I'm just not sure what we want exists :) > > It tends to get bike-shedy pretty quickly talking about > wordpress/drupal/typo/other-FOTM-CMS, but we do need something sooner > or later. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com
