Warren Baird wrote: > Seems to me that using a wiki to host a formally controlled policy > document doesn't make a lot of sense - seems like we aren't using the > right tools for the job. > > I suspect that the packaging policy isn't the only place this might come up. > > Should formal policies be hosted on the non-wiki part of the site, > with a few people able to make updates through the CMS? The wiki > could have a page like "Packaging_Policy_Proposal" where proposed > changes are made - the discussion about the proposed changes can be > either in the ML, or in the 'talk' page on the wiki, and when things > are finalized, someone copies the changes to the CMS?
The hosting of the pages was not the part of my proposal I really wanted to discuss :) but yes, I take your point and I did consider this. OTOH a wiki has a 'talk' page; the ability to trivially host 'draft' versions of pages nearby; email notification of changes; and I've proposed a reasonable process that, together with the great audit trail that a wiki offers should trivially identify and allow reversion of any unwanted edits. Oh, and most importantly: we can use it today. If we get unmanageable problems we can use something else. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
