In article <[EMAIL PROTECTED]>, "Berin Loritsch" <[EMAIL PROTECTED]> wrote: >... > 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.
Actually, it defeats many of the purposes of the ASF: * the code has a name associated with it, so who do you think will be sued for patent infringement? e.g. hurts the ASF's intent to indemnify * ten years down the road, the author has moved on, but people still try to get a hold of him for things. this hurts the ASF's intent to provide long-term code ownership Establishing a CREDITS or AUTHORS or something would at least be better, in the sense that it loosens the tie from specific files, yet still gives the ability to have your name recognized. In the httpd group, we credit committers and third-party patch providers in the CHANGES file. The CVS commit logs also have the information, of course. Cheers, -g -- Greg Stein, http://www.lyra.org/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
