Hi all, we have the same policy of "no author tags" in Cocoon. Even if @author tags are there to say "this code, and the bugs there in, are responsability of ... " and not "this code belongs to ... " as it has been interpreted, an SVN log or SVN blame will give the same (and better) information to the developers, while the plain user that don't look at SVN history should be redirected to the users mailing list.
Simone Emmanuel Lecharny wrote: > Thorsten Scherler wrote: >> On Fri, 2008-09-12 at 23:30 +0100, sebb wrote: >> >>> On 12/09/2008, Ryan McKinley <[EMAIL PROTECTED]> wrote: >>> >>>> How do you feel about removing the @author tags from class >>>> headers? How >>>> about not allowing them as general policy? >>>> >>>> In my opinion, this helps things feel more like community >>>> development... >>>> we can give credit through a "who" page and callouts in a >>>> CHANGES.txt file. >>>> >>>> >>> Agreed. >>> >>> Per >>> http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_09_22.txt >>> >>> >>> "Recommend strongly that @author is avoided; but leave it to each PMC >>> to make the final call with their respective communities" >>> >> >> How about >> @author Droids community >> > We are using @author <a href="mailto:[EMAIL PROTECTED]">Apache > Directory Project</a> > at directory. It redirects code readers to the directory ML, which > seems to be ok. > > But this may be just is... > > 0.2cts. > -- Simone Gianni CEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
