On Thu, May 20, 2010 at 3:28 PM, David Greaves <[email protected]> wrote:
> 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. I think it makes perfect sense to *develop* policy on the wiki, for all of the reasons you mention... I'm less convinced it makes sense to use it to host published, fairly static policy docs that you definitely *do* not want people changing, accidentally or otherwise... > Oh, and most importantly: we can use it today. I could be mistaken, but I thought that the main meego.com site was based on drupal, and that it was possible to set aside portions of meego.com with one or more maintainers... I'm pretty sure that can also be done today. Would it make sense to have something like meego.com/policies that hosts the *approved* versions of the policies, while the drafts are maintained on the wiki? It seems to me that this would simplify the process you proposed, since I don't think you'd need as formal a discussion and approval process... If you don't think it'll simplify the process, I wouldn't worry too much about it... it just looked like the process that you proposed was put in place to deal with the limitations of the wiki system --- and I prefer using the right tools than implementing processes to deal with existing tools. Warren -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
