Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90500
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gohearsay.com designates 50.116.30.253 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_96D5901F-0C33-4673-8133-4C7FAFC75DA2"
Message-ID: <D7EDD4FA-1DB1-4FEC-AAA6-1F13984E2FC0@gohearsay.com>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Date: Mon, 11 Jan 2016 09:33:53 -0600
References: <CAAyV7nFbngZ42qzbSFyveH+vsyir9QNtMJq8H=u9VqTBVBv5Og@mail.gmail.com> <CAAyV7nHrip8Ljxjdi2DiGbcnXxY9JK+pN+LCwYKqsjJNvEyUrg@mail.gmail.com> <910b145571b2c3e98338d54c0dd6a981@mail.gmail.com> <CAAyV7nGGJ3-mCZhDcmhcjqgEOMUBQwvA0vVEE67K4Vmot4ep5Q@mail.gmail.com> <CAPgLKii-L-TvKLiSYNdcXxmkr60k2_93EE7hc9LSL=3NQwQjRw@mail.gmail.com> <CAESVnVqrXQHpYabkOZvVhbGVUNtQLLS_h=OsnaaQWhEeHWx+uw@mail.gmail.com> <CAAyV7nGV4Vawdq67j0eZa4j+R2zM_14-KZpBe_S6JUOc7-9Yfg@mail.gmail.com> <0E9E4C89-1800-4000-BD5A-BC81F43BE2FE@gohearsay.com> <CAAyV7nEVKqOJWn9Fb7Sa2cAPRBZ-Pu00BOmha4ObGciwPHXiGQ@mail.gmail.com> <44142A2C-0E7C-4525-880F-7759CD8A502A@heroku.com> <5691D820.4080309@gmail.com> <56934116.70002@garfieldtech.com> <CALuPxdC64svDjOsK4z=gU8OurHDS6H0kFx7Re=G4xMrRxQU9Tg@mail.gmail.com> <CAAyV7nEQ3GySgPvoDB3Q7+pEXpK5zG0rue7s-VZYzX1j1EiHhQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <CAAyV7nEQ3GySgPvoDB3Q7+pEXpK5zG0rue7s-VZYzX1j1EiHhQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: kevin@gohearsay.com (Kevin Smith)

--Apple-Mail=_96D5901F-0C33-4673-8133-4C7FAFC75DA2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jan 11, 2016, at 9:11 AM, Anthony Ferrara <ircmaxell@gmail.com> =
wrote:
>=20
> Brandon,
>=20
> On Mon, Jan 11, 2016 at 8:47 AM, Brandon Savage
> <brandon@brandonsavage.net <mailto:brandon@brandonsavage.net>> wrote:
>=20
>> And that to me is the crux of the issue. When it comes to making
>> discussions on internals more civilized, governing a person's conduct =
*as
>> it relates to their participation in the discussion* is about as far =
as PHP
>> should go. A person who is not a party to the discussion, who does =
not
>> vote, but does have karma, who happens to tweet "I think X is a moron =
for
>> proposing Y" is entitled to that opinion, *until they bring it here.*
>=20
> While everyone is entitled to their opinion, sharing that opinion is
> potentially another story. I think the exact quote you bring here is
> one of the things a CoC is designed to prevent. I would absolutely
> consider it bad if one karma-holding individual calls another a
> "moron" at all in public for proposing an RFC. While we may disagree
> with someone, we should hold ourselves to a constructive standard. The
> vast majority of people here want to see PHP (as a project) improve.
> Even if we don't agree with how someone approaches that, we should at
> least hold ourselves to a level of mutual respect. Going out and
> calling someone a moron in public is not constructive nor respectful,
> and IMHO we as a project shouldn't sit back and blindly say "whatever"
> if it happens.


Ok, so given this continued line of reasoning, is this a fair summary:=20=


The goal of this proposal is to create a code and enforcement body that =
seeks to improve the content and tone of communications by and between =
members of the PHP community regardless of venue using punitive measures =
if necessary.


Kevin Smith
Hearsay Interactive <http://gohearsay.com/>=

--Apple-Mail=_96D5901F-0C33-4673-8133-4C7FAFC75DA2--