Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90880
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lange.demon.co.uk from 91.221.169.46 cause and error)
To: internals@lists.php.net
References: <alpine.DEB.2.20.1601201851500.3314@whisky.home.derickrethans.nl>
 <alpine.DEB.2.20.1601221028450.3314@whisky.home.derickrethans.nl>
 <CAEZPtU7QgfRp-ipT=H5BGbLQhWiUBxGHkuB2bb11nEvuJfag3g@mail.gmail.com>
 <56A25C2D.3060903@anderiasch.de>
 <alpine.DEB.2.20.1601221652090.3314@whisky.home.derickrethans.nl>
 <56.3B.03822.C8854A65@pb1.pair.com>
Message-ID: <56A4BB54.9000000@lange.demon.co.uk>
Date: Sun, 24 Jan 2016 11:53:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56.3B.03822.C8854A65@pb1.pair.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct
From: mark@lange.demon.co.uk (Mark Baker)

On 24/01/2016 04:52, Andrea Faulds wrote:
> 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 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.

The structure of the Go CoC is good.... starting with explaining why 
have one, and with the positive values emphasised before it gets into 
the what is unwelcome behaviour and what to do about it.... the emphasis 
is still on mediation, but it looks more positive from an outsiders 
perspective.

While the wording could be a bit different in places, the overall 
structure promotes the benefits and I'd like to see something similar 
for PHP. As one of those outsiders looking in, and occasionally 
considering contributing more, seeing something like that would make me 
feel a lot more comfortable about being more proactive

-- 
Mark Baker

  _________
|.  \     \-3
|_J_/ PHP |
|| |  __  |
|| |m|  |m|

  I LOVE PHP