First up, sorry I didn't make the headline more juicy. A few ideas did cross my mind - "feminist sociopaths greenlighting harassment" or "SJWs: 'racism and sexism totally okay!'" for ultimate flamebaiting. :)
Anyway, recently GitHub adopted Open Code of Conduct.
What is it?
It's a code of conduct regulating interactions between community members (duh). It's in a kind of a copy-paste template form so that it would be easy to adopt. Many popular sites have adopted it (twitter, facebook) with some (small but critical) adjustments in the code.
So, what's the problem?
Well, the OCoC is mostly a reasonable piece of regulations, but among many agreeable rules, there's this:
What's this "reverse racism/sexism" that they will not act on?
For people not familiar with the Social Justice lingo, racism or sexism necessitates privilege+power, eg if you're the majority in whatever country/culture you are in, a minority can be as sexist and racist against you as they want without actually being sexist or racist. Yeah, it's just as ass-backwards as it sounds. This means for example, if you're an European in, say, Japan, you can be as... racially prejudiced as you want against the Japanese and going by their definition not be a racist. (well actually no, a white person is always guilty of racism, they will find an ad hoc rationalization)
In short, reverse sexism is sexism against men (eg women being sexist against men), reverse racism is racism against the majority race (eg blacks being racist against whites (in US culture at least)).
The problem is not only that GitHub has adopted it without adjustment to the code, the problem is that it's in the OCoC template to begin with.
How's this happening?
Well, the TODO group, a group of companies behind this OCOC, took Geek Feminism CoC as a model, I kid you not. Theirs is the only one that has the aforementioned blatantly sexist, racist clause.
Indeed, TODO's github page recommends using Ashe Dryden's advice on how to compose a CoC. They link to her site on two occasions.
Who's Ashe Dryden? She's a diversity activist and writer for Model View Culture, an unapologetic SJW/radfem blog founded by Shanley Kane - someone who indeed seems to be a radical feminist sociopath.
Another link in the recommended sites directs to a site, which attributes Geek Feminism and JSConf.
I see a pattern.
What does it mean to GitHub community?
If you're white, male and/or cisgendered, then people get a free pass on being racist, sexist and/or cisphobic against you.
We truly have come full circle, when Code of Conducts are endorsing sexism, racism and gender identity phobia now. This is exactly what not honoring complaints of "reverse sexism/racism" or cisphobia means. In the name of "diversity" and "safety" of course.
I personally don't rely on CoCs in any community, I just block the troll. But this sends IMHO a quite clear message that white cis males are not welcome, they're a lower class you can harass at will. As a web developer and part-time/almost/kinda aspiring indie game dev, I find this open source code of conduct extremely troubling and will probably clone my repos from github to somewhere else. Not that there would be any immediate or direct effect on my day-to-day workflow due to this CoC, but it's really the principle. I wouldn't host my files on KKK servers either, just on principle.
Here's a bonus point for making the definition of "harassment" even more meaningless:
This is a Code of Conduct for online open source communities, not for conferences. Physical contact over the Internet? :eye-poppi
And apparently *hugs* is an act of harassment.
All in all, another day in the asylum of SJWism.
Anyway, recently GitHub adopted Open Code of Conduct.
What is it?
It's a code of conduct regulating interactions between community members (duh). It's in a kind of a copy-paste template form so that it would be easy to adopt. Many popular sites have adopted it (twitter, facebook) with some (small but critical) adjustments in the code.
So, what's the problem?
Well, the OCoC is mostly a reasonable piece of regulations, but among many agreeable rules, there's this:
"Our open source community prioritizes marginalized people’s safety over privileged people’s comfort. We will not act on complaints regarding:
‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you”
Refusal to explain or debate social justice concepts
Communicating in a ‘tone’ you don’t find congenial
Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions"
What's this "reverse racism/sexism" that they will not act on?
For people not familiar with the Social Justice lingo, racism or sexism necessitates privilege+power, eg if you're the majority in whatever country/culture you are in, a minority can be as sexist and racist against you as they want without actually being sexist or racist. Yeah, it's just as ass-backwards as it sounds. This means for example, if you're an European in, say, Japan, you can be as... racially prejudiced as you want against the Japanese and going by their definition not be a racist. (well actually no, a white person is always guilty of racism, they will find an ad hoc rationalization)
In short, reverse sexism is sexism against men (eg women being sexist against men), reverse racism is racism against the majority race (eg blacks being racist against whites (in US culture at least)).
The problem is not only that GitHub has adopted it without adjustment to the code, the problem is that it's in the OCoC template to begin with.
How's this happening?
Well, the TODO group, a group of companies behind this OCOC, took Geek Feminism CoC as a model, I kid you not. Theirs is the only one that has the aforementioned blatantly sexist, racist clause.
"The Geek Feminism community prioritizes marginalized people’s safety over privileged people’s comfort. The Geek Feminism Anti-Abuse Team will not act on complaints regarding:
‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ (because these things don’t exist)"
Indeed, TODO's github page recommends using Ashe Dryden's advice on how to compose a CoC. They link to her site on two occasions.
Who's Ashe Dryden? She's a diversity activist and writer for Model View Culture, an unapologetic SJW/radfem blog founded by Shanley Kane - someone who indeed seems to be a radical feminist sociopath.
Another link in the recommended sites directs to a site, which attributes Geek Feminism and JSConf.
I see a pattern.
What does it mean to GitHub community?
If you're white, male and/or cisgendered, then people get a free pass on being racist, sexist and/or cisphobic against you.
We truly have come full circle, when Code of Conducts are endorsing sexism, racism and gender identity phobia now. This is exactly what not honoring complaints of "reverse sexism/racism" or cisphobia means. In the name of "diversity" and "safety" of course.
I personally don't rely on CoCs in any community, I just block the troll. But this sends IMHO a quite clear message that white cis males are not welcome, they're a lower class you can harass at will. As a web developer and part-time/almost/kinda aspiring indie game dev, I find this open source code of conduct extremely troubling and will probably clone my repos from github to somewhere else. Not that there would be any immediate or direct effect on my day-to-day workflow due to this CoC, but it's really the principle. I wouldn't host my files on KKK servers either, just on principle.
Here's a bonus point for making the definition of "harassment" even more meaningless:
Harassment includes:
<snip>
- Physical contact and simulated physical contact (eg, textual descriptions like “*hug*” or “*backrub*”) without consent or after a request to stop.
This is a Code of Conduct for online open source communities, not for conferences. Physical contact over the Internet? :eye-poppi
And apparently *hugs* is an act of harassment.
All in all, another day in the asylum of SJWism.
via International Skeptics Forum http://ift.tt/1InnhzC
Aucun commentaire:
Enregistrer un commentaire