Issue #12004 has been updated by Robert Klemme.


Folks,

I guess by now all the arguments have been presented already.  I'll just post in case someone wants to draw a statistic from this comment thread and give my perspective.

Coraline Ada Ehmke wrote:

> My suggestion to adopt the Contributor Covenant was a first step. Ideally each community starts with something like this and evolves and shapes it to suit their particular needs.

Please don't.  This will almost inevitably draw some people to spend time and time again "improving" the wording of the CoC.  With this discussion (currently at 300+ comments!) we can see the effect already: people spend time discussing a document rather than actually being nice to each other and given those appropriate feedback that are not nice.

> What's important in this process however is that people who might otherwise feel excluded from certain open source communities be involved in shaping the final code of conduct.

This means that people who might feel excluded must be given chance to work on the CoC while for all others it is optional.

Please do not get me wrong: I am sympathetic of the goal to give more people a chance to contribute that for whatever reason do not do it today.  But I object installint a CoC for a number of reasons:

* I do not see that we actually have an issue with "non niceness".
* Some people seem to believe that having a CoC solves issues - which is nonsense of course.
* I have the impression that some expect a CoC ensures maximum happiness of all community members.  This will never happen as conflicts are human.
* A CoC will encourage some bad, unnecessary or unwanted behaviors:
  * judging and policing of others pointing to the "law"
  * spending time on working on the CoC
  * even founding a CoC Committee
  * debating interpretation of particular rules (while creating the CoC, but also later on)
* We are grown ups and every grown up should know how to behave.  Those who are not, will remove themselves from the community by their behavior or be removed by the community - regardless whether a CoC exists or not.
* I do not support the goal of featherbedding everybody.  There are too many people insulted by peanuts that make noise or even harm others.  People need to learn (again) that life also has its harsh sides and nobody is entitled a first row seat in heaven.
* I very much prefer the Buddhist approach to define the noble goal ("reduce suffering") and leave it to the individual's responsibility to do the needful in every situation than other religious approaches which give detailed rules ("here are the rules, this is forbidden, this is allowed") which tend to be applied thoughtlessly across the board.

If someone needs a negative example you can look at what is happening at US university campuses currently (search for keywords "trigger warning" and "microagression").  There are a lot of people under way with very good intentions but in the process they loose completely sight of the right measure with negative consequences for freedom of speech and even some individuals who have lost their jobs because of peanuts.

Kind regards

robert

PS: Sorry for the lengthy comment.

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

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