You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ceki Gulcu (JIRA)" <ji...@apache.org> on 2010/02/21 21:59:27 UTC
[jira] Issue Comment Edited: (LOG4J2-30) Author tags
[ https://issues.apache.org/jira/browse/LOG4J2-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836445#action_12836445 ]
Ceki Gulcu edited comment on LOG4J2-30 at 2/21/10 8:57 PM:
-----------------------------------------------------------
Let's say that author tags remains a question awaiting consensus, with the board leaving the door open for author tags to be adopted or rejected by each individual PMC. With regards to people contacting the author directly upon reading the author's name in a tag, I can confirm that it occurs, but the phenomenon is entirely marginal, at least from my perspective. Receiving an email once every six months (my experience) cannot be considered an issue. Of course, your experience may vary.
Having one's name on a team list both for committers and contributors, is a different way of providing acknowledgment. The team list answers the question "who is working on project foobar?". An author tag answers a different question. "Who wrote java class org.foo.bar.SoylentGreen?". Users will stumble upon authors tags while perusing source code. One does not stumble upon team lists as causally or as often.
As Ralph observes, information about authorship for a given piece of code can be obtained via SVN. But this involves an active command while authors tags placed at the top of each class get as many eye-ball hits as there are readers of that class.
Incidentally, in french copyright law, the author name can never be removed even by the copyright holder. According to french law, one can own copyrighted material but only the author can claim authorship and the publisher can never deny attribution. This is called right of attribution. Contrary to copyright, right of attribution is perpetual. One might pooh pooh the french for various reasons (as I often do) but the distinction they are making between proprietary rights and moral rights is quite interesting. For more details about this topic see http://en.wikipedia.org/wiki/French_copyright_law
was (Author: ceki@qos.ch):
Let's say that author tags is question where there is no consensus with the board leaving the door open for author tags to be adopted or rejected by each individual PMC. With regards to people contacting the author directly upon reading the author's name in a tag, I can confirm that it occurs, but the phenomenon is entirely marginal, at least from my perspective. Receiving an email once every six months, which corresponds to my experience, cannot be considered an issue. Of course, your mileage may vary.
Having one's name on a team list both for committers and contributors, is a different way of providing acknowledgment. The team list answers the question "who is working on project foobar?". An author tag answers a different question. "Who wrote java class org.foo.bar.SoylentGreen?". Users will stumble upon authors tags while perusing source code. One does not stumble upon team lists as causally or as often.
As you observe, information about authorship for a given piece of code can be obtained via SVN. But this involves an active command while authors tags placed at the top of each class get as many eye-ball hits as there are readers of that class.
Incidentally, in french copyright law, the author name can never be removed even by the copyright holder. According to french law, one can own copyrighted material but only the author can claim authorship and the publisher can never deny attribution. This is called right of attribution. Contrary to copyright, right of attribution is perpetual. One might pooh pooh the french for various reasons (as I often do) but the distinction they are making between proprietary rights and moral rights is quite interesting. For more details about this topic see http://en.wikipedia.org/wiki/French_copyright_law
> Author tags
> -----------
>
> Key: LOG4J2-30
> URL: https://issues.apache.org/jira/browse/LOG4J2-30
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Curt Arnold
> Priority: Minor
>
> Logging this as a bug so that it eventually gets resolved.
> From log4j-dev thread "Future development of log4j 2.0"
> On 20/02/2010 12:42 AM, Christian Grobmeier wrote:
> there might be other discussions which could
> lead to frustrations on several sides. I think on discussions like
> having author tags and such.
> On Feb 19, 2010, at 5:57 PM, Ceki Gülcü wrote:
> Author tags is a way of recognizing contributors. Recognition is a
> very important aspect of oss.
> ---
> Author tags have been discouraged by the board, http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt (section D)
> This statement by Dirk-Wlllem van Gulik, then president of the ASF, expands on the rationale:
> http://marc.info/?l=xml-cocoon-dev&m=107787986409413&w=2
> Don't think we need to tackle the issue until there is code someone wants to tag. I'm not planning on tagging any code that I initially develop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org