Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90511
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain brandonsavage.net designates 209.85.213.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAAyV7nGEUSQ67Ptp_cqL0ZHFiAgs9HnCfjp1CfsO2VATnGY7Og@mail.gmail.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> <CALuPxdC64svDjOsK4z=gU8OurHDS6H0kFx7Re=G4xMrRxQU9Tg@mail.gmail.com>
 <CAAyV7nEQ3GySgPvoDB3Q7+pEXpK5zG0rue7s-VZYzX1j1EiHhQ@mail.gmail.com>
 <5693D1A4.2050208@gmail.com> <CAAyV7nGEUSQ67Ptp_cqL0ZHFiAgs9HnCfjp1CfsO2VATnGY7Og@mail.gmail.com>
Date: Mon, 11 Jan 2016 12:00:35 -0500
Message-ID: <CALuPxdB2vj9c1wqFEXL-j67AM0zQ+NWBgmavJ6fwH=p=V=iEmg@mail.gmail.com>
To: Anthony Ferrara <ircmaxell@gmail.com>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1135e154524c07052911e176
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: brandon@brandonsavage.net (Brandon Savage)

--001a1135e154524c07052911e176
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 11, 2016 at 11:26 AM, Anthony Ferrara <ircmaxell@gmail.com>
wrote:

> The CoC doesn't try to enforce itself outside
> of the scope of project members. Instead, it applies to project
> members wherever they represent the project.
>

So just to be clear, your intent is for the CoC to apply *only* to those
who actively participate in the project. Individuals who do not participate
in the project would not be subject to the CoC *or* the mediation team, and
complaints to the mediation team would be rejected as out of
scope/jurisdiction?

I think this is an important point to discuss, because it sets
jurisdictional boundaries for the project, but also sets intent for what
we're achieving here.

I think this is also important because things have a tendency to expand. We
need to have an answer if a conference organizer asks us to use our
mediation team to resolve disputes at their conference. Or an open source
project. Etc. I don't think we want to become the community's police
force/judge/jury.

This has been my chief concern all along: what to do about people who are
NOT a part of the project. I think the RFC ought to make that explicit.

Brandon

--001a1135e154524c07052911e176--