Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90489
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A0C1936C-FDAD-4B67-934B-EA612C3EBCEA@gohearsay.com>
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> <56936C66.2050006@gmail.com> <A0C1936C-FDAD-4B67-934B-EA612C3EBCEA@gohearsay.com>
Date: Mon, 11 Jan 2016 08:58:23 -0500
Message-ID: <CAFi=QfaM++hwE3wt_uO1Pk=skKjhjG8wF7cVxRuk2ThYyVkorw@mail.gmail.com>
To: Kevin Smith <kevin@gohearsay.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1140ef92c0377e05290f55be
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: oldschooldsl@gmail.com (Adam Howard)

--001a1140ef92c0377e05290f55be
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I question if there is a way to keep all communication in PHP Internals on
PHP Internals, which would minimize the risk of someone reaching someone
outside of PHP Internals.  By that I mean, as it stands now, everyone's
email is public and someone meaning to cause or threaten harm could
personally target someone.  Would it not be better if a system was designed
to generate an anonymous email and only official PHP Team Members would
know the true identity.

Thankfully, I have never read or see any abuse within PHP Internals or
among The PHP Development.  I am somewhat surprised to read this and I too
am alarmed.  I've experienced some less than appropriate contact elsewhere,
but never within PHP.  I do not doubt the possibility, though.

On Mon, Jan 11, 2016 at 8:46 AM, Kevin Smith <kevin@gohearsay.com> wrote:

>
> > On Jan 11, 2016, at 2:48 AM, Stanislav Malyshev <smalyshev@gmail.com>
> wrote:
>
> >
> > So, we have a situation where we have a mismatch between a problem and =
a
> > solution, and that is what the misunderstanding is based on. You and
> > several other people try to prove something we already agree about -
> > that certain problems exist - and forget to prove something that needs
> > to be proven - that what you propose would solve *these* problems in an=
y
> > acceptable way. Instead, the solution (at least part of it) is designed
> > to solve *different* problems, which nobody showed we even had. This
> > mismatch is an issue.
>
> This is my chief concern with the proposal. We keep seeing allusions to
> problems of toxicity and tone and the like all the while being assured th=
at
> the proposal does not seek to dictate behavior or punish people for
> defending their position passionately.
>
> If the latter is true, what=E2=80=99s the use in making a case that certa=
in people
> and/or communication channels aren=E2=80=99t friendly enough?
>
>
> Kevin Smith
> Hearsay Interactive <http://gohearsay.com/>
>

--001a1140ef92c0377e05290f55be--