Re: [DOCS] Uniform policy for author credits in contrib module documentation? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [DOCS] Uniform policy for author credits in contrib module documentation?
Date
Msg-id 47597CF8.20307@dunslane.net
Whole thread Raw
In response to Re: [DOCS] Uniform policy for author credits in contrib module documentation?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: [DOCS] Uniform policy for author credits in contrib module documentation?  ("Selena Deckelmann" <selenamarie@gmail.com>)
List pgsql-hackers

Joshua D. Drake wrote:
> Tom Lane wrote:
>> Josh Berkus <josh@agliodbs.com> writes:
>>> Historically, the only way to troubleshoot some of the contrib
>>> modules was to e-mail the author.  If people think that we've
>>> reached a standard that everything in /contrib is now
>>> well-documented and supported by the general community, the I
>>> suppose we don't need contact information.  I'm not so sure myself.
>>
>> I do not think that we should encourage people to mail the authors first
>> rather than pgsql-bugs.  For one thing, a lot of those addresses are
>> dead, and some of the ones that aren't don't respond especially fast.
>>
>> If the community-at-large can't handle a bug, we certainly have enough
>> institutional memory to try to contact the original author, even if that
>> address isn't in the SGML docs.
>>
>
> Perhaps the at a minimum the email goes in the commit?
>

I don't see any reason, unless we're going to start doing that for all
contributions. 'contrib' is a serious misnomer anyway, and there's no
reason to think in general that the original author is specially
responsible for any of it. I think Tom's point is entirely valid.

cheers

andrew

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: [DOCS] Uniform policy for author credits in contrib module documentation?
Next
From: Bruce Momjian
Date:
Subject: Re: Release Note Changes