public inbox for [email protected]  

help / color / mirror / Atom feed

From: Gregory Stark <[email protected]>
To: 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 20:40:04 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <C11F9B25.131C6%[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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. 

Experience shows that most people are cooperative most of the time. If there
turns out to be particularly contentious areas you can restrict access to
those areas to authorized users or ban ip addresses.

I've already put some stuff up there. I didn't plan to, but when I was
browsing I had ideas and the ability to add content was just one click away...

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.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]
  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