We disagree strongly; I would say this essay should be posted periodically to *any* git development group's list. And frankly, your complaining about "bad practice" (as opposed to bad result) without offering an actionable alternative called for this reminder.
Pronoun: Valid but nitpick. Breaking the stereotype is a valid inclusive practice; if you're embarrassed that's a teaching moment since you should be asking yourself why you wouldn't be objecting as strongly (if at all) if "he" had been used. In any case, since this is a direct quote I decline to tamper with it; what you do if/when you re-quote it elsewhere is up to you. Style is important, but content matters more. Quoting Steve Boies, "Make it work. Make it good. Make it great." Implied: In that order of priorities. -- /_ 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: Tuesday, October 17, 2023 6:05:16 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Quoting some good advice on git/jira management Joseph, Thanks for the reminder, however, it does not belong to dev@xalan list. It is especially painful to read all this while both my JIRA issues and PRs are effectively ignored. I know "everyone's time is limited, and so on", however, at the same time, I would prefer if the committers/PCM could recognize the contributions in form of PRs, issues, answers on the mailing list rather than just posting periodic "general OSS comments". >but a guarantee that she will never contribute again and use her time I would suggest using inclusive wording instead of she/her only. I will be embarrassed if people address me with a she/her pronoun. Vladimir
