Peter Donald wrote:
+1 for framework. But having the authors has been valuable over time for knowing who to+1 to remove them from framework which is where the real problem lies.
talk to within the team.
For the rest I would prefer to leave as-is until we migrate all the stuff out. At that point it may be a good idea to re-address the issue with remaining code.
On Sat, 23 Nov 2002 09:18, Leo Simons wrote:
Hi all,
I saw a suggestion come by in that it might be a good idea to remove
author tags from source files as it will help eliminate any community
issues that arise from ego conflicts and/or 'personal playground'
problems. Removing the tags sounds like a very pragmatic way of helping
to remove any perception of code ownership.
The only disadvantage I could see arising from this is that it might
become more difficult to figure out who you need to talk to about a
piece of code you're looking at. I think the solution to that is simple:
indicate the software was authored by the avalon people, and reference
avalon-dev. Whoever wrote that code should be around on avalon-dev :D
As to credit where credit is due....we have a list of contributors for
that, and one can always look at the cvs commits.
Hence I propose we do a global replace of
@author Some Person
(...)
@author Other Person
to
@author <a href="mailto:[EMAIL PROTECTED]";>Apache Avalon
Development Team</a>
Here's a +1 from me.
cheers,
- Leo Simons
I'm learning regexp at the moment but I've so far not succeeded at
writing the perl snippet that should accomplish the above so it'd be
cool if some perl guru out there were to help a little? (if not my +1
indicates I will spend an afternoon or two figuring out how to do this I
guess :D)
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
