public inbox for [email protected]
help / color / mirror / Atom feedFrom: Josh Berkus <[email protected]>
To: Gregory Stark <[email protected]>
Cc: [email protected]
Cc: Martijn van Oosterhout <[email protected]>
Cc: Neil Conway <[email protected]>
Cc: Dave Page <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [HACKERS] Developer's Wiki
Date: Sat, 16 Sep 2006 13:09:49 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <C11F9B25.131C6%[email protected]>
<[email protected]>
<[email protected]>
Greg,
> I think the lessons of wikipedia is precisely that you *don't* want to add
> such barriers. You want to let people add stuff pretty much freely. That
> encourages people to get involved and put up information.
The other lesson of Wikipedia is that maintaining wiki quality for a generally
editable wiki requires a full-time dedicated staff. We don't even have any
volunteers who have 4 hours/week to commit to cleaning up the wiki, unless
you're volunteering.
This is *particularly* true of the TODO stuff. We simply don't want Joe User
adding their personal wishlist to the TODOs, and that's exactly what will
happen if the TODO list is world-writable. TODOs should be items which have
been hashed out here on the Hackers list, and the wiki page should list the
specification which is the general consensus.
If we had a "user documentation wiki", then *that* should be world-editable,
but again that would require community volunteers to dedicate to cleaning it
up. The developer wiki is by and for actual contributors.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
view thread (45+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] Developer's Wiki
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox