The SJW war on Ruby continues

Despite being warned off by members of the group, and despite the Ruby project founder making it clear that thought policing and enforcement is not going to be permitted, Typhoid Coraline has taken advantage of the founder’s desire to be nice as he continues revising and spinning and attempting to take control of the project. This is his latest attempt after having the poison pill that is his Contributor Covenant knocked back:

As part of our collective culture we believe that the Ruby community should be open and welcoming to everyone, regardless of age, body size, disability, culture, ethnicity, gender, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual orientation.

This document provides community guidelines for a safe, respectful, productive, and collaborative place for people engaging with and contributing to to the Ruby community. It applies to all collaborative spaces and documents, including mailing lists, IRC, submitted patches, big reports, and pull requests.

  •     Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
  •     Participants must agree that the use of sexual imagery, sexual language, and sexual advances are not conducive to a professional environment and must be avoided.
  •     Participants must not publish non-public contact information about other members of the community, including physical addresses or other private information.
  •     Participants who disrupt the collaborative space, or participate in a pattern of behaviour which could reasonably be considered harassment will not be tolerated.

    Anyone asked to stop unacceptable behavior is expected to comply immediately.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by sending an email to [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Respondents are obligated to maintain confidentiality with regard to the reporter of an incident.

We believe that by thoughtfully abiding by these community guidelines, we help Ruby fulfill its promise to make people happy and to put the needs of the community first.

This is a retreat from the Covenant, which covers all behavior by a contributor, whether it is related to the project or not. But the level of sheer dishonesty it entails is revealed by some of Typhoid Coraline’s SJW supporters.

I would recommend the Contributor Covenant. People complaining that it includes harassment in public spaces are most likely just guilty of doing so. Just because the harassment occurs outside the scope of the project does not make it any more ok!

It’s quite obvious from this thread alone how toxic this community is, I can’t believe so many people are essentially saying they don’t want to stop harassing people by coming up with silly excuses as if a CoC was somehow implementing communism.

The responsibility of enforcing the code of conduct should be handed to a committee comprised of people who have more experience with harassment which is often not recognised by people with more privilege. As well as that, what if Matz or one of the maintainers themselves were to violate the code of conduct? Nobody could stop them, therefore the CoC enforcement task should be carried out members of minority groups who will not violate the CoC. Nobody, not Matz or any maintainers should be exempt from consequences like demotion and banning. And as Matz has already stated, he will probably not have the time or willingness to deal with peoples reports of unacceptable behaviour.

Notice how their priority is not the Code of Conduct, but the committee that is charged with enforcing it. This SJW is considerably clumsier than Typhoid Coraline, in that he openly states how the committee will be stacked by “members of minority groups” who, by their very nature, “will not violate the CoC”. Remember, SJWs always set up rules that do not apply to them. They are above the law; laws are for those lesser people who are insufficiently idealistic.

Only an idiot would accept the establishment of an authority that not only has the ability to demote and ban him, but quite clearly has every intention of doing so. Sadly, there are more than a few naive idiots in the OSS world.

And, of course, anywhere there are SJWs, the First Law of SJW is in action:

I also support adopting a Code of Conduct. I believe CC 1.3 is a good base to work from simply because it is already used on many well known projects. I grew up in a “thick skin” internet age myself, so I personally prefer the “deal with it, fight back, or killfile” approach. That said, I live on top of a giant mountain of privilege. For my projects, I feel that I have a greater responsibility than simply serving my personal ideology. For me, I wasn’t quick to decide that adding a code of conduct to a project was a good thing, and I shared many of the concerns expressed by the non-troll commenters on this thread.

But the net effect of actually taking the time to listen and learn, not just to those active in social justice, but everyday people from many different backgrounds, was to find out… yes, this is a real problem. Sending a signal of support to those who have experienced that problem elsewhere in a way that’s loud and clear is worth doing. A CoC is one of the basic tools that can set the stage for accomplishing that, and if we trust the maintainers of this project, that trust will be preserved even after a CoC is implemented.

However, if the core team decides not to act on this, or acts on this in a way that’s half baked and idealistic, or acts in way that’s meant to preserve the “nice” attitude rather than making an effective decision — you will lose the trust of many who have come to realize that community management involves a lot more than the purely technical aspect of things. There are people in this thread that I’ve totally lost respect for already, who I’ve collaborated with before and previously thought of as very insightful voices in Ruby.

Not only the lies, but the threat is always the same. Do what I demand or I shall disapprove of you! However, it is clear from this Japanese Ruby administrator’s response that patience is wearing thin and the SJW attack has been recognized for what it is.

Currently, in order to maintain the integrity of the discussion in this issue, creating new accounts have been suspended. This means that we considered that this issue may be important, and this issue is occurring some hindrance to the development of Ruby. I hope that everyone who comments to this issue understands that.

After this issue was opened, many new accounts are created. Most of such accounts only commented to this issue. Normally new comers are welcomed, but in this case, sorry, I am watching such accounts with distrust.

My policy should be clear. I stand by the One-Finger Code of Conduct.