As I say, only mild disagreement; if someone wants to aggregate the credits I won't object. I still like my thought of doing that by package, but if that's too much effort, sigh. (I may also be biased by the fact that some things, such as DTM, are largely my fault.)
-- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Joseph Kesselman <kesh...@alum.mit.edu> Sent: Saturday, July 1, 2023 5:17:40 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Suggestion: avoid adding @author tag to javadoc Mild disagreement. I like seeing the reminders of who contributed to what parts of the system, and some of that history predates our moving to Git (or even the code's contribution to Apache). I think authors deserve credit. But I'm biased; I worked directly with many of those people. I suppose the information could be extracted and summarized into a "credits page", if someone wanted to spend the cycles on that. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Vladimir Sitnikov <sitnikov.vladi...@gmail.com> Sent: Saturday, July 1, 2023 4:39:39 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Suggestion: avoid adding @author tag to javadoc Hi, I suggest to stop adding @author tags. The relevant information exists in Git, and it is hard to tell when @author tags should be added, updated, and removed. See reasoning in https://stackoverflow.com/a/17271433, https://github.com/junit-team/junit5/issues/914#issuecomment-328078934 What do you think? Vladimir -- Vladimir
