Stefano Mazzocchi wrote:
Leif Mortenson wrote:
Jeff Turner wrote:
Besides, I believe we're all adult enough not to let @author tags get in
the way of community code ownership.
-1
I agree on this. This had come up before as a possible solution to
the problems we
had been having before. I don't feel that removing the author tags
would do anything
towards solving those problems.
I also agree with some ot the other comments about keeping them in to
give credit
where credit is due. I'll admit it is fun to get credit for the hard
work that you put into
a project.
I agree. I would like to keep the author tags in there as well.
Cocoon, for example, does have author tags and everybody loves them and
never created any problem whatsoever.
Can we get back to work together on code instead of creating parties and
find all possible excuses to fight over stuff, please?
I agree with Stefano on this. Framework can be one of the generic
@author places--it defines no functionality.
For any Avalon code that defines functionality (like components and
containers), keep the @author tags. It doesn't harm anything, and
it is good to let people get recognition.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
