Re: New Contrib Build?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: New Contrib Build?
Date: 2005-05-12 04:44:48
Message-ID: 26843.1115873088@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Andrew Dunstan wrote:
>> First, I *really* wish we'd call it something else. Contrib conveys
>> "unsupported" to people.

> And that's exactly what it is supposed to mean. We say, these modules
> do not necessarily meet our standards with regard to code quality,
> portability, user interfaces, internationalization, documentation, etc.
> There is certainly a lot of good software in contrib and one could in
> individual cases consider moving them out of there, but contrib is what
> it is.

Which is as it should be, I think. Contrib is essentially the "not
quite ready for prime time" area. If it were 100% up to speed then
it'd be in the core backend already ... while if we required it to be
100% in advance, then it'd not have gotten out there in the first place.

The real issue seems to be that we have a disconnect between what is
presently in contrib and what is on gborg or pgfoundry. There are
certainly many contrib modules that are only there on seniority: if
they were submitted today then they'd have gotten put on pgfoundry.
But I'm not sure that there's much value in an enforced cleanup.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-05-12 05:23:17 Re: Views, views, views: Summary of Arguments
Previous Message Thomas F. O'Connell 2005-05-12 04:34:27 Re: Views, views, views: Summary of Arguments