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 2D4B419E0056 for ; Sun, 24 Jan 2016 05:26:54 +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 8A1E0B5D8E1 for ; Sun, 24 Jan 2016 06:00:43 +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 A0F1018CC7D0 for ; Sun, 24 Jan 2016 06:00:43 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id BC54B1205CB; Sun, 24 Jan 2016 06:00:42 +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 6791F1204FD for ; Sun, 24 Jan 2016 06:00:39 +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=pqUxuPQr0NH762lvDhfQbbIYifU=; b=Rl28NmvYRM5m+DXTsW zocZWddLUEAOH3aDdcnErFoGILyApEW8ke2bCJRgmoEaY0Lp35pIBGZSd37ycsWS 5n0KFKeTXhghtrto4duhk3+qEU3V3fXc538sMQz8d/y4kFKWhE+nDaNKXLoKn/Rh lLcLz6bOmEOX37T+UBCsz1pjM= Received: by filter0550p1mdw1.sendgrid.net with SMTP id filter0550p1mdw1.7978.56A3E9ECC 2016-01-23 21:00:28.183413352 +0000 UTC Received: from herokuapp.com (ec2-54-146-188-210.compute-1.amazonaws.com [54.146.188.210]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id Ii4uRv85TT6n9brMPA7axQ Sat, 23 Jan 2016 21:00:28.661 +0000 (UTC) Date: Sat, 23 Jan 2016 21:00:28 +0000 From: coraline@idolhands.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47934 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: CoralineAda 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS5Dp3UtT3Tzuk1viv9LIJb68EVrXZClqeigUV zYB2z73fMpYP4TZpjWmWoWohrIK+xYK+PdCncX+C/OsjIz+MQT0//odFQhsqJqOYBxfMsErqXSEP/F uopQbLRq85ttUkqkWtiWDv6DUAIXzFfYPdbqhLuISe+WKF3kEkJF2To5oA== X-ML-Name: ruby-core X-Mail-Count: 73328 Subject: [ruby-core:73328] [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 Coraline Ada Ehmke. It's important to note in the face of all this hand-wavy "SJWs are coming to steal my cheese" nonsense that enforcement of a code of conduct is and always will be in the hands and in the discretion of project maintainers, or whomever Matz and others assign to the task. The code of conduct is not a set of draconian laws that obligate maintainers to ostracize someone at the first sight of an offense and it's disingenuous to say that this is so. If you don't trust project managers with a code of conduct, then how can you possibly trust them without one? ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56557 * 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/