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


Several comments:

1) It's a pity that this proposal didn't come in a day or two earlier. This would have made it possible to discuss it at the recent developers' meeting (see https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20160118Japan). The next such meeting is in about a month (see https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20160216Japan). I don't want to imply that we have to wait that long before moving forward (which may include deciding that we don't need any explicit code of conduct, as some contributors have already suggested), but for issues like this, some face-to-face discussion may help a lot.)

2) As most of you know, the Ruby language has its origin in Japan, and many of the development activities (including meetings such as the above) continue to be centered in Japan. This raises a number of issues:

2.1) The proposed code of conduct is available in quite a few languages, but not in Japanese.

2.2) The proposed code of conduct mentions religion and nationality, but not culture and language. Those seem important to me both because they are important aspects of diversity, and also because they are important sources of misunderstandings.

2.2) The proposed code of conduct, in the second-to-last paragraph, has some clear requirements on what it calls 'project maintainers'. In Ruby, we have 'branch maintainers'. We are very grateful for all the hard work that they are doing as volunteers, but they may not have the time or willingness to take on yet another responsibility, in particular one which some of them may not feel very confident with. We would have to figure out who might be willing to serve as the 'project maintainers' in the sense of the code of conduct, i.e. who would get the mails sent to the email address that we would have to set up.

3) RubyKaigi (http://rubykaigi.org) has a code of conduct (see http://rubykaigi.org/2015/code-of-conduct), both in English and in Japanese. Although some changes would be needed, it may be possible to leverage that document, and the experience around it.

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

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