On Fri, 2010-05-21 at 19:11 +0100, Ryan Ware wrote: > On 05/20/2010 11:15 PM, Quim Gil wrote: > > There is a thin line between CMS pages that only some editors can touch > > and protected wiki pages that only some editors can touch. Proposal: get > > first such page ready in the wiki and then we can discuss case by case > > where each one belongs to. > > > > I think the line is a bit thicker than you believe. The problem is that > by default any wiki page can be edited by anyone. In addition, anyone > can start a _new_ wiki page. With the CMS, only a few have either the > capability to edit pages or to create entirely new ones and they are > never by default editable by everyone.
It is possible to protect pages in the wiki so they're not editable by just anyone. That doesn't stop someone creating a bogus page which purports to be official, of course, so that could still be a problem. > > I'd also hate to see us having to decide in an ongoing effort on a page > by page basis if it should end up in the CMS or the wiki. > > Don't get me wrong. The wiki is a great tool and using it go communally > create policy content is the perfectly correct approach since that is > the best collaboration tool we have. However, things that will be > mostly static over time (like policies and security advisories) need a > different home. I think most documents aren't going to be static (and shouldn't be). I'd like to try to get as much as we can in the wiki, where anyone can see it and possibly contribute to it, and find mechanisms to protect "official" documents within that environment. > > Ryan > Elliot -- Elliot Smith Intel Open Source Technology Centre --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
