| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to Sponsor a Feature |
| Date: | 2008-06-12 07:07:28 |
| Message-ID: | B3EC54DD-6C2E-4C68-BA33-D7D7440E8D5D@gmx.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Smith wrote:
> On Wed, 11 Jun 2008, Andrew Dunstan wrote:
>
>> If we want to help people to sponsor features, then I think we need
>> to deal with subjects like finding someone to undertake the
>> development, the sponsor's relationship with the developer, methods
>> and times of payment, etc.
>
> The bit on the wiki is helpful for developers trying to get a new
> feature implemented but I think that's where its scope ends.
>
> There seem to be occasional person wandering by here that it really
> doesn't help though. Periodically you'll see "I want feature $X in
> PostgreSQL. I'm willing to help fund it. What do I do?". In most
> of those that have wandered by recently, $X is a known feature any
> number of other people want. Good sample cases here are recent
> requests to help fund or implement materialized views, supporting
> queries on read-only slaves, and SQL window support.
>
> I don't think these people need guidance on how to manage the
> project, they need some sort of way to feel comfortable saying "will
> pledge $Y for feature $X" in a way that makes sense on both sides.
That's what I thought, too. That page just needs a different title.
Best Regards
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2008-06-12 10:41:33 | Re: rawhide report: 20080612 changes |
| Previous Message | Bruce Momjian | 2008-06-12 02:36:11 | Re: Overhauling GUCS |