Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90020
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.194 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <568B0C8E.3080206@eliw.com>
References: <CAAyV7nFbngZ42qzbSFyveH+vsyir9QNtMJq8H=u9VqTBVBv5Og@mail.gmail.com>
	<568AE803.1080209@gmail.com>
	<568B0C8E.3080206@eliw.com>
Date: Tue, 5 Jan 2016 07:30:53 +0700
Message-ID: <CAEZPtU6oKG1aHWCb2YUFXPv5bU1E16w__QDZ2HmV-q_KRSceqQ@mail.gmail.com>
To: Eli <eli@eliw.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Jan 5, 2016 at 7:21 AM, Eli <eli@eliw.com> wrote:
> On 1/4/16 4:45 PM, Stanislav Malyshev wrote:
>> Looks to me like solution in search of a problem. I'm with PHP project
>> since 90s, and maybe it is my biased view
>
> As someone who originally was hesitant to do something similar with his
> conferences.  I can speak that the reason for such a proposal is not
> "because we have a problem".
>
> It's a pro-active step, which makes it clear to people who are not a
> part of our community at the moment, when they happen to approach our
> community, and perhaps, are interested/intrigued about joining it.  That
> yes, it will be a safe environment for them to do so.
>
> Without such a statement.  They would have no way to determine that,
> other than reading 10 years worth of internals+reddit+etc.
>
> To that end, it's a great step, and I will +1 vote for it when it comes
> up.   Thanks for putting it forward Anthony.

I fully agree here.

To start to think about it or adopt one when a problem happens will be too late.

The effort to create and adopt a CoC is minimal and the benefits are
huge. It creates, confirms or ensure that the context of the php.net
remains a safe for anyone to contribute.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org