On Tue, Apr 14, 2009 at 11:55 AM, Jorge G. Mare <koki@xxxxxxxxxxxxx> wrote: > I would like to have a single place with all the accurate and up-to-date > information about Haiku as much as you do. But this is open source, and > you cannot force people to do one way or another. No matter what you do, > there will always be those who prefer to do their thing, and that's a > natural part of the ecosystem. I think you just gotta learn to live with > that. :) But, you can give them an "outlet" for their desire to create, along with attribution for their contributions, and that can help to keep it more centralized :) It is likely intimidating to ask for editing permission for content that can/should be community maintained in the first place, and I believe that granting that role to registered users by default may start to change this behavior. But also, if they don't realize they can edit the content in the first place, then it won't help much. >> In the meantime, I recommend we start tagging the current website >> content that needs to be updated or consolidated so that those who do >> want to work on that project when the time is right will be able to >> locate the content that is in question more easily. >> > > I suppose by content you mean documents? Also, how would you want to tag > the documents? Do you want me to add an extra "Needs update" field for this? I was thinking we can just agree on a standard tag for putting into the "tags" section of the page at the top, that we can then search on. Something like "needsupdate" or "needsreview", etc. It's a method I've seen used to identify stale, or inaccurate documents on other sites, so that "cleanup" crews can come through and fix the issues as time permits. Just a thought, it would be similar to adding TODO's to source code that can be searched for later... - Urias ----------------------------------------------------------------------- haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List