From: duerst@... Date: 2016-01-23T03:26:09+00:00 Subject: [ruby-core:73295] [Ruby trunk - Misc #12004] Code of Conduct Issue #12004 has been updated by Martin D��rst. Motohiro KOSAKI wrote: > Sorry, I respectfully and strong disagree to reuse security@ruby-lang.org. security@ruby-lang.org is not only subscribed security team, but also some OS vendor and Linux distributor staff because we want they handle security issue very quickly. If real and serious personal attack will be happen, I suspect injured person don't want the attacking message widely spread. Then, harassment and security reporting place should be separated. Sorry I wasn't clear enough. What I meant is to create a SEPARATE mail address, but to run it somewhat similar to the security list. Similar means that the recipients are volunteers appointed by Matz, but not a committee officially listed on a Web page. The easiest way to create such a list would be to just use something like moderators@ruby-lang.org, and subscribe the current admins to the list. Such a list would also help for spam. I have on occasion sent a mail to somebody that I suspected had administration privileges to point out some spam. But I never was sure I sent the mail to the right person, and to the person who had some time. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56524 * 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) -- https://bugs.ruby-lang.org/ Unsubscribe: