public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Martijn van Oosterhout <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Gregory Stark <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Neil Conway <[email protected]>
Cc: Dave Page <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [HACKERS] Developer's Wiki
Date: Sun, 17 Sep 2006 14:25:16 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <C11F9B25.131C6%[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Martijn van Oosterhout <[email protected]> writes:
> On Sat, Sep 16, 2006 at 09:15:24PM -0400, Tom Lane wrote:
>> Fortunately, none of the real developers would have to pay any attention
>> to any such page ... and you can bet they wouldn't.

> If someone wants to spend an afternoon putting up a coherent
> description of their wishlist item complete with possible problems and
> solutions, then I don't see why we should stop them.

Because if they're willing to put any actual effort into it, the right
way is to post that same item to the mailing list where it can be
discussed.  If it survives such discussion (very possibly in a modified
form) *then* it belongs on a TODO list.  The first problem with a wiki
TODO is that it will not reflect any sort of community consensus, only
the opinions of whoever edited the page last.  The second problem is
that setting it up represents a unilateral attempt to redefine (bypass?)
the community's design/development process, which is a process that has
served us well for many years and is not showing any signs of being
broken.

			regards, tom lane

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