Re: pgFoundry

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Lamar Owen <lowen(at)pari(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgFoundry
Date: 2005-05-16 17:56:38
Message-ID: 200505161056.38709.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew,

> down, if positioned right, but can help people to see where things are
> going, and where the gaps are. This could in a sense be as simple as
> prioritising the TODO list. Right now anybody who wants to contribute
> and looks at the list has no idea if the item is considered important or
> even if it is still thought to be desirable. There are many changes that
> can be rung on this theme - you would probably want to keep the "roadmap
> process" as light as possible for the cultural reasons you mention.

The substantial problem here is that nobody *wants* to create a roadmap type
document. If you can find a volunteer, it'd be worth discussing -- I can
see a way we can make a "roadmap" without being deceptive about how we get
features.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-05-16 18:07:51 Re: pgFoundry
Previous Message Jeffrey W. Baker 2005-05-16 17:47:53 Re: bitmap scans, btree scans, and tid order