There literally wasn’t a problem.
Until the person that asked for the correction literally assumed that said dev was assuming. Since thats what they said in their comment.
So I can understand being a little pissy at someone pointing to you and accusing you of assuming something. It’s stupid.
I may have been a little irritated too if someone accused me of assuming something. I wouldn’t have reacted the same, but I would have been clear that I in no way assume anything related to gender identity.
If the person wouldn’t have put that assumption into their comment, the change may have been more likely to happen.
Instead they assumed something and got push back which turned into the scene we see now.
Ass u me… I mean it’s pretty clear.
Exactly this.
Just because you wrote your documentation a certain way, doesn’t automatically mean that you feel a certain way about any particular group, or that your users are primarily a certain gender. It may just be writing what pronoun you are most familiar with.
In this particular case, we can see that the author didn’t exactly make the best case for himself.
However, there was never a problem to begin with until the person that requested the change also accused the the author of assuming that the user/dev of the OS is male.
If that little bit of accusation would have been left out, and they just put a note like “grammatical correction” it may have just been accepted and moved on. Instead they asked for a change while accusing the author of feeling a certain way.