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 D85AD19E0056 for ; Sat, 23 Jan 2016 21:41: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 1DD65B5D87C for ; Sat, 23 Jan 2016 22:15:36 +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 BCF4A18CC7AF for ; Sat, 23 Jan 2016 22:15:36 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id AE9521204F0; Sat, 23 Jan 2016 22:15:35 +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 E3B221204A5 for ; Sat, 23 Jan 2016 22:15:31 +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=rmKGvIQ1aLoWCYyQzf/TCpMw5wk=; b=FVnG5nxpktTJd8MsTp xMkjt1EQCfBe3zYz6pcEjhcHmZBMzPS3GM6so82aUAZPCJIasH9rAhbgADyMkCn3 rQVVJTc0s5aOlTKZPlCHQM0HOPq5kjnH6EcH7WrM4kw5Sf18Ps9JOBHbv6fD6rRk Gaft0/SBbyCN1wditklXa8ShE= Received: by filter0487p1mdw1.sendgrid.net with SMTP id filter0487p1mdw1.8755.56A37CEF3D 2016-01-23 13:15:27.755481566 +0000 UTC Received: from herokuapp.com (ec2-54-145-241-100.compute-1.amazonaws.com [54.145.241.100]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 4E8KzJWPSSWBWaeVTul8Ag Sat, 23 Jan 2016 13:15:27.374 +0000 (UTC) Date: Sat, 23 Jan 2016 13:15:26 +0000 From: 6ftdan@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47922 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: danielpclark 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS6sGs9QRlcwm3UxsLuGT78tHeeMEi7XguUSFI o6IzAtKb3KcsFxGYnGo+lfI+gAY6iWVszg1pIME+fdGDNhjAFaiYFXM1ts0flfvmV8Mi4iqXPtPZO8 34Wkwn3ThWpZYEKha2PA0U+lJlz0LY7kVzk8 X-ML-Name: ruby-core X-Mail-Count: 73316 Subject: [ruby-core:73316] [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 Daniel P. Clark. Olivier Lacan wrote: > It seems, however, that most of the reasonable participants of this thread agree that a more clearly defined code of conduct (whatever its final form) is a welcome addition. I disagree. I think this is merely your opinion on how the conversation has gone. I believe both sides have raised some good and reasonable points. Just because one side has used many more words does not mean that that side is the "most" of us all. It is important to consider all aspects here. There can be harm done by having a CoC and their can be harm done without a CoC. That will never change. The point I have tried to express is that both love and respect are things each individual can freely choose to give and no form of legislation can enforce that. Once the "law" has been written it not only limits all parties involved but it can, and will, hurt (ban/imprison) many who will unknowingly transgress it. No one here knows every law of their land and won't know if their breaking them. I believe it's better to be confident in life by not having to worry about a "law" looming over us and to simply love and respect others by our own free will. I have never read any CoC of projects that I've contributed to. As far as I know I've done what was right. But in truth I'm ignorant of the "laws" they've placed and if I've broken them. If they've written that I should read the CoC before contributing then that alone would be actionable for me to be banned. Then I would be the hurt party. Even though I was offering something good and with good intention the law would cause more damage than good in this situation. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56545 * 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/