Message-ID: <408F0752.4@metatrontech.com>
Date: Tue, 27 Apr 2004 18:22:26 -0700
From: Chris Travers <chris@metatrontech.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Tim Conrad <tim@timconrad.org>
Cc: Josh Berkus <josh@agliodbs.com>,
	"Marc G. Fournier" <scrappy@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: Upcoming Features WAS: What can we learn from
References: <200404262213.44601.jm@poure.com>
	<20040427165746.GA1873@external.timconrad.org>
	<200404271030.28173.josh@agliodbs.com>
	<200404271039.52552.josh@agliodbs.com>
	<20040427174922.GA35932@external.timconrad.org>
In-Reply-To: <20040427174922.GA35932@external.timconrad.org>
Content-Type: multipart/mixed; boundary="------------040301050704070604080507"

This is a multi-part message in MIME format.
--------------040301050704070604080507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tim Conrad wrote:

>On Tue, Apr 27, 2004 at 10:39:52AM -0700, Josh Berkus wrote:
>  
>
>>Tim, Folks:
>>    
>>
>>>I guess there's a perception that we are "above" the marketeering of MySQL
>>>and Microsoft, where features are promised as much as 6 years before they
>>>appear, or are heavily publicized while still in alpha.   So the most you'd
>>>be likely to get the community to commit to is maintaining a list of
>>>easy-to-read "Major Features in Development".
>>>      
>>>
>>Actually, I really like this idea.  It could go like:
>>
>>Feature				Lead			Status	
>>Improved Memory Use		Jan Wieck		Complete, Committed for 7.5
>>HA M-S Replication		Jan Wieck		Alpha testing
>>PITR					Simon Riggs	Early Development
>>Tablespaces			Gavin Sherry	Late Development
>>Integrated pg_autovacuum	Matthew O'Con.	Planning
>>Server Clustering		None			Developer Needed
>>etc.
>>
>>As well as giving the press something to look at, this would give programmers 
>>and corporate sponsors an idea of where their time/money would be of use.  
>>And it could put to bed the myth that we're not constantly improving.
>>    
>>
>
>This suggestion would be good. Something that's not super-detailed
>and not super-technical. Also stuff that's on the 'todo' list that
>is certianly long-range goals as well - just so people are aware
>that it's something that the 'group' is aware of as well as a need.
>
>  
>
The big issue I see with this is maintenance.  Ideally, it would be 
handled in a DB-driven web app and maybe even tied to the TODO (when an 
item is listed as committed, the item gets the  leading - in the TODO?).

I would be happy to contribute programming time, but I would need to 
leave the maintenance to others.

Best Wishes,
Chris Travers

--------------040301050704070604080507
Content-Type: text/x-vcard; charset=utf8;
 name="chris.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="chris.vcf"

begin:vcard
fn:Chris Travers
n:Travers;Chris
email;internet:chris@metatrontech.com
x-mozilla-html:FALSE
version:2.1
end:vcard


--------------040301050704070604080507--