Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91143 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54311 invoked from network); 9 Feb 2016 12:33:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2016 12:33:53 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Received: from [82.113.146.227] ([82.113.146.227:36742] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7D/F1-39202-FACD9B65 for ; Tue, 09 Feb 2016 07:33:52 -0500 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id A26A210C7EF for ; Tue, 9 Feb 2016 12:33:48 +0000 (GMT) Date: Tue, 9 Feb 2016 12:33:48 +0000 (GMT) X-X-Sender: derick@whisky.home.derickrethans.nl To: PHP Developers Mailing List Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: [VOTE] Contributor Guidelines, and Updates to Code of Conduct progress From: derick@php.net (Derick Rethans) Hello! Things have quieted down around the Code of Conduct and Contributor Guidelines process, but I have not been sitting still. In the last week, the following things happened: - I had a call with the Drupal Community Working Group - as suggested by Larry Garfield. Stanislav was on the call as well. Take aways: - Texts should be void from ambiguity. - Although their CWG dealt with plenty of cases, no punitive action has occured as parties would often step back themselves. In most cases, a gently reminder was all that was necessary. - We should be reluctant to limit the scope of the Code of Conduct and Contributor Guidelines. - A Code of Conduct without *any* 'teeth' would not be beneficial. - We should start with suggesting/nominating people for the Mediation Team *before* deciding on the procedures and guidelines that they should mediate around. The underlaying reason is that if the team is known upfront, there ought to be more understanding for the general developer community. Or in other words, there should be no reason that "I would only put my friends on it". I do however have a few people in mind that I will reach out to privately, to see whether they are interested. If you have any suggestions for people that you consider reliable, considerate, and empathic, please reach out to them yourself, or let me know and I will. - The RFC text has seen a few updates as well. - @jessamynwest improved some of the text for "encouraged behaviour" https://github.com/derickr/php-community-health/commit/134670974b000483c2a179a02fc05a6d2de85d97 - @hnrysmth imported some new phrases from the Contributor Covenant 1.4 over https://github.com/derickr/php-community-health/commit/8ca9fe70538b036a938acbafa5f5f27f91228602 - @connerbw added a more general blurb about PHP and the commitment of the PHP team to be inclusive https://github.com/derickr/php-community-health/commit/e6c33f4b81975f2b2f27919e37c585322f829a1c - I combined the three bits of text around mailinglist posting guidelines into the Contributor Guidelines https://github.com/derickr/php-community-health/commit/7c55d1dd407524cdab593b885e6b3101bf590769 I feel that the "Contributor Guidelines" are now in a reasonable shape to do a quick poll to gauge acceptability. As this is not a formal RFC vote, it's simply done through an online poll: http://twtpoll.com/y6hs4ndsfiki485 Voting is non-binding, and will end at Friday February 12th, at noon UTC. Feel free to reply here with suggestions, comments, etc. cheers, Derick