Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91158
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.48 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
In-Reply-To: <alpine.DEB.2.20.1602091208150.7348@whisky.home.derickrethans.nl>
Date: Tue, 9 Feb 2016 16:17:09 +0100
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <C34531BA-CD09-44CB-8757-712DF66EA9F3@heroku.com>
References: <alpine.DEB.2.20.1602091208150.7348@whisky.home.derickrethans.nl>
To: Derick Rethans <derick@php.net>
Subject: Re: [PHP-DEV] [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress
From: dz@heroku.com (David Zuelke)

Thanks for the work, Derick. Looks good!

(aaand I just top-replied :p)


> On 09.02.2016, at 13:33, Derick Rethans <derick@php.net> wrote:
>=20
> Hello!
>=20
> Things have quieted down around the Code of Conduct and Contributor=20
> Guidelines process, but I have not been sitting still. In the last =
week,=20
> the following things happened:
>=20
> - I had a call with the Drupal Community Working Group - as suggested =
by=20
>  Larry Garfield. Stanislav was on the call as well.
>=20
>  Take aways:
>=20
>  - Texts should be void from ambiguity.
>=20
>  - Although their CWG dealt with plenty of cases, no punitive action=20=

>    has occured as parties would often step back themselves. In most=20
>    cases, a gently reminder was all that was necessary.
>=20
>  - We should be reluctant to limit the scope of the Code of Conduct =
and=20
>    Contributor Guidelines.
>=20
>  - A Code of Conduct without *any* 'teeth' would not be beneficial.
>=20
>  - We should start with suggesting/nominating people for the Mediation=20=

>    Team *before* deciding on the procedures and guidelines that=20
>    they should mediate around. The underlaying reason is that if the=20=

>    team is known upfront, there ought to be more understanding for the=20=

>    general developer community. Or in other words, there should be no=20=

>    reason that "I would only put my friends on it".
>=20
>    I do however have a few people in mind that I will reach out to=20
>    privately, to see whether they are interested. If you have any=20
>    suggestions for people that you consider reliable, considerate, and=20=

>    empathic, please reach out to them yourself, or let me know and I=20=

>    will.
>=20
> - The RFC text has seen a few updates as well.
>=20
>  - @jessamynwest improved some of the text for "encouraged behaviour"
>    =
https://github.com/derickr/php-community-health/commit/134670974b000483c2a=
179a02fc05a6d2de85d97
>  - @hnrysmth imported some new phrases from the Contributor Covenant=20=

>    1.4 over
>    =
https://github.com/derickr/php-community-health/commit/8ca9fe70538b036a938=
acbafa5f5f27f91228602
>  - @connerbw added a more general blurb about PHP and the commitment =
of=20
>    the PHP team to be inclusive
>    =
https://github.com/derickr/php-community-health/commit/e6c33f4b81975f2b2f2=
7919e37c585322f829a1c
>  - I combined the three bits of text around mailinglist posting=20
>    guidelines into the Contributor Guidelines=20
>    =
https://github.com/derickr/php-community-health/commit/7c55d1dd407524cdab5=
93b885e6b3101bf590769
>=20
> I feel that the "Contributor Guidelines" are now in a reasonable shape=20=

> to do a quick poll to gauge acceptability. As this is not a formal RFC=20=

> vote, it's simply done through an online poll:=20
> http://twtpoll.com/y6hs4ndsfiki485
>=20
> Voting is non-binding, and will end at Friday February 12th, at noon
> UTC.
>=20
> Feel free to reply here with suggestions, comments, etc.
>=20
> cheers,
> Derick
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20