Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90869 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71942 invoked from network); 24 Jan 2016 04:52:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2016 04:52:30 -0000 X-Host-Fingerprint: 176.248.2.57 unknown Received: from [176.248.2.57] ([176.248.2.57:20671] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/3B-03822-C8854A65 for ; Sat, 23 Jan 2016 23:52:28 -0500 Message-ID: <56.3B.03822.C8854A65@pb1.pair.com> To: internals@lists.php.net References: <56A25C2D.3060903@anderiasch.de> Date: Sun, 24 Jan 2016 04:52:24 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 176.248.2.57 Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct From: ajf@ajf.me (Andrea Faulds) Hi Derick, Derick Rethans wrote: > On Fri, 22 Jan 2016, Florian Anderiasch wrote: > >> On 22.01.2016 15:29, Pierre Joye wrote: >>> >>> Freshly adopted: >>> >>> http://rubyonrails.org/conduct/ >>> https://golang.org/conduct >>> >> >> Ruby (the language) is discussing the adoption of a Code of Conduct >> right now, and several people in that thread issue what I think are >> similar concerns about the wording in the covenant one: >> >> https://bugs.ruby-lang.org/issues/12004 >> >> AFAICT Rails adopted exactly that one, not sure about slight changes. >> >> FWIW, I like the Go one a lot better. > > I do too. I think there is a lot we can borrow from that. I'll probably > use the weekend to draft the first bit of my suggested process: THe > values document. Expect things from other "codes" to come back into it. The Go one looks pretty great to me. It might not be such a bad idea if we were to adopt it almost verbatim. I'm concerned that the code of conduct RFC, since its introduction, has ballooned in length and complexity, and I don't think it's really done any good. I don't like the idea of having to read pages upon pages of regulata to know what our values and rules are. I also don't think we need to write anything new. Other people have done that legwork for us, we are wasting our time if we try to create something new. PHP is not radically different from other open-source projects. Go's one is not excessively long, gets to the point, and is reasonable. It appears to cover everything we need: positive values, what is unacceptable, a statement of why moderation is needed, and how to report issue and how it will be handled. I'm not sure yet, but if we were to adopt a code from another project (which I think we should definitely do), Go's looks like a good choice. Thanks! -- Andrea Faulds https://ajf.me/