Issue #12004 has been updated by John Croisant.


This thread has had personal attacks, trolls, and impersonation. The mods have acted in some cases (in other cases we are still waiting), but only because it is happening right in front of them.

But what if harassment happens where the mods cannot see? For example, what if a new Ruby user sends an email to ruby-talk, and someone replies privately (not to the list) with harassment, insults, sexual comments, etc.? The new user might think that the Ruby community is a bad place, and leave without telling anyone. The mods might never find out, because the harasser did not say it on the list, and the Ruby community has no CoC to provide guidance about how to report harassment. The harasser could remain for years, scaring people away from the community.

A CoC needs to *at least*:

- Provide a list of examples of unacceptable behavior. Otherwise people may be not sure whether the behavior is allowed in this community. For example, personal insults are (apparently) allowed on the Linux Kernel Mailing List, but are not allowed on ruby-talk. The CoC needs to reflect the Ruby community's standards and expectations of behavior.
- Provide guidelines and instructions about how to report incidents. Otherwise people may not know who to contact about the incident.
- Describe the possible consequences of bad behavior, so that people know reports will be taken seriously.

Those features are missing from the PostgreSQL draft CoC, and the version Jeremy Evans posted, and the Code of Merit, and the Sass community guidelines. In my opinion that makes them inadequate for helping members of the Ruby community who experience harassment. Of the CoCs I have seen proposed in this thread, only the Contributor Covenant has those important features.

I understand the desire to avoid bureaucracy, but we could start with something as simple as an email address or private mailing list that people can contact when an incident occurs, as Martin Dürst suggested. (The address would be a new address, not security / ruby-lang.org.) That address could forward the reports to the mods, who would then decide how to respond.

----------------------------------------
Misc #12004: Code of Conduct
https://bugs.ruby-lang.org/issues/12004#change-56462

* Author: Coraline Ada Ehmke
* Status: Assigned
* Priority: Normal
* Assignee: Yukihiro Matsumoto
----------------------------------------
I am the creator of the Contributor Covenant, a code of conduct for Open Source projects. At last count there are over 13,000 projects on Github that have adopted it. This past year saw adoption of Contributor Covenant by a lot of very large, very visible projects, including Rails, Github's Atom text editor, Angular JS, bundler, curl, diaspora, discourse, Eclipse, rspec, shoes, and rvm. The bundler team made code of conduct integration an option in the gem creation workflow, putting it on par with license selection. Many open source language communities have already adopted the code of conduct, including Elixir, Mono, the .NET foundation, F#, and Apple's Swift. RubyTogether also adopted a policy to only fund Ruby projects that had a solid code of conduct in place.

Right now in the PHP community there is a healthy debate about adopting the Contributor Covenant. Since it came from and has been so widely adopted by the Ruby community at large, I think it's time that we consider adopting it for the core Ruby language as well.

Our community prides itself on niceness. What a code of conduct does is define what we mean by nice. It states clearly that we value openness, courtesy, and compassion. That we care about and want contributions from people who may be different from us. That we pledge to respect all contributors regardless of their race, gender, sexual orientation, or other factors. And it makes it clear that we are prepared to follow through on these values with action when and if an incident arises.

I'm asking that we join with the larger Ruby community in supporting the adoption of the Contributor Covenant for the Ruby language. I think that this will be an important step forward and will ensure the continued welcoming and supportive environment around Ruby. You can read the full text of the Contributor Covenant at http://contributor-covenant.org/version/1/3/0/ and learn more at http://contributor-covenant.org/. 

Thanks for your consideration and I look forward to hearing your thoughts.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>