[
https://issues.apache.org/jira/browse/JCLOUDS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978748#comment-13978748
]
Jeremy Daggett commented on JCLOUDS-546:
----------------------------------------
+1 The community is responsible for the codebase as a shared collective. If you
search for "remove author" in JIRA, many of the projects have gone this route.
Git annotate/blame and history will tell you who changed what and when.
> 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)
