On 19/11/12 20:44, Rob Vesse wrote:
My bad as usual ;)
Our internal policy is to have @author added so my Eclipse is configured
that way, thus I have to remember to explicitly remove them
It wasn't you ... when deep in the DAML+OIL code there are people's
names who are no longer active here.
(and I was aware I was swinging the ax(e) through code with @author on
it - I could see how it might feel like stepping on toes)
So let's remove @author as and when taking a pass through a package or
file. There are quite a lot of files with them on.
Andy
Will try and do this in future,
Rob
On 11/19/12 12:35 PM, "Stephen Allen" <sal...@apache.org> wrote:
+1
I agree about no @author tags, they tend to say who wrote the initial
version of the class. As long as we have SVN history to identify who we
might ask if we have a question about some code fragment, that is good
enough for me.
-Stephen
On Mon, Nov 19, 2012 at 3:23 PM, Andy Seaborne <a...@apache.org> wrote:
Do we want a policy about @author tags and other comment metadata about
authorship?
Personally, I'd like to see none at all - they age badly and maybe they
put off outside contributors to the code.
(I've just been in some very old code and while it's an interesting
history exercise, it's not very useful. I have some time ago removed
any
@author with my name on in ARQ, TDB etc.)
Thoughts?
Andy
