On 05/21/2010 12:20 PM, Foster, Dawn M wrote:
I monitor all of those as well via the RSS feed. If catching something and reverting it going to be the plan of record, so be it. Please document that as the POR somewhere. For the record, I'm against it as I believe it to be an unwarranted security risk. On to other concerns.On May 21, 2010, at 12:06 PM, Elliot Smith wrote: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 just don't see this as being as issue. Several of us monitor all of the wiki recent changes, and I'm sure that the documentation team watches their pages. We'll catch anything and get it reverted quickly on the off chance that something happens. The community collaboration and ease of use / updating on the wiki outweighs any potential security risk.
Ryan
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
