Welll
kfogel@collab.net schrieb:
> Greg Stein <gstein@lyra.org> writes:
> > Precedent sets policy. It seemed a good number of us believed in not putting
> > our names in the code, so it was effectively policy. We don't write down
> > everything about how to code -- there are dozens of unwritten rules.
> >
> > Have we written down "check in often; avoid sweeping changes" ? Nope. It is
> > just something we do, but I would put forward that it is policy.
>
> Good point, yeah.
>
> > It is a poor precedent to have personal names in a team effort. And that is
> > what we're doing here: acting as a team.
> >
> > I've mentioned it elsewhere, but names in code can engender fiefdoms ("don't
> > touch that; it's my code!"). That is the single-most destructive thing that
> > occur to a team and to the codebase that is being built. The potential cost
> > of that outweighs any minor benefit that I could think of for having names
> > in there.
> >
> > [ note: I'm not suggesting Alex has the fiefdom point of view; I'm concerned
> > about the precedent ]
> >
> > Yes, I've written large chunks of code. It actually upsets me that others
> > aren't in there all that much (Joe Orton thankfully assists!). I avoid
> > putting my name in there because I *want* others to work on it. It isn't
> > really a good thing for the team/code to have a single author on critical
> > pieces of code. I'm confident with my code, but realistic enough to know
> > that it would be best to have more people contributing to those portions.
>
> Okay. Alex, I think Greg's points are good ones; would you mind
> reconsidering?
Well, I will remove the @author tags. Still not my private opinion. But I can
live with it. So shall it be...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:35 2006