I'm willing to let whoever does the work make the call. My only hesitation about the git logs is that they might not capture the IBM folks who worked on LotusXSL before it was donated to Apache as Xalan, and probably has no record of the Sun folks before compilation was merged into Xalan. The author tags may have those people.
Courtesy/tradition/convenience tradeoffs... -- /_ 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: Gary Gregory <garydgreg...@gmail.com> Sent: Sunday, July 2, 2023 12:11:55 PM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Suggestion: avoid adding @author tag to javadoc Removing the tags is a trivial serach and replace task. My simple view is that authorship is transferred to the pom.xml. For me personally, a non-detailed entry is enough. For others that want their footprints recorded, the proper path might be to scan the git log for all the files that person touched since day one and list those in the description. Gary On Sun, Jul 2, 2023, 10:16 Mukul Gandhi <muk...@apache.org<mailto:muk...@apache.org>> wrote: Hi Gary, On Sun, Jul 2, 2023 at 6:20 PM Gary Gregory <garydgreg...@gmail.com<mailto:garydgreg...@gmail.com>> wrote: > > In (requires login and proper rights) > > https://whimsy.apache.org/board/minutes/Confirming_that_the_current_stance_on__author_tags_as.html > > I quote the Apache Board minutes: > > "per Greg's email message of February is still appropriate > (Recommend strongly that @author is avoided; but leave it to > each PMC to make the final call with their respective > communities.). > > This was confirmed." > > Well, the way I see it, nothing is required of us to happen, but I do not see > why we would go against a STRONG recommendation. Thanks for the details. I agree with you. I guess that, this activity needs to be done a bit carefully. From a technical point of view, I guess, if @author tags need to be deleted from XalanJ .java codebase files, then these actions need to be consistent across XalanJ's all the .java codebase files (that is, all XalanJ .java codebase files may need to be cleared of these details). But I guess that, this may not be trivial task. After clearing all these @author tags, we may need to test XalanJ implementation and look whether XalanJ javadocs appears nice (and XalanJ team may need to certify that, XalanJ implementation is fine after these actions). Also I guess, assuming all @author tags from XalanJ codebase get deleted, then there needs to be a place perhaps somewhere on XalanJ site mentioning, who all are contributors to XalanJ project (I guess, you could be one of the main persons to determine this information, and to put this information together on XalanJ site). I guess, its nice for a public site of a software project like XalanJ, to have this information (I've observed that, many of the ASF projects sites have, information like "who we are", "who's involved"). I also personally feel that, XalanJ .java codebase files may be having @author tags referring to original authors of XalanJ codebase. As a courtesy to these people, I guess the @author tags mentioning these people's references may be retained. IMHO, the current XalanJ team is maintaining codebase donated by these kind persons. I personally, feel pride with this activity :) I'll leave it to you, and persons like Joseph Kesselman, to decide about this topic for XalanJ and conclude this activity further. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org<mailto:dev-unsubscr...@xalan.apache.org> For additional commands, e-mail: dev-h...@xalan.apache.org<mailto:dev-h...@xalan.apache.org>
