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 07F1919E003B for ; Thu, 21 Jan 2016 21:52:45 +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 AFB97B5D87F for ; Thu, 21 Jan 2016 22:26:26 +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 553AD18CC7B2 for ; Thu, 21 Jan 2016 22:26:27 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 20BA012043A; Thu, 21 Jan 2016 22:26:27 +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 74A7912040F for ; Thu, 21 Jan 2016 22:26:23 +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=eydu2kX83QXR9fpR6vdBrPzFaRI=; b=z2nRbb/qjPz/rbKsGM krXcKMvxJUBJwrMYs1cnnpCsGTkuWk5fsvQctWI/1NoTv24YHuT7myloqQbDFhHh Vf+UhVuFCgSI54bRfiwjkw8jPfw0MMkMZs+TmSgRI9vg193Oc3jTM4oveWrg9E2t mm7oxaoh46FlBqLaHOXiRmvIg= Received: by filter0507p1mdw1.sendgrid.net with SMTP id filter0507p1mdw1.18709.56A0DC797E 2016-01-21 13:26:17.917216672 +0000 UTC Received: from herokuapp.com (ec2-23-20-84-133.compute-1.amazonaws.com [23.20.84.133]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id M8sk2CQbSdCa8rux5qZZDw Thu, 21 Jan 2016 13:26:17.497 +0000 (UTC) Date: Thu, 21 Jan 2016 13:26:17 +0000 From: git@chuckremes.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47636 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: cremes 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7wf6HqnMQA+pStb6m8dfCL/98oWQlva6IbAG KEbFMeZN/Eiv8S4Q+0Fjc5AuLJcCbmWGLTTofRRD+6LNoa5iZvScDgVhnISOfQrsBaHldxpxRi5oQN gt9ZMlkFEZcLNEoYdbPOfD37U8m1Ypei82CLxU1F3U5ftsB0FKmTcLSTxA== X-ML-Name: ruby-core X-Mail-Count: 73026 Subject: [ruby-core:73026] [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 Chuck Remes. I am not in favor of the adoption of a CoC. If this solved a real problem, I would consider it as would any reasonable person. However, no one in this thread has been able to point to any situations where a CoC (and specifically, *this* CoC) would have solved the problem. Instead they say that we can't know if there are problems because those marginalized people have avoided the community. Their claim is not falsifiable. To me that makes the claim absolutely worthless. I do think we should learn a lesson from the Rubinius community (where I am an active contributor). Brian Shirai (brixen) recently banned Charles Nutter (headius) from the community. I have a real problem with this because I consider myself a friend of both men and it pains me to see this kind of rift. But we have clear evidence that a CoC can and *will be used* to ban someone for behavior and/or conduct outside of a project. In the aforementioned situation, Charlie was banned from the Rubinius project for participating in a thread ON TWITTER. He wasn't harassing Brian in a github issue, spamming a Rubinius mailing list, sending spurious PRs to the project, being a nuisance on IRC or gitter, or really doing anything related to the project other than commenting on a project's choice of release versioning. I think Brian's choice to ban him was unreasonable (and yes, I read his blog post explaining the action and the history leading to it). I hate having to write this because I *fear* that it may sour my relationship with Brian. I don't want it to as I respect him as a developer and as a person. If you follow my twitter feed and his you'll see that we are unlikely to agree on a good number of political issues. :) I haven't even brought up with topic with him (privately or otherwise) because of that fear of damaging our relationship. How would a CoC protect me? It wouldn't. In fact, it could be used to ban me too. I don't like having that kind of threat hanging over my head. Should I start censoring my political opinions on twitter now? Oh no, I'm considering a vote for Trump; is that actionable under a CoC? I've broken my silence on this topic because I can't bear to see another project be poisoned by a CoC. Please Matz, use your powers of Benevolent Dictator for Life and reject this CoC. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56248 * 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/