PhantomDiploma
kiwifarms.net
- Joined
- Nov 8, 2016
There has been a push by social justice warriors to impose codes of conduct on open source projects. This would not be much of an issue if it was limited to fairly resolving disputes within the community. At worst it would be considered redundant, because most projects large enough for this to be needed already have processes in place to resolve conflicts between developers. After all, bickering interferes with productivity.
The problem is these processes tend to be geared more towards amicably resolving the dispute, not labeling certain developers as oppressive nonpersons. More importantly, controlling a developer's behavior within the scope of the project is just not enough. No, people must follow this code of conduct outside of the project as well because wrongthink anywhere is wrongthink everywhere:
Despite being able to get her Code of Conduct imposed on Opal through these tactics, Coraline had never before and has never since contributed to Opal.
And what about this Coraline Ada? Did her career flounder after this unprofessional and bizarre chapter? Was she a skilled enough programmer that some people were still willing to hire her in spite of this?
What?
And this is where it gets interesting...
In short:
GitHub's Atom repo uses the Contributor Covenant. The creator of the Contributor Covenant has violated both GitHub TOS and the Contributor Covenant by making a "threatening" tweet about the reporter who interviewed Richard Spencer when he was assaulted. GitHub staff refuses to acknowledge this infraction and an employee closes and locks the issue on the Atom repo when this is brought up, claiming that the opener was "taking some, obviously sarcastic, quotes out of context".
In long:
The creator of the Contributor Covenant also gave her own spin to the "punch Nazis" fad after Richard Spencer's unprovoked assault. In reference to this assault, she went beyond the norm of condoning unprovoked violence against just the white nationalist and asked, "why didn’t anyone punch the reporter giving the nazi air time?"
On April 9. this tweet was brought up in a GitHub issue on the Contributor Convent: "Violent maintainer should be removed from project".
The issue was closed by Coraline Ada, on May 19. She made this defense when closing the issue:
A day later an issue was opened on GitHub's Atom repo, asking "Why is Atom using the Contributor Covenant?"
The issue mentions both the original tweet that Coraline posted and her response when closing the issue on the Contributor Covenant repo. It notes that Coraline is in violation of both GitHub's TOS and her own CoC and "the only way this person can continue to operate on GitHub and on her own project is through the selective enforcement of both of these guidelines".
In response to this, a GitHub Community Manager closed and locked the issue. He dismissed the tweet and her defense of it as "some, obviously sarcastic, quotes out of context". He also went on to rationalize closing and locking the thread (ie: making it so any other users could not comment on it) by claiming it was because "this is obviously a vendetta that has nothing to do with Atom".
The problem is these processes tend to be geared more towards amicably resolving the dispute, not labeling certain developers as oppressive nonpersons. More importantly, controlling a developer's behavior within the scope of the project is just not enough. No, people must follow this code of conduct outside of the project as well because wrongthink anywhere is wrongthink everywhere:
This kind of logic was clearly illustrated during an event which is now known as "OpalGate", when the creator of the Contributor Covenant opened an issue on the Opal demanding a frequent contributor be removed for comments he made on Twitter (it is also worth noting that she never linked to anything the programmer said but to how an ANTIFA member construed it). She went on to make unsolicited contact with the programmer on Twitter by demanding he "retract and apologize for transphobic behavior and donate to a transgender charity of [her] choice".This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
Despite being able to get her Code of Conduct imposed on Opal through these tactics, Coraline had never before and has never since contributed to Opal.
And what about this Coraline Ada? Did her career flounder after this unprofessional and bizarre chapter? Was she a skilled enough programmer that some people were still willing to hire her in spite of this?
What?
And this is where it gets interesting...
In short:
GitHub's Atom repo uses the Contributor Covenant. The creator of the Contributor Covenant has violated both GitHub TOS and the Contributor Covenant by making a "threatening" tweet about the reporter who interviewed Richard Spencer when he was assaulted. GitHub staff refuses to acknowledge this infraction and an employee closes and locks the issue on the Atom repo when this is brought up, claiming that the opener was "taking some, obviously sarcastic, quotes out of context".
In long:
The creator of the Contributor Covenant also gave her own spin to the "punch Nazis" fad after Richard Spencer's unprovoked assault. In reference to this assault, she went beyond the norm of condoning unprovoked violence against just the white nationalist and asked, "why didn’t anyone punch the reporter giving the nazi air time?"
On April 9. this tweet was brought up in a GitHub issue on the Contributor Convent: "Violent maintainer should be removed from project".
The issue was closed by Coraline Ada, on May 19. She made this defense when closing the issue:
Coraline Ada said:I'm obviously a very toxic person, as evidenced by my hatred for bigots, racists, homophobes, transphobes, and other bad actors. No one should contribute to this project anymore and I should step down as sole maintainer and let it languish. I'll let the hundreds of people involved in translating the Contributor Covenant into 21 languages and the 20k open source adopters know that they are dealing with a person who believes that literal nazis should not be given a media platform so that they can find an alternate code of conduct, preferably one that leaves room for people to foment hatred under the guise of inclusivity.
Thanks for bringing this to my attention!
A day later an issue was opened on GitHub's Atom repo, asking "Why is Atom using the Contributor Covenant?"
The issue mentions both the original tweet that Coraline posted and her response when closing the issue on the Contributor Covenant repo. It notes that Coraline is in violation of both GitHub's TOS and her own CoC and "the only way this person can continue to operate on GitHub and on her own project is through the selective enforcement of both of these guidelines".
In response to this, a GitHub Community Manager closed and locked the issue. He dismissed the tweet and her defense of it as "some, obviously sarcastic, quotes out of context". He also went on to rationalize closing and locking the thread (ie: making it so any other users could not comment on it) by claiming it was because "this is obviously a vendetta that has nothing to do with Atom".
Last edited: