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 A948F19E004C for ; Sat, 23 Jan 2016 04:21:48 +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 27454B5D89D for ; Sat, 23 Jan 2016 04:55:35 +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 3520518CC7AF for ; Sat, 23 Jan 2016 04:55:35 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id A0BCC12076C; Sat, 23 Jan 2016 04:55:33 +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 BF09B120739 for ; Sat, 23 Jan 2016 04:55:30 +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=b6Yxz0krDMfDP2r+h+gACNV7Mgs=; b=AwJqrJXZx4TvoRzJzc dLnPPJZ1EVdkImbPBLP4TSKnUgBryvQYlcXsKQ4gi8XthzurAS66geawbZCLTGTH /XS/d3+tbjfy6LTMpPE2PjsqSIWtged7O8lVMmr3a2M8f+dw1+kdmfAWekG3epWC WKZ2Oyn1yZwGGuhBW7Cd0Y904= Received: by filter0810p1mdw1.sendgrid.net with SMTP id filter0810p1mdw1.6130.56A2892511 2016-01-22 19:55:17.307152802 +0000 UTC Received: from herokuapp.com (ec2-54-226-16-127.compute-1.amazonaws.com [54.226.16.127]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id Slgwz-YNT9CaQZ6k99eZ5w Fri, 22 Jan 2016 19:55:17.225 +0000 (UTC) Date: Fri, 22 Jan 2016 19:55:17 +0000 From: azzzz@gmx.net To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47825 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: AstonJ 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS5ZdYGfVoeQ0hnU6hUeWVQMGbP7PaMHC+nIkW xjJdAI6xLnN4XMQ4gQ7uO3Z6GwY0+9kzQ2iQYebPZL2VJrXRgm5OIyyFzTo8K+fUGfVMq0X/Xq4rzU o/rhfOBhCQYvgDD+n+a5hhQHKYUOoa30zpVj X-ML-Name: ruby-core X-Mail-Count: 73217 Subject: [ruby-core:73217] [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 Aston J. Matz, Please don't feel like you have to act now. It would be totally fine to thank everyone for bringing the matter to your attention and saying that you would now like some time to think about it. That could be a few weeks or a few months - there is no rush. You have been running things absolutely fine for over 20 years - a few months without a CoC isn't going to kill anyone. I do feel that rushing into one could create more problems that it would solve - particularly if it is based on the CCoC - which I feel has a negative, unnecessarily antagonistic tone and is connected to an unpleasant episode in our very community (Opal controversy). Contrast it to the positive open-armed tone of the Sass community guidelines: http://sass-lang.com/community-guidelines Aston ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56442 * 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/