public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joshua D. Drake <[email protected]>
To: Gregory Stark <[email protected]>
Cc: Josh Berkus <[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:27:09 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <C11F9B25.131C6%[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Gregory Stark wrote:
> Josh Berkus <[email protected]> writes:
> 
>>> I was actually hoping for more feedback on the content itself. I'm
>>> still not clear if it's supposed to be "developers only - to the
>>> exclusion of users" or "developers only - but accessable to anyone".
>> It should be readable by everyone, but editable only by authorized users.
> 
> 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. 

I don't agree, you should also look at the recent post and fork by one 
of wikipedia's co-founders. The developers wiki should only be edited by 
authorized users.

Now, getting authorized should be easy as reasonably possible, but 
having a wholesale editing orgy on the wiki responsible for tracking 
postgresql developer information is not a good idea.

Joshua D. Drake


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/

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], [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