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 EAB6719E0053 for ; Sun, 31 Jan 2016 04:51:47 +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 BE71FB5D89A for ; Sun, 31 Jan 2016 05:25:56 +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 D2B1818CC7B8 for ; Sun, 31 Jan 2016 05:25:56 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 4A81512050D; Sun, 31 Jan 2016 05:25:55 +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 10D2C1204CC for ; Sun, 31 Jan 2016 05:25:51 +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=Uvf7o1az9uNBu5dYvK4uzdFEwrU=; b=l2i5EbeAgVohvMzgT4 bVVrKQ6kCPy2XV5/HC2kocGjY1aNV+DWwdjoqaAm7OvCv59NN2/bynYCk6RGN3Nx IrpNOjDP6kEXXh1aitxS+0DcgwKEb4ZYTeJvIzFlEH7a0wbyj0kUCek5GRWyimQl 5KLRyYjBgeXCm7Z60e55zLm7Q= Received: by filter0921p1mdw1.sendgrid.net with SMTP id filter0921p1mdw1.16027.56AD1C4CC 2016-01-30 20:25:48.071785771 +0000 UTC Received: from herokuapp.com (ec2-54-204-173-172.compute-1.amazonaws.com [54.204.173.172]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id ajmSp8pUSK2vkvK-JwQPlg Sat, 30 Jan 2016 20:25:47.945 +0000 (UTC) Date: Sat, 30 Jan 2016 20:25:47 +0000 From: merch-redmine@jeremyevans.net To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 48207 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: jeremyevans0 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS70ZipnYMkmW2rPh0gaioXvnQ7Rs/zMY/KrAJ z9fSHk8d2JBQssV/lfdhnLPD22u8iHiBCpcKoslpWgHOyuM+gDkaSd9zKjenzWeHn+Qrjz7accku6v 12kmCBkz8jAlVGhAwG0mGod5LQ6zONArrtOlt/l5S4WXEvEBHEQ+wygDzQ== X-ML-Name: ruby-core X-Mail-Count: 73612 Subject: [ruby-core:73612] [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 Jeremy Evans. Coraline Ada Ehmke wrote: > It should be noted that the leaders of the Postgres project rejected the language in the proposed CoC and have decided to consult with professionals on developing an appropriate code of conduct for their community. In light of that I don't think that we should be considering their draft as a possibility. Details are here: http://www.postgresql.org/message-id/56A8516B.8000105@agliodbs.com They didn't reject the language. From the email: "The Core Team will appoint an exploration committee which will look at various proposals (including the one drafted on pgsql-general) for CoCs and discuss them." Implying that the PostgreSQL Core team disagrees with the language of the draft is disingenuous. Just as Matz is doing, they are taking some time to decide on an appropriate one. It could end up looking similar to the draft, it could end up looking completely different. In any case, whether or not PostgreSQL ends up using the language in the draft should not affect Matz's decision on a CoC for Ruby. Arguing otherwise is simply an appeal to authority. Though considering the language used to open the issue, maybe Coraline doesn't consider that a problem. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56807 * 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) Ruby_Code_of_Conduct_Discussion.png (143 KB) 1362181286eb3305_l.png (168 KB) -- https://bugs.ruby-lang.org/