Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90893 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50781 invoked from network); 24 Jan 2016 21:23:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2016 21:23:02 -0000 X-Host-Fingerprint: 176.252.240.88 unknown Received: from [176.252.240.88] ([176.252.240.88:28650] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/61-42451-4B045A65 for ; Sun, 24 Jan 2016 16:23:01 -0500 Message-ID: <19.61.42451.4B045A65@pb1.pair.com> To: internals@lists.php.net References: Date: Sun, 24 Jan 2016 21:22:57 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 176.252.240.88 Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct From: ajf@ajf.me (Andrea Faulds) Hi Sharon, Sharon Levy wrote: > After reviewing the proposed CoC, I wonder if its good intent might > boom-a-rang and have an opposite, chilling effect. I would respectfully > suggest re-thinking the notion of a CoC for the PHP project. Some > questions to consider: > > 1. Who is the CoC for, i.e. who should be its beneficiaries? Users, > core contributors and maintainers? All of the above? I'd say that a code of conduct would be for whole community. Its purpose is to keep the community a friendly and inviting place. That goal is surely one beneficial to everyone. > 2. What should a CoC seek? Is it the elevation of PHP culture so that > whether on the internals list or another forum there is less vulgarity > and crudity and more respect? That would be the idea, yes. > Or, is the purpose of the CoC really a > device to control perceptions, i.e. protect the image of the PHP project > and its citizens? Well, that would also be a benefit. I don't think these are exclusive goals. If PHP isn't inviting, people won't want to contribute. > If a CoC were to use language such as "guidelines" rather than the > anonymous authoritative language contained in the current proposal, I > think it would be more beneficial for encouraging productive discussions . > > We can have a more welcoming community and one in which people can feel > free to share their technical thoughts even if they are far beyound the > perimeter of the box if we emphasize the importance of each person > taking personal responsibility for their deportment rather than > attempting to dictate behavior. The idea of "taking personal responsibility for their deportment" reminds me a little too much of Soviet-era jokes about how the KGB would function once communism was achieved. Mostly-irrelevant musings aside, I don't think that simply asking people to be nice, on its own, is necessarily sufficient. At the very least, having people tasked with moderation means people get warned if they step over the line, rather than them doing it unaware. If you put up rules, not everyone will read them, or at least remember them in full. Thanks. -- Andrea Faulds https://ajf.me/