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 (smtp.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 2F5B919E0032 for ; Thu, 21 Jan 2016 03:45:24 +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 1ED93B5D8CD for ; Thu, 21 Jan 2016 04:19:05 +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 28A0218CC7D1 for ; Thu, 21 Jan 2016 04:19:05 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 03258120479; Thu, 21 Jan 2016 04:19:01 +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 5073212040F for ; Thu, 21 Jan 2016 04:18:58 +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=MUECreRPgPMKa4nork4YnJCLCRA=; b=cHsZAEqqjVZHhfCwhe ww6t6HUyrsCdN5aLUh1n1MbuU5VoYMZ377WabKgf7xhHazNHxL9Jsl6LKXMAsUQF 3PV12+owXU8hZtdVf+4moR32+gqtVnaJMYP2ysWDwbIj61LHIkLVW2Cqk2wyekNY loXHOGUre8HxCeBCEUXxnKg5Q= Received: by filter0490p1mdw1.sendgrid.net with SMTP id filter0490p1mdw1.8117.569FDD9D58 2016-01-20 19:18:53.640063088 +0000 UTC Received: from herokuapp.com (ec2-54-145-248-20.compute-1.amazonaws.com [54.145.248.20]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id hMJbo5q_StS1ewEorzgGbg Wed, 20 Jan 2016 19:18:53.503 +0000 (UTC) Date: Wed, 20 Jan 2016 19:18:53 +0000 From: naruse@airemix.jp To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47603 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12004 X-Redmine-Issue-Author: CoralineAda X-Redmine-Issue-Assignee: matz X-Redmine-Sender: naruse 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4bPw2BOxr1iA1QQwcdVYLjwdrKUxd4yhS2cK w+VWdrDbSzjfPrfSRUJVFvIiSeDtd+DKoriZsa92jEHE5PA8trvGjAETkq/JIhHSJtrBrmwKHfe5iy WG6Np4cO089aDutHH7mgSxKOk50rhHiXtZYT X-ML-Name: ruby-core X-Mail-Count: 72994 Subject: [ruby-core:72994] [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 Yui NARUSE. Laws is born to solve the real problem. So laws shall be designed to solve the real problem. I know CoC is born because of real problems. And it seems trying to solve some problems with some preconditions. As far as I understand, it solves harassments under projects whose privilege is distributed. Under such projects issues around membership is tough issue. I can imagine predefined blacklist of actions helps to make a consensus. On the other hand, Ruby is generally the honest dictator model. The source of all privilege is derived of the creator, Matz. Ideally he doesn't need a consensus (but he is enough honest to respect a consensus). So I don't understand why CoC is required for Ruby. I know sometimes written list of rights and responsibility is important like Bill of Rights. But you intend to limit Matz' right? As far as I remember Matz did his best for at least 16 years (I use Ruby 16 years; I don't know before that at real time). I believe Matz to handle his ability better than written text. Anyway keeping more options is good habit. People can fork Ruby with 2-clause BSDL, which is considered to be compatible with MIT License. (The license change is proposed because of GPLv3 compatibility but I proposed more flexible license instead of Ruby's, GPLv2, and GPLv3 triple license) People sometimes really forked Ruby. Some committers including me seem to have the option to get a better programing language if it is required. About the CoC text, he definition of "Project maintainers" is not clear in the Ruby project yet. Some people may think committer is them. (As above I personally think the Maintainer of Ruby is Matz) If so, I can't understand committers who agree this CoC without acquiring privilege to achieve those responsibilities. I believe laws must work well, and people under a law must work to keep the law works well. ---------------------------------------- Misc #12004: Code of Conduct https://bugs.ruby-lang.org/issues/12004#change-56214 * 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/