That said, open source has been shaped by the people behind it. Entire forks have been created over nothing but internal politics regardless of "inclusivity." Large projects have rejected major features just because the maintainer didn't want it even though others did. Just because you have been insulated from this doesn't mean it isn't there.
To me this just sounds like some sort of "stranger danger" boogeyman. A problem that is much smaller than you make it out to be.
https://github.com/opal/opal/issues/941
https://github.com/kickstarter/rack-attack/pull/181
https://github.com/graphite-project/graphite-web/issues/1569
https://github.com/dotnet/roslyn/pull/3507
https://github.com/Droogans/unmaintainable-code/pull/20
https://github.com/zendframework/zend-expressive/pull/340
https://github.com/assemble/assemble.io/issues/163
https://github.com/braydie/HowToBeAProgrammer/issues/68
https://github.com/airbnb/javascript/pull/698
https://github.com/lighthouse-labs/clock-tower/pull/87
https://github.com/smalltownheroes/bikini-girls-with-machine...
https://github.com/kubernetes/kubernetes/issues/27430
https://github.com/ardanlabs/gotraining/issues/75
https://github.com/antirez/redis/issues/3185
https://github.com/syl20bnr/spacemacs/pull/3484
https://github.com/TryGhost/Ghost/issues/5889
https://github.com/twolfson/sexy-bash-prompt/issues/56
http://web.archive.org/web/20151030100136/https://github.com...
> People crawl through projects on github for certain words and open pull requests to try and get them changed
You've also failed to demonstrate in this thread instances of people being called out for using the "wrong" libraries (where "wrong" is defined as libraries that don't conform to the complainant's views). All of these examples are of people making direct changes to software. The idea that one should be scared that they may get called out over the transgressions of their software dependencies has yet to be demonstrated.
I have no idea what you're talking about with regards to wrong libraries and dependencies. I made no mention of such a thing.
> Nowadays I worry that I might be called out for using a piece of code (however good it might be) just because the person who wrote it does not use "inclusive" language
This is what I was originally responding to.
Judge for yourself:
And the majority of SJ-related requests I've seen are in effect just that; declarations that the existing society standards are suboptimal for the usecases of ethnic minorities, women, LGBTA+ people, etc., along with suggestions for revisions.
They are (in my mind) the same people that view Native Americans being offended at the existence of the Washington Redskins as people that are making "a bit fuss over nothing."
It seems that we're commenting on an article where just such a person materialized, and their impact can be quantified: a well-qualified speaker was dropped from a conference.
> They are (in my mind) the same people that view Native Americans being offended at the existence of the Washington Redskins as people that are making "a bit fuss over nothing."
I admit I don't follow sports enough to know the details of that brouhaha so I don't know if someone (or many someones) of American Indian descent were the ones calling for the change or if it was a "disinterested" third party. Either way, the opinions and preferences of the community at large must be weighed against those of the dissenters. In my opinion we already have an extremely effective means of recourse for those who take offense - the free market, which can be impacted by direct means (boycott) or indirect means (convincing others to support your view).
I can give other examples. For example, this past weekend saw an air show about downtown Toronto as part of the Canadian National Exhibition. There was talk of how the thundering of the jets flying over downtown wasn't necessarily "enjoyed" by people that have been in war-zones (e.g. Syrian refugees). I don't think that there was any suggestion that the air show should be scrapped on this basis, but still there were people claiming that the refugees should "just get over it" because they are not in a war zone anymore. This is incredibly insensitive. Someone in my own family expressed the view point that after a couple of years out of the war zone that they should "get over it."
That aside, I don't see where in this comment chain we're discussing a standards body. This type of commit to individual projects should, in my opinion, be strongly discouraged.
I didn't end up using the library.
What I haven't done is try to gin up a twit mob to have the author hounded from his job, no-platformed at conferences, and so on.
This lead to threats of boycott where the Flycheck maintainer said that he would actively discourage the contributors to his project from supporting Spacemacs because of this issue.
I sincerely doubt one would find anything remotely similar in C++, Linux (C lang), or Assembly-programming communities.
The "harder" the language the less non-coding politics around.
The Linux world is full of commotion surrounding (written) language.
The necessity of Unicode is a great example of how a seemingly-straightforward technical design can prove inadequate once it needs to serve the full set of humanity.
Upvote this comment if you agree.
Upvote this comment if you think it's sarcasm.