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 (smtp.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id E68C219E003C for ; Wed, 20 Jan 2016 19:26:03 +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 BCBC8B5D86D for ; Wed, 20 Jan 2016 19:59:42 +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 63E7218CC7B1 for ; Wed, 20 Jan 2016 19:59:43 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id AC52C120440; Wed, 20 Jan 2016 19:59:41 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 20A8E12003B for ; Wed, 20 Jan 2016 19:59:37 +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=Edij+SP029B5eMoxyorxhlcFuKs=; b=K+t6JcqCud90lvKIbV zcuo6yEgS+KO3XvQU/wGBOde61CtQDg50O1pYD/Z3wNP9dLt/kqIv9VEcLL4lcm1 QGMHVRzH7a+JJFz93eTwOc2nzhxIkaGW9bo/2K60uR/GkmPwNYBCXOGv5LIumeyu ISlmVBHHI7G5tWvtfDGqakx+Q= Received: by filter0815p1mdw1.sendgrid.net with SMTP id filter0815p1mdw1.2499.569F68953F 2016-01-20 10:59:33.671551294 +0000 UTC Received: from herokuapp.com (ec2-54-198-71-154.compute-1.amazonaws.com [54.198.71.154]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id lKJU0_CkSte5s6fv8IlqLQ Wed, 20 Jan 2016 10:59:33.793 +0000 (UTC) Date: Wed, 20 Jan 2016 10:59:33 +0000 From: rdrake98@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47585 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: rdrake98 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4BdjsZqRf3gL5AAQKPjctKwhZqj3hmxdpll2 Ucv1nmP9DebYl9JKMz88Jcbj6bFcfq/5LMODDICY+fnfmYsNPyXJV5H2zyMdi9ytq0rhloV6FGE5BY IHDyJMkjlv5wwehFgbImMrkEepotNVVBGu2baGKGYQUrg11NjSdUVhL7yQ== X-ML-Name: ruby-core X-Mail-Count: 72976 Subject: [ruby-core:72976] [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 Richard Drake. Final point of the PostgreSQL CoC: > 5. The CoC is only about interaction with the PostgreSQL community. Your private and public lives outside of the PostgreSQL community are your own. This would have prevented the stupidity in the Opal case in July, where 1. a tweeted comment by the second most regular contributor 2. in a context quite outside that community 3. was interpreted in the most negative way possible 4. with only one person interested in what had been meant (my first question) 5. the accusing being done by people the vast majority of whom had never contributed 6. leading to widespread demands for Elia's expulsion and other personal attacks on him. A bad introduction for me and others to one kind of CoC applied to FOSS projects. The PostgreSQL approach would have nipped all of this in the bud. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56196 * 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/