From: rubyamateur@... Date: 2016-01-23T01:22:34+00:00 Subject: [ruby-core:73273] [Ruby trunk - Misc #12004] Code of Conduct Issue #12004 has been updated by Ruby Amateur. Olivier Lacan wrote: > I must insist on the consequences for violations to be more clearly defined. Otherwise the fact that few in the core team are trained to handle conduct issues could become more problematic. I think Coraline mentioned that examples of consequences give "teeth" to a code of conduct. That makes sense to me. While I understand why Matz would be reluctant to ban people who violate the code of conduct, clear consequences need to be stated. Otherwise the only proof that the code of conduct is being enforced would be the public announcement that someone violated the code of conduct. Meanwhile neither perpetrators nor victims of code of conduct violations can be assured that the core team will act because no examples of potential consequences are stated. > > I would admit that applying a code of conduct to the public sphere beyond the project (say if a contributor is a frequent Twitter user with a lot of followers) is a very problematic idea. I can understand reticence on that front. > > Jeremy Evan's version is without a doubt better than *nothing*. But I believe [Matz's earlier edit of the CC 1.3.0](https://bugs.ruby-lang.org/issues/12004#note-95) is a far better compromise. Matz argues that consequences and violations such as banishment is ineffective and very much useless. The accused can simply recreate a new account or identity and contribute again. There is also too much burden in doing so. My other concern is these violations and enforcements aren't protective of identities and make spectacles of people, people that may have not done anything terribly wrong (going back to the retribution aspect), which I is what I believe happened to Charles Nutter and the Rubinius project. Having said that... may I suggest a compromise? The Ruby community already feels it is a safe and respectful community. This thread itself is getting out of hand and away from the topic of **implementing a code of conduct**. So perhaps Matz should decide, and let's revisit the topic at a later stage regarding enforcement and consequences (something Matz doesn't feel necessary today), and determine if such a mechanism needs to be in place. I'm not sufficiently convinced this needs to be implemented on day 1, and it simply might be a case of YAGNI. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56502 * 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>