Re: Managing the community information stream

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jim Nasby <decibel(at)decibel(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Managing the community information stream
Date: 2007-05-12 22:13:02
Message-ID: 200705122213.l4CMD2i16672@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Nasby wrote:
> On May 6, 2007, at 8:18 AM, Andrew Dunstan wrote:
> > Oh, the answer to Bruce's question about when to create a feature
> > item? You could well do it at the time when today you create a TODO
> > item. However, we might even do better. For example, we might well
> > add feature requests that are denied. That would help people to see
> > if something has been proposed before.
>
> The problem with our current TODO process is that whether an item
> makes it onto the list is essentially determined by did the idea
> catch a committer's attention, and did that committer happen to think
> it was a good idea. That sets the bar pretty high for getting stuff
> on the list (which you need for a simple list like TODO), but it also
> means it's very subjective. (Of course 98% of the time that committer
> is Bruce, but I don't think that matters here...)

Users often request items be added to the TODO list, and I usually comply.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-05-12 22:13:41 Re: Managing the community information stream
Previous Message Bruce Momjian 2007-05-12 22:06:56 Re: plperl vs. bytea