shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalle Korhonen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SHIRO-168) Remove all @Author tags
Date Sun, 30 May 2010 08:53:36 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kalle Korhonen resolved SHIRO-168.
----------------------------------

    Fix Version/s: 1.1.0
       Resolution: Fixed

> Remove all @Author tags
> -----------------------
>
>                 Key: SHIRO-168
>                 URL: https://issues.apache.org/jira/browse/SHIRO-168
>             Project: Shiro
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 1.0.0
>            Reporter: Kalle Korhonen
>            Assignee: Kalle Korhonen
>             Fix For: 1.0.1, 1.1.0
>
>
> On Fri, May 21, 2010 at 7:49 AM, Alan D. Cabrera <list@toolazydogs.com> wrote:
> > Usually, Apache projects don't have author tags.  I actually can't recall any project
that does.  There's a number of good reasons for this.
> > -  the people who worked on a file can easily be discovered via the SCM system
> > - after a while others may modify the file and then the list becomes a bit confusing
> > - removing individual author tags strengthens the code's affinity to the community
> > A good tag might be
> >  @author The Apache Shiro Project (shiro-dev@incubator.apache.org)
> > Up to you guys but I think they should be removed.  Just my 2 cents.
> Easier to make sure they don't exist at all than use a common tag.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message