Torben, I think these are strong arguments and I am now tempted to avoid @author. It seems cleaner and more elegant to me to keep all metadata (authorship, version history, and copyright) outside the source code itself. The downside is that this information is not visible to non-revision-aware consumers (web browsers, search engines) and is lost on export from the revision control system, but the upside is that the code base becomes cleaner and easier to maintain.
Kind regards, Ben. On 23/04/16 11:53, Torben Barsballe wrote: > My thoughts on the @author tag: > I feel like the git commit log gives a clearer and more usefull picture of > this sort of information - You can see the initial author, as well as the > author of any major changes, and can usually get a good idea of who is > currently doing the most work in that area of the codebase (as compared to > someone who authored a class 5 years ago and hasn't touched it since). > The one exception is when stuff gets transitioned between repositories or > other similar bulk import cases. > Conversely, the @author tag is much less maintainable, less enforcable, and > prone to getting out-of-date. > > Torben > > On Fri, Apr 22, 2016 at 2:39 PM, Ben Caradoc-Davies <b...@transient.nz> > wrote: > >> I used to share Andrea's view but, as my confidence grew, I became more >> comfortable seeing @author tags as historical information not an >> assertion of ownership. >> >> On 23/04/16 09:24, Jody Garnett wrote: >>> Andrea had a very reasoned argument for not using the @author tag and >>> started discouraging its use. >>> It amounted to team ownership of the codebase empowering everyone to work >>> on a class, rather than slowing down to seek permission (or even worse >> wait >>> for someone else) to fix a problem. >> >> -- >> Ben Caradoc-Davies <b...@transient.nz> >> Director >> Transient Software Limited <http://transient.nz/> >> New Zealand >> >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with Applications >> Manager >> Applications Manager provides deep performance insights into multiple >> tiers of >> your business applications. It resolves application problems quickly and >> reduces your MTTR. Get your free trial! >> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z >> _______________________________________________ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
