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 3503519E0013 for ; Sat, 23 Jan 2016 11:19:15 +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 F134AB5D83C for ; Sat, 23 Jan 2016 11:53:01 +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 4AF8118CC7B2 for ; Sat, 23 Jan 2016 11:53:02 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id D6BCA1207B3; Sat, 23 Jan 2016 11:53:00 +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 9F19D1205F1 for ; Sat, 23 Jan 2016 11:52:57 +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=zJU/w7Ytjl65fwmt79kFFj6fBWg=; b=bnU2zOTDZlTakBJROb S4IWIGKA30Mc8pAA/PHFriBg2ya/NE+3s3ZCo+JO7IpQb/xswk3j3QUTb+ebn1eY 2YI3hMwJXP6HnQIR4G6cMHylln/7oA95DX69sXrq6KmyGBlwPUCAtg5O/h2UEpB9 vkQzqaWHN0ghYaLCrMbRQgBMA= Received: by filter0551p1mdw1.sendgrid.net with SMTP id filter0551p1mdw1.9548.56A2EB05B 2016-01-23 02:52:53.22514263 +0000 UTC Received: from herokuapp.com (ec2-54-167-38-51.compute-1.amazonaws.com [54.167.38.51]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id p6DE0ZK2RLSWn2tg-AoGuw Sat, 23 Jan 2016 02:52:53.124 +0000 (UTC) Date: Sat, 23 Jan 2016 02:52:53 +0000 From: rubyamateur@wbml.net To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47900 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: lubyamateur 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS45Es8E4EaCDNgaP+Obq1kxsgkCCkZ+XyXdaw rk2G0q0hLSkjiMG3vHeFdCi4vtsExhUkjkfQxolCHA7A0ilynuZWetnhPdMCEwsmkavZ6XKpfELU+t q79STYVcFjlPoklVm5HxQcMWu6WYm8CD+iba9AiTkabtY6e35pn+2JZAEQ== X-ML-Name: ruby-core X-Mail-Count: 73293 Subject: [ruby-core:73293] [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 Amateur. Jeremy Evans wrote: > I think "responsibilities" here applies to contributors, as they are the ones responsible for not violating the CoC by disrupting the community, posting personal attacks, etc.. > > In regards to "practices", notice that the definition states "...social norms and rules and responsibilities of, or proper practices for..." (note the "or"). A document that outlines the social norms, rules, and responsibilities without mentioning practices still meets the definition of a CoC. As in ruby: (true or false # => true) I think a succinct way of putting it is "responsibilities" is being mindful of others and practices is "etiquette." ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56522 * 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) -- https://bugs.ruby-lang.org/