Issue #12004 has been updated by Olivier Lacan.


Ruby Amateur wrote:
> To simplify for those looking up thread for [Jeremy Evan's version](https://bugs.ruby-lang.org/issues/12004#note-104) (which Matz consider a better fit) to contrast with Matz original version reposted by Oliver, here it is:
Thanks for clarifying that. I missed it.

I'd like to point out differences between the following proposals if that can help:
- [Contributor Covenant 1.3.0](http://contributor-covenant.org/version/1/3/0/code_of_conduct.md)
- [Matz edit of Contributor Covenant 1.3.0](https://bugs.ruby-lang.org/issues/12004#note-95)
- [Jeremy Evan's version](https://bugs.ruby-lang.org/issues/12004#note-104)

## [Contributor Covenant (1.3.0)](http://contributor-covenant.org/version/1/3/0/code_of_conduct.md)
### Included
- statement of intent
- statement of commitment
- multiple clear examples of unacceptable behavior
- detailed consequences of violations
- statement of commitment to fairness and consistent application
- scope of application ("collaborative spaces" and public)
- point of contact for reporting violations
- promise of confidentiality for violation reporters
- responsibility and commitment of maintainers

## [Matz edit of Contributor Covenant 1.3.0](https://bugs.ruby-lang.org/issues/12004#note-95)
### Included
- statement of intent
- multiple clear examples of unacceptable behavior
- non-tolerated negative behavior
- detailed consequences of violations
- point of contact for reporting violations
- promise of confidentiality for violation reporters

### Not Included
- scope of application (although implied project-only)
- consequences of violations to perpetrators
- expectation of public or private behavior (outside project)
- responsibility and commitment of maintainers

## [Jeremy Evan's version](https://bugs.ruby-lang.org/issues/12004#note-127)
### Included
- statement of intent
- scope of application: "collaborative space"
- expected positive behavior
- non-tolerated negative behavior

### Not Included
- point of contact for reporting violations
- detailed consequences of violations
- consequences of violations to perpetrators
- expectation of public or private behavior (outside "collaborative spaces")
- responsibility and commitment of maintainers

I'll admit that the Contributor Covenant 1.3.0 version is far more verbose and specific. I think however that [Matz's original proposal for an edit](https://bugs.ruby-lang.org/issues/12004#note-95) of the CC 1.3.0 version was more appropriate since it only removed the following:
- application to public sphere outside the project
- statement of commitment to fairness and consistent application
- statement that the maintainers "have the right and responsibility" to act.

It merely modified the untouched parts of the CC 1.3.0 by removing:
- copy that referenced behavior outside the scope of the project ("public")
- threat of temporary or permanent ban for violating contributors
- "unprofessional conduct" as an example of unacceptable behavior
- "electronic addresses" as something not to published without permission

And adding:
- "belief" as something protected by the code of conduct

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.  

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

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