Issue #12004 has been updated by Ruby Amateur.


Andreas Fast wrote:
> I still think that the tone of Coraline's proposal isn't very much aligned with the ruby community. I think that the core team has shown a lot of common sense in the past and we can trust they will continue to do so in the future.
> This is about people feeling comfortable and welcome with the ruby community, and I think it has shown maturity and people do feel welcome. I don't think that a code of conduct in itself would make the community a safer place, but people following it.
> 
> I like Jeremy's proposal much better, specially because the tone is more attuned to the ruby community and conveys the message, and I think everyone finds it acceptable, although those wanting forceful action might find it lacking, they're not against it. Matz has stated that he doesn't want to put that burden on maintainers and I support his choice.
> 
> We can still rely on common sense for forceful action should it be needed, and as we've seen in this very thread, it works just fine.

I fully agree. I think the community needs to **stop torturing itselves** over this thread and do the following:

(1) Choose Jeremy, PostgreSQL, or OpenSSL proposal (the latter 2 being my specific opinion). Attribution goes to PostgreSQL or Jeremy. Commit it to the project.

(2) Perhaps make a date 3, 6, or 12 months from now to review if we need to reconsider what further to put into the code of conduct.

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

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