The successful defense of Ruby against SJW infiltrators demonstrates the importance of having a strong project leader rather than a committee, or worse, a democracy, running an open source software project:
The Ruby Community Conduct Guideline
We have picked the following conduct guideline based on an early draft of the PostgreSQL CoC, for Ruby developers community for safe, productive collaboration. Each Ruby related community (conference etc.) may pick their own Code of Conduct.
This document provides community guidelines for a safe, respectful, productive, and collaborative place for any person who is willing to contribute to the Ruby community. It applies to all “collaborative space”, which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.).
- Participants will be tolerant of opposing views.
- Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
- When interpreting the words and actions of others, participants should always assume good intentions.
- Behaviour which can be reasonably considered harassment will not be tolerated.
It’s worth noting that this not only defeats the primary, secondary, and tertiary purposes of the Code of Conduct that Typhoid Coraline was attempting to install in order to unseat Matz, but it can obviously be used effectively against SJW entryists.
No wonder Typhoid is so upset. It’s a superficial victory of absolutely no utility for him.
Coraline Ada Ehmke @CoralineAda
This is very disappointing. No one to report abuse to. No recourse for victims of harassment. Poor showing, Ruby.
Coraline Ada Ehmke @CoralineAda
Sad that Ruby still doesn’t have a code of conduct. I don’t know what to call that thing.
Coraline Ada Ehmke @CoralineAda
Unfortunately I fear that it will take a nasty incident for Matz to change his mind
about a code of conduct. I feel bad about this.