>>>d) Bringing PL/Java into core will force a consistent documentation
>>>and, I imagine, a chapter of it's own in the main docs. I'm happy
>>>to write most of it but English is not my native language. Whatever
>>>I put into print will always benefit from a review.
>>
>>There is nothing stop'ng a chapter being added now,
>
>
> Actually there is: We don't ship documentation for software that we
> don't ship.
How about we start a new standard extensions manual on pgFoundry, and
give the documentors from all the main extension projects commits on it.
That way it's all in one place :)
Or at least a PL's manual...
Chris
