[
https://issues.apache.org/jira/browse/JCLOUDS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978773#comment-13978773
]
Chris Custine commented on JCLOUDS-546:
---------------------------------------
Just for the record since it was not easy to find, here are the board minutes
which set the precedent:
http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
Relevant part:
5. Special Orders
...
D. Discussion: copyright ownership
Although initiated due to the current efforts for Spam Assassin,
the board discussed at length the issues and guidelines regarding
copyright ownership for the ASF. It was agreed that all files
should have 1 single copyright to the ASF. Copyrights extend
to the work as a whole, and the ASF must have these. The
use of the CHANGES files should note any "history" regarding
copyrights and that the use of 'author' tags should be
discouraged for this and other reasons.
> Remove @author from javadocs
> ----------------------------
>
> Key: JCLOUDS-546
> URL: https://issues.apache.org/jira/browse/JCLOUDS-546
> Project: jclouds
> Issue Type: Task
> Components: docs
> Reporter: Chris Custine
> Priority: Trivial
>
> There is a long standing board resolution that discourages use of @author
> tags in Apache project javadocs. jclouds source also contains @author tags
> attributing authorship to people that are not committers (from the Github
> days). I know its a pain, but it might be a good task prior to 1.8 and maybe
> even a 1.7.x release.
> Hadoop and other projects also have automated checks to flag patches with
> @author tags so that is something to consider down the road.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
