Issue #12004 has been updated by Martin Dürst.


[I'm only writing this as my personal opinion, not speaking for Matz or anybody else.]

Ary Borenszweig wrote:
> My personal belief is that the issue with these CoCs is who enforces them. It seems Matz and other members don't want to spend part of their time in thinking and judging "Is this comment harassment? Should I ban this member? Should I remove this comment?". That is, spending that time in addition to already spending time on the project: code, issues, pull requests, etc, which, if you ever managed an open source project, takes a huge amount of time.

I don't think anybody would want to spend time on such issues if they could avoid it. There are many more fun activities to spend your time on.

However, I think that Matz and others up to now have shown that they care for the community, and that if necessary, they will take some action. MINASWAN wasn't born out of a vacum, it came from how Matz was and is leading the community. Also, having a look at some of Matz's invited talks at conferences will show that he cares a lot for the community.

As such, I see an additional document not so much as a set of new rules, and much more as a clarification of things that in one way or another have been in practice all along already.


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

* 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.


---Files--------------------------------
Screen Shot 2016-01-22 at 6.45.23 PM.png (595 KB)
Ruby_Code_of_Conduct_Numbers.png (119 KB)
Ruby_Code_of_Conduct_Discussion.png (143 KB)


-- 
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>