Re: [DOCS] Contrib modules documentation online - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [DOCS] Contrib modules documentation online
Date
Msg-id 46D6CECF.7010207@dunslane.net
Whole thread Raw
In response to Re: [DOCS] Contrib modules documentation online  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers

Peter Eisentraut wrote:
> Am Donnerstag, 30. August 2007 15:26 schrieb Tom Lane:
>
>> I thought a large part of the desire was to improve the visibility of
>> the contrib docs, ie, put the docs under the noses of people who have
>> *not* installed or even heard of the modules.  So "it's not in the docs
>> unless you installed it" seems counter to the point.
>>
>
> I thought the point was to make the extensibility features of PostgreSQL more
> usable so people would be more inclined to use them.  The assumption being
> that the problem is not finding things but the hesitation against
> using "unofficial" things.  Moving everything to the main blob of things
> seems to go against that idea.
>
> So perhaps some market research is required to clarify the actual requirements
> and goals.
>
>

The idea that seemed to gain traction last time this was discussed was
to treat the contrib modules as standard, included in the core
distribution as examples of how modules work, and as modules that have
moderately wide use (not sure how true that is of all of them, but I
don't see any great point in pushing them out.) Quite apart from
anything else, keeping them part of the main distribution helps us to
validate the module process via buildfarm etc.

So this isn't just "moving everything to the main blob of things".

If you want to pay for market research then feel free ;-)

cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the
Next
From: "Gabor Szabo"
Date:
Subject: Re: testing more than one configuration on a single build machine