Re: [HACKERS] Increased company involvement

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org>, Dave Held <dave(dot)held(at)arraysg(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Increased company involvement
Date: 2005-05-02 17:22:49
Message-ID: 20050502142051.M53065@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

On Mon, 2 May 2005, Bruce Momjian wrote:

> Bruce Momjian wrote:
>> Dave Held wrote:
>>> Well, you make Postgres sound like a very democratic community, but
>>> I'm afraid this is a fairy tale. Aren't the people who approve
>>> patches exactly the in group that you claim doesn't exist? Aren't
>>> they the people that you need buy-in from to really contribute to
>>> Postgres? The reason I make this point is because I know what a
>>> democratic development community really looks like, and the Boost
>>> community is one such example. That truly *is* democratic, because
>>> decisions are made as a group, and no fixed subset of members has
>>> an overriding veto. The group has moderators, but they exist only
>>> to moderate discussion on the mailing lists. I'm not saying that
>>> it is bad that Postgres is not democratic. Postgres is a totally
>>> different kind of beast than Boost, and probably benefits from
>>> having a few people ultimately decide its fate. But let's call a
>>> spade a spade and not pretend that contributors don't have to get
>>> buy-in from core.
>>
>> Really? You have a different perspective than I see. I have seen
>> patches be accepted that had no core buy-in. We accept patches based on
>> group feedback, not some closed approval process.
>
> Let me also ask for you to provide an example of the behavior you
> describe.

How many patches have you "applied" thinking they were good/safe, only to
have Tom jump on top of you and either require changes, or yank them
completely?

As far as code submissions are concerned, Tom has pretty much been "final
arbitrar" (not that I'm against that, I think its required to keep the
code 'clean') ... those with cvs commit privileges are a bit higher on the
totem, but they've already been "through the fire" with Tom, else they
would't have those privileges ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Bruce Momjian 2005-05-02 17:28:46 Re: [HACKERS] Increased company involvement
Previous Message Bruce Momjian 2005-05-02 17:17:16 Re: [HACKERS] Increased company involvement

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-05-02 17:23:02 Re: pg_locks needs a facelift
Previous Message adnandursun 2005-05-02 17:20:51 Re: Feature freeze date for 8.1