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 2D05B19E004C for ; Sat, 23 Jan 2016 07:34: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 C0C92B5D87C for ; Sat, 23 Jan 2016 08:08:34 +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 E602118CC7D1 for ; Sat, 23 Jan 2016 08:08:34 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 912941205B6; Sat, 23 Jan 2016 08:08: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 8C3381204A7 for ; Sat, 23 Jan 2016 08:08:29 +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=yBVLRKqCHdgFer6mBNMGpAWsQ/4=; b=eY8mMEmMYO+5nYwNb2 HI4nGPxqJj+cBH6VVaAhNbjNAhlFfv3EbLUZACuslbBzE5DIIgSTUZkDBptS16qP T42y2mAFBDNEYt8xpQWvE+owRSdYeVTOOeq6cisG+TZA2+pu33eiPRTLy4iXmVkH uhUmtcTdwdjNjlkSfXF68kiVs= Received: by filter0542p1mdw1.sendgrid.net with SMTP id filter0542p1mdw1.25602.56A2B6692F 2016-01-22 23:08:25.928139478 +0000 UTC Received: from herokuapp.com (ec2-54-160-196-92.compute-1.amazonaws.com [54.160.196.92]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id ol0Dk2Z9RcuO_4JT0hC0Vg Fri, 22 Jan 2016 23:08:25.959 +0000 (UTC) Date: Fri, 22 Jan 2016 23:08:25 +0000 From: nekocat432@yahoo.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47861 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: rubydino 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7ZgeQBvKpLKTJsS8YnsBENUVT9ntZ5gKlvun NnknITxJ+hC+ZGcmnqri0ZljSC+sgOzcm0WUkMgFL0hPWzmsvghywiVqafiE86PG/RsWp/+TvRD4Eo cG0x5ptk6QobeL2XpKV8h0RsOeePoGMNmkjc2c2uCyzXLf/h+Dx2bSZ4xg== X-ML-Name: ruby-core X-Mail-Count: 73254 Subject: [ruby-core:73254] [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 Ruby Dino. Kurtis Rainbolt-Greene wrote: > It should be noted that both Rust and node have seemly reacted to this discussion by doing exactly what Olivier Lucan is talking about. > > The Contributor Covenant is the appropriate choice, with *minor* adjustments to fit the architecture, scope, and space of the CRuby community. It's not actually, as the Contributor Covenant is a politically motivated document. A different non-political CoC is best suited. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56478 * 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/