Re: 8.2 features status

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Neil Conway <neilc(at)samurai(dot)com>, David Fetter <david(at)fetter(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.2 features status
Date: 2006-08-05 02:30:26
Message-ID: 24339.1154745026@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> As I was saying on #postgresql, the current system works well for a
> small group of developers. I don't think there is any arguing that.

> However, there is a larger group out there, that would likely be willing
> to contribute but we are a bit of a black box, or perhaps we are too
> transparent?? I am not sure which.

Maybe I'm too much "on the inside", but I see the problem the other way
'round: too little visibility of what's being done by people who are not
part of the inner circle of developers.

It's possible that creating a more formal structure would aid these folk
to let the rest of us know what they're doing ... but I think it's at
least as likely that a more formal structure would just drive them away.

> I am actually hoping that jabber.postgresql.org would help that in the
> long run.

Now here I think we might be on the same page. If people pop up on IRC
or jabber or any other communication method and talk about what they're
doing, that fixes the whole problem. I'm for adding anything that
provides an opportunity for people to talk to the community --- I'm not
for trying to force them to talk to the community, 'cause I don't think
that will work very well.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-08-05 02:30:33 Re: 8.2 features status
Previous Message Joshua D. Drake 2006-08-05 02:19:28 Re: 8.2 features status