Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90118
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <568BFF63.3080403@garfieldtech.com>
References: <CAAyV7nFbngZ42qzbSFyveH+vsyir9QNtMJq8H=u9VqTBVBv5Og@mail.gmail.com>
	<568AE803.1080209@gmail.com>
	<568B0C8E.3080206@eliw.com>
	<CAEZPtU6oKG1aHWCb2YUFXPv5bU1E16w__QDZ2HmV-q_KRSceqQ@mail.gmail.com>
	<568B1041.1060601@gmail.com>
	<CAEZPtU7dpgh65Nzs61wPmckvPx4sfT4y+8P3fAfJoLyQfb5mxw@mail.gmail.com>
	<568B1DA8.3060908@gmail.com>
	<CADajX4Aur47K4_TnkhScUw6RfA+1LMoDi3JKT9zc0oGJ0EiaAQ@mail.gmail.com>
	<a94b087e3efebf4e8948b79d19d1f565@mail.gmail.com>
	<568BD0CA.7040909@php.net>
	<CAEU6NAeX+PXGOYVc-EE0P5y-LmfG8OsmLzhSNLqHDhSvkTcQmg@mail.gmail.com>
	<568BE845.2090102@php.net>
	<alpine.DEB.2.20.1601051607280.4541@whisky.home.derickrethans.nl>
	<CAEZPtU5T6HnbmNYu0qHBax0SoS+OxnutZZ=fWTquRJt5=pom0g@mail.gmail.com>
	<568BFF63.3080403@garfieldtech.com>
Date: Tue, 5 Jan 2016 19:03:21 +0100
Message-ID: <CAH-PCH5qUNJiAvB0V1_NpKsf7CLJ7satvHEs_HsNGnmNVj1U5w@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114435f4a0339105289a0d9f
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a114435f4a0339105289a0d9f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 5, 2016 at 6:37 PM, Larry Garfield <larry@garfieldtech.com>
wrote:

> On 1/5/16 11:08 AM, Pierre Joye wrote:
>
>> Anyway, I don't say that it cannot happen, I just say that, AFAIK, we
>>>> never got such concerns in the PHP community.
>>>>
>>> Sorry - not true. I can name several issues from various PHP related
>>> conferences. Although not directly under the "control" of the PHP
>>> developers team (and hence not influenced by a proposed CoC), they're
>>> certainly part of the community.
>>>
>> Same here. And in the core as well. Even relatively recently.
>>
>> I would love to see more focus on how to make this out in a fork we can
>> all
>> agree on instead of arguing about the rights of one or the other, all
>> parties will have the same rights. Or to argue about whether such bad
>> event
>> can happen or not. It will too late to do it when it will happen again.
>> This alone is a good enough reason to do it, now.
>>
>> About anonymity, it is also critical during the whole investigation and
>> afterwards. The reasons are rather obvious for both parties and have bee=
n
>> explained here.
>>
>> A quick but well thought reaction is vital. In case of an harassment, th=
e
>> group can take measure and "officially" request to stop any private
>> contact
>> with the victim. Whether the accused person is guilty or not is not
>> relevant at this stage. It will help to protect both parties.
>>
>> I am also convinced that we need one  now more than ever before. Not
>> because we have more issues (or less) but because we are in a position n=
ow
>> to actually setup such CoC in a good way. And we are also the leading we=
b
>> programming language. We must ensure that we act accordingly. I also tru=
st
>> us to have the structure to manage such situations in a fair manner.
>>
>> Cheers,
>> Pierre
>>
>
> Who would like to be connected with the Drupal people in this space, if I
> can get their time?  I figure Anthony and Stas are good to include there
> (proposer and someone with well-reasoned concerned). One or two more peop=
le?
>
> --
> --Larry Garfield
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Maybe Sarah and Paul and with that we covered every angle :)

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a114435f4a0339105289a0d9f--