Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90891 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46369 invoked from network); 24 Jan 2016 20:44:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2016 20:44:54 -0000 Authentication-Results: pb1.pair.com smtp.mail=slevy1@pipeline.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=slevy1@pipeline.com; sender-id=unknown; domainkeys=good Received-SPF: error (pb1.pair.com: domain pipeline.com from 209.86.89.64 cause and error) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: slevy1@pipeline.com X-Host-Fingerprint: 209.86.89.64 elasmtp-curtail.atl.sa.earthlink.net Linux 2.4/2.6 Received: from [209.86.89.64] ([209.86.89.64:59615] helo=elasmtp-curtail.atl.sa.earthlink.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/B0-42451-6C735A65 for ; Sun, 24 Jan 2016 15:44:54 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=pipeline.com; b=sNUIjWhfFNzOcRj3Xh4rRKoFKDZYPdzhUqm++wwOuS3SEA5oy8+f+puYDW5sHfvZ; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [108.215.225.25] (helo=sharonc67d61d6) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1aNRWf-0000SK-N5 for internals@lists.php.net; Sun, 24 Jan 2016 15:44:45 -0500 Message-ID: To: "PHP internals" Date: Sun, 24 Jan 2016 12:45:58 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-ELNK-Trace: ad108fc9e0b7e924cd4e711cd2c366965f08d759999b5662653afe43bbe9c60651dbfad31ba9f274350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 108.215.225.25 Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct From: slevy1@pipeline.com ("Sharon Levy") 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? 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? 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? 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.