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.
--
Jody Garnett
On 22 April 2016 at 14:21, Ben Caradoc-Davies <b...@transient.nz> wrote:
> In fact, I think we should *require* rather than just encourage the use of
> @author.
>
> Kind regards,
> Ben.
>
>
> On 23/04/16 09:14, Ben Caradoc-Davies wrote:
>
>> I like the Javadoc @author tag. We should encourage its use on all new
>> classes, and additional @author tags for any substantial contribution to
>> an existing file. @author tags are useful not only for provenance but
>> for seeking help; successive changes can make @author tags easier to use
>> than git blame. @author tags also allow us to respect the moral right of
>> attribution.
>>
>> Kind regards,
>> Ben.
>>
>> On 23/04/16 08:42, Jody Garnett wrote:
>>
>>> I like having headers that capture the initial author - since that has
>>> been
>>> very helpful in sorting out any questions during our incubation and
>>> subsequent external code audits.
>>>
>>
>>
> --
> 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
