commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: [ALL] @author tags (was Re: DO NOT REPLY [Bug 37028]<snip/>)
Date Thu, 13 Oct 2005 21:51:50 GMT
On Wed, 2005-10-12 at 11:49 -0400, Rahul Akolkar wrote:
> On 10/12/05, bugzilla@apache.org <bugzilla@apache.org> wrote:
> <snip/>
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=37028
> <snap/>
> > ------- Additional Comments From sebb@apache.org  2005-10-12 16:28 -------
> <snip/>
> > BTW, I'd rather not have been added as an @author - besides, I thought the ASF
> > are not keen on @author tags?
> <snip/>
> 
> That is probably the consensus in theory, in practice, its project dependent.

IMHO all these are true. 

the ASF isn't keen on author tags and the consensus is that these are
best left off. the older components tend to have @author tags and i
generally continue to add ones (crediting the ASF to give an url back to
the foundation) in components that generally have author tags. 

author tags are not a good way to credit contributions. they've been a
source of difficulties in the past (an author may not like the way the
design of a class has evolved, for example). the maven generated
contributor lists are better in many ways.

but i don't feel strongly enough about author tags to veto commits with
them (and have never seen anyone else do so).

contributions must be credited in commit messages. (this creates a
public record of the contribution.)

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message