Message-ID: <47597CF8.20307@dunslane.net>
Date: Fri, 07 Dec 2007 12:03:52 -0500
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: "Joshua D. Drake" <jd@commandprompt.com>
CC: Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>,
	pgsql-hackers@postgresql.org, pgsql-docs@postgresql.org
Subject: Re: [HACKERS] Uniform policy for author credits in contrib
	module documentation?
References: <3393.1196917132@sss.pgh.pa.us> <4758E528.2090507@agliodbs.com>
	<12069.1197008470@sss.pgh.pa.us>
	<47596FFE.9090903@commandprompt.com>
In-Reply-To: <47596FFE.9090903@commandprompt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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