Kevin Dangoor <[EMAIL PROTECTED]> writes: > A wiki adds to this the ability to link easily to different articles. > I wrote a bit about a wiki for software documentation here: > http://www.blueskyonmars.com/2005/09/27/what-i-want-in-a-wiki-for-software-development/ > > I wanted to raise this for discussion and, hopefully, volunteers who'd > like to work on the app. I am more than 100% booked right now, but an > app like this would be really helpful. > > Thoughts?
Even though I really like those comments -- and I've even posted some for the PostgreSQL docs --, one thing that we have to think about is moderating *and* not starting discussions there. Otherwise we'll end up with pieces of docs here, there and everywhere (ML, Wiki, Tickets, blogs, etc.). Moderation will help keeping the correctness of comments and clarifications (doubts should go to the mailing list and not on the documentation page, it might get something to make it clearer later...). But I really like the idea to the this. Ah! And I'd advise to add a note on every page (currently Trac has it only on the documentation playgroung page...) that all contributions are public domain and if appropriate will be incorporated in the official documentation at any time or might get erased from the page (I believe we'll enhance the official pages with clarifications from one release to the next...). One thing is for sure: there will be the need for a wiki editor, to keep the documentation categorized correctly and to remove old stuff -- and, if moderation is implemented, to approve comments... -- Jorge Godoy <[EMAIL PROTECTED]>
