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 2633219E004C for ; Sat, 23 Jan 2016 04:26:06 +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 9805EB5D89D for ; Sat, 23 Jan 2016 04:59:52 +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 A7F2418CC7D0 for ; Sat, 23 Jan 2016 04:59:52 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id EF480120775; Sat, 23 Jan 2016 04:59:50 +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 825FA120761 for ; Sat, 23 Jan 2016 04:59:47 +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=QjZ7H29zdfkP8122XXAZIWzA6Ag=; b=ogf6X0pbdvqideOhVw wwyNQLwj9s/nlx/jN9OsckceWmYkERzfHYOA6v+eZyRK6jtadd/Ch4gj2oMGAHTG nVIj/u2jMBHnAS6I2mkbAuvpnsOZPhoANj+YHbn0Q5PPwtvW4V/GxuZyV4BwqO0R 4rcu6f5gDaIrlCW8ggorOSCtI= Received: by filter0554p1mdw1.sendgrid.net with SMTP id filter0554p1mdw1.11880.56A28A2E24 2016-01-22 19:59:42.75996727 +0000 UTC Received: from herokuapp.com (ec2-54-144-204-85.compute-1.amazonaws.com [54.144.204.85]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id xUTG9Np8TtG70C27keI8lg Fri, 22 Jan 2016 19:59:42.730 +0000 (UTC) Date: Fri, 22 Jan 2016 19:59:42 +0000 From: lvoswink@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47826 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: valarissa 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7DeRL6/k25jQPVMT/9TgLfUBTUs9gDk2qlvg ICmKvUmACiTC0bsowGCkHrwNuN+lvgwubgOs+9eVaspO9/LL12+zJagDxVEOqs5zY7QdTVGs4YNQxC +Ti/T49gG7y2Z4EuGtOVSMiKs7t1Y2AJSETsSd0L8Q/ypkICzcW6aBmpXg== X-ML-Name: ruby-core X-Mail-Count: 73218 Subject: [ruby-core:73218] [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 Lauren Voswinkel. Ruby Dino wrote: > The relevance of WHICH CoC Ruby should adopt if any. The Contributors Covenant is bad spirited, as I've displayed the github link to the commits. Which is fair, looking my initial comment on here, do you support or not support a CoC to be used as described. If so, which one, if not, why? Do you disagree with my suggestion of enforceable and definable protocols in cases where existing methodologies of remediation fail? Let's move the conversation about this in a productive direction rather than sniping at each other. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56443 * 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/