In general @author tags are discouraged Apache wide IIRC but I don't have a URL for that. Over in the Commons project, we not only stopped using them, but I've removed most of them. The tags are usually misleading because that's usually never the only person who touched the file. You then get into games about what the threshold for adding a name is, and that's a waste of time IMO.
Instead, authors get credit in the pom.xml, and in changed.xml for each action element which are used to generate release notes. And that's a much better reflection of who did what. My suggestion is that we do the same in Xalan-J. 2c, Gary On Sat, Jul 1, 2023, 05:17 Joseph Kesselman <kesh...@alum.mit.edu> wrote: > 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 >
