avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <paul_hamm...@yahoo.com>
Subject Re: [VOTE] Remove all author tags from all source code files
Date Mon, 20 Jan 2003 09:16:42 GMT
Right, you should set at the outset of a project the expectations for @author tags for a project.

Many of us really like seeing out name in headers as it is proof to the claims we make on
resumes.  To wait four years then purge names from headers is shitty.  

How does this work with Krysalis?  Can you expand your community enthusiasm to remove your
name from your org, site, source, pages, credits such that it has peer equivalence to everyone
else who contributes?  Anonimize yourself?  As an aside you, Nicola, have little java contributed
to the Avalon codebase compared to others. It is no skin of your nose if this is taken away.
have willfully accepted patches from others and credited them with author tags as we pushed
in. I'll tell you that this will tail off if there is no name in lights reward for those brave

Is it not time we stopped damaging this community. Oh, and this is damage, you are steam-rolling
over the feelings of others.  It was *completely* unecessary to suggest this.  Just becuase
are PMC chair does not mean you have to invent things to do.  

I am amazed that so many people have voted in favor.  I emplore people to switch their votes.

>     (authors get forgotten, just code remains)


 --- Nicola Ken Barozzi <nicolaken@apache.org> wrote: > 
> Jeff Turner wrote:
> > On Sun, Jan 19, 2003 at 11:34:32AM +0100, Nicola Ken Barozzi wrote:
> > 
> >>I thought that this issue had been addressed, but I can't find the vote 
> >>results, if we had a vote.
> >>
> >>Thus, I'm asking to vote on this issue.
> >>
> >>Do you want that all @author tags and all reference to authors of source 
> >>code files be removed from the files themselves? The information about 
> >>the authors will still be present in commit messages and in the site 
> >>credits.
> > 
> > 
> > I assume this is a majority vote..
> > 
> > -1.
> > 
> > Author info is frequently useful.  Code moves around, and CVS histories
> > get lost. 
> So?
> If a file is moved, or it's so new that the original author is working 
> on it, or it's so old that the community should have gotten hold of it, 
> hence there is no need to have that info anyway.
> > Code gets copied into foreign (non-OSS) codebases.
> It's Apache code, the Apache license and a community author tag is enough.
> > Also, contributors get a kick out of seeing their name in lights.  I
> > remember I did, when I contributed my first OSS patch to Log4j (way back,
> > before it migrated to Apache) and Ceki added my name to Category.java.
> > It is a small - but to some - important piece of recognition we can give
> > to contributors.
> This is another issue. We could decide that Avalon committers do not add 
> author tags but are part of the Avalon Project author tag, and that 
> instead external contributors do get recognition there.
> > Besides, I believe we're all adult enough not to let @author tags get in
> > the way of community code ownership.
> Why taks the risk?
> Moreover, given the above points, it seems that author tags are not 
> needed, and serve only for recognition. In a community project 
> recognition is not based on how many author tags there are, so...

Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message