I understand your intentions are noble, but we kinda go back to one of the points the author of the post was making: Has anybody bothered to asked black developers if the terminology alienates them, or makes them feel uncomfortable?
I don't believe it was the technical terminology that caused unwelcoming conditions, but the people in the industry.
And, of course technical terminology _alone_ is not the issue! Totally agree that there is more to be done. I just find it amusing that there is so much pushback on this particular aspect (the naming of the branch). Clearly it is a concern, and it is on the whole a small thing to change. Larger systemic change is of course more ideal, but sometimes the battle starts at the symbolic level and expands from there.
So before I answer, I'm aware that there's a bit of "cognitive dissonance" going on in my head about this topic. One one hand I fully agree with you, but on the other it feels like it's deflecting/trivialising the issue and creates a false sense of accomplishment that will delay the necessary change.
> I just find it amusing that there is so much pushback on this particular aspect
I think push back comes not from attachment to "master" but from the emotions the virtue-signalling crowd causes in people who desire real change. The virtue-signallers are like the kid on a school project who did virtually nothing, and then tried to claimed all the credit once the project was done. It's a bit "hashtag-contribution," but ironically. It awakes a sense of righteousness in people (whether it's misguided or not is another topic) that think this is stupid, useless, and some probably think it's harmful because it pacifies a large group of people with thinking change happened, when it didn't. It's a bit like seeing a broken website, then changing the button colour and calling the website fixed and being done with it.
However, it's like you said, people aren't monoliths. Various people have trigger words. Some people get triggered by "moist," someone in another comment mentioned Jews have the right to be offended by the word "concentration" or the word "camp" (yes, even if it's out of context; master in the case of git is also very out of context to slavery).
I don't think changing the world for the sake of individuals is possible/scalable, but what we should do is try and accommodate them. I'm all for making people included and accommodating them, to a degree in which it doesn't make me feel uncomfortable in; I want to be given the same courtesy.
It feels like Alex from the blog post waited for the world to change, instead of being the change he wants to see. Waiting for the world to change is futile, you can only influence your environment to a degree, and if that doesn't work look for a better one that suits you better. I don't know if Alex did that or not, but it reads as if he was passive until now. I guess better late than never.
> Larger systemic change is of course more ideal, but sometimes the battle starts at the symbolic level and expands from there.
I fully agree with you on this, which is where my cognitive dissonance kicks in. I guess part of the reason is that, even though I agree symbolic changes are good, I don't feel that this was even symbolic enough. A better symbolic change in my mind would be for Github to announce a paid apprenticeship program for people without a STEM/CS background, and try to also somehow cover more black communities. I don't know how this would be executed[1], or if it even can be executed, so maybe it's not a well thought-out idea.
[1]: Maybe engage/market more proactively at schools/communities where the majority of the students/people are black?
I don't believe it was the technical terminology that caused unwelcoming conditions, but the people in the industry.