On 06/28/2010 12:08 PM, Bernd Eilers wrote: > A staging site for OOo on kenai is going to be set up soon but I can > not give any information on how soon that will be at the momment.
1) Please give more consideration to the methods or tools I describe below. They might successfully obviate the need (or perceived need) for the burden of creating or using a CMS. 2) If you are going to re-invent the wheel, please be sure to re-invent a better wheel, not just a newer one or a different one. ;) On 06/28/2010 12:08 PM, Bernd Eilers wrote: > You can learn more about kenai migration at > http://kenai.com/projects/ooo-migration/pages/Home "The move is going to include services like publishing of web content, mailing lists, bugtracking, ... and the existing content of those." Ok. From a software engineering, maintenance and security perspective a monolith should be avoided. So if you are making a framework into which many modules fit, then great. If it is yet another BlackBoard(tm), then please stop and erase the disks now. ;) The technical side of publishing web content can be done here and now using CVS plus a few templates using CSS and SSI. The templates, if they are just a port of the current OOo Look & Feel, can be done in a few weeks -- even allowing for tremendous time padding for meetings and phone tag. The mailing list can be managed by GNU Mailman. Tweaking that to match the current OOo Look & Feel can be done in a few hours. The phase out of the old list manager can be done starting one list at a time, growing to several at a time, over a few weeks, mostly by fiddling with DNS MX entries. The bug tracking can be managed by any ticketing system: RT, Bugzilla, OTRS, Trac or Redmine. Tweaking that to match the current OOo Look & Feel can be done in a few hours. Judicious use of vhosts, links, and stylesheets can provide a unified appearance and the user will experience the whole as a single interface. Migrating the old archives from the old bug tracker and the old mailing lists, can be done over time after the roll out of the new systems. Just lock them read-only and leave them running until the data is successfully copied and transformed. /Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
