Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90259
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.174 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
In-Reply-To: <CAEZPtU5BaogkrJ4H9o1x9ENWXOVqnAye8Oh535aTHOefMuJz6w@mail.gmail.com>
Date: Thu, 7 Jan 2016 10:08:09 -0600
Cc: Anthony Ferrara <ircmaxell@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3AB5AA82-4F17-40C3-B8B5-33697A8DBEC2@gmail.com>
References: <BE0EB5B804BC488AAD1344BF9D3B9277@gmail.com> <66E04ACF-7363-4E47-BFFD-E380E5B1EA23@gmail.com> <CAL=_i_kspY_v0Z-WvPdUAc3-_YfNC_a=59nUrLuW65G97+qZTg@mail.gmail.com> <6D.39.21755.3576D865@pb1.pair.com> <1AD1B991-A3E5-4D6C-A532-5F0FCCC2ED61@gmail.com> <CAObuZdtKyJXVEAtJzvZENf+Da6S+BFCnXaErvmiHJXen9DCDmA@mail.gmail.com> <568D7C5D.9020405@php.net> <CAAyV7nFYYxZELZhgo_wrhr9u2+Lww1jQAw+3O=fGqLJJdg7GkA@mail.gmail.com> <1e6a13607a3a1c8b20a4649f8a5ef767@mail.gmail.com> <CAEZPtU5BaogkrJ4H9o1x9ENWXOVqnAye8Oh535aTHOefMuJz6w@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: pmjones88@gmail.com ("Paul M. Jones")

Hi all,

As I have stated previously, I find the Contributor Covenant text =
objectionable, in that it couples person, project, and politics, so that =
the person becomes answerable to the project for their politics.

If there simply must be a code of conduct, they should be decoupled. To =
that end, I propose that the entire "Code Of Conduct Text" in the RFC be =
removed, and replaced with this single sentence:

    We are committed to evaluating contributions within project
    channels without regard to the contributor's experience,
    ability, identity, body, religion, politics, or activity
    outside of project channels.

Alternatively, if that's not specific enough, use this single sentence =
instead:

    We are committed to evaluating contributions within project
    channels (such as reporting issues, posting feature requests,
    updating documentation, submitting pull requests or patches,
    and other project activities) without regard to the
    contributor's level of experience, gender, gender identity
    and expression, sexual orientation, disability, personal
    appearance, body size, race, ethnicity, age, religion,
    nationality, politics, or activity outside of project
    channels.

Both of these use language cribbed from the Contributor Covenant, and =
add explicit protections for politics and other activity outside the =
project. This decouples person, politics, and project from each other, =
leaving each with its own separate sphere of influence. It also removes =
the scope of resulting actions-to-be-taken from the expectations of =
conduct, and leaves it to the conflict resolution language.

The replacement is restricted to project channels only. I predict, based =
on earlier comments, that some will object to this. I opine that it is =
beyond the scope of the project to either reward or punish members for =
their activity outside channels owned by the project. Even so, conflict =
in non-project channels does occur. As such, I suggest adding the =
following text (or substantially similar text) to the conflict =
resolution language:

    Q: What about conflict outside of project channels?

    A: If you feel conflict via a non-project channel is
    unbearable, you should handle the incident(s) using the
    means provided by that channel. For example:

        - If you feel you are being abused via Twitter, you
        might block or mute the person(s) you feel are abusing
        you, and/or report the abuse to Twitter.

        - If you feel you are being harassed via email, you
        could set up a rule to delete or junk emails from the
        person(s) you feel are harassing you.

        - If you feel you are subject to a credible threat of
        physical harm, you should report it to law enforcement.

Finally, although the original RFC text does not define "project =
spaces", I think that "project channels" should be defined; for example, =
the official PHP accounts on Github, Twitter, and Facebook, as well as =
all php.net mailing lists, and perhaps even all php.net email accounts.


--=20
Paul M. Jones
pmjones88@gmail.com
http://paul-m-jones.com

Modernizing Legacy Applications in PHP
https://leanpub.com/mlaphp

Solving the N+1 Problem in PHP
https://leanpub.com/sn1php