From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 9E67119E0032 for ; Thu, 21 Jan 2016 04:39:14 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 9675EB5D86B for ; Thu, 21 Jan 2016 05:12:55 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id A6F9918CC80C for ; Thu, 21 Jan 2016 05:12:55 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id D7BBF120496; Thu, 21 Jan 2016 05:12:52 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 10F73120487 for ; Thu, 21 Jan 2016 05:12:48 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=WHKHTHp+Pxp6+hEr1bG5GAMhFMQ=; b=YEobqctmThl4Al7l6x FB/2aT6cBK4CaN9hkB2Di0JI9vnGm1xvel0OaQxL1uf6Mbe084cpQLbNLHpjQeUc GX5xM+JauzZPixc/Nlb1Im163wF/6Bt3g9U4jbWx0yqdV0APMunx+KIX3W8oTXso YtEenYGAgf+8PmpAm/AVpvOuk= Received: by filter0423p1mdw1.sendgrid.net with SMTP id filter0423p1mdw1.30289.569FEA3B54 2016-01-20 20:12:43.662732852 +0000 UTC Received: from herokuapp.com (ec2-54-147-204-177.compute-1.amazonaws.com [54.147.204.177]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id N4zGBsr_RRGGeY3VjzD4AQ Wed, 20 Jan 2016 20:12:43.526 +0000 (UTC) Date: Wed, 20 Jan 2016 20:12:43 +0000 From: andrew@avit.ca To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47605 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: avit X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4wJ1ciORWp44RIbgnEtqzal4eWeKcfXXCrhh l+InsMAOk6NCVoBLur/tXnFzwPcxzQBEVW8XsnTft2MA5fVx7Id54lgX7JxWRoZvGmdtdJQcY5veJf GXpaEfHqYoyJbuIUL2fC5QE9YfIVNR2RMpOv X-SendGrid-Contentd-ID: {"test_id":"1453320764"} X-ML-Name: ruby-core X-Mail-Count: 72996 Subject: [ruby-core:72996] [Ruby trunk - Misc #12004] Code of Conduct X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #12004 has been updated by Andrew Vit. Fred Heath wrote: > That alone isn't enough. We need evidence as to whether these issues would have been either avoided or better handled by the existence of a CoC. > > As evidence that would be purely circumstantial. We need evidence of how many potential contributors have been put off by the lack of a CoC. Against how many will be put off by the existence of such a CoC. To be clear, I was not suggesting that there's an exact measurement for human factors. But, is there *any* data that might show a correlation between CODE_OF_CONDUCT.md and greater diversity? When I just say it that way, the idea by itself sounds ridiculous, but maybe I'm wrong. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56216 * 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/