Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90115 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35164 invoked from network); 5 Jan 2016 17:37:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 17:37:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.28 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.28 out4-smtp.messagingengine.com Received: from [66.111.4.28] ([66.111.4.28:56516] helo=out4-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/4A-12097-56FFB865 for ; Tue, 05 Jan 2016 12:37:42 -0500 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9560D20B89 for ; Tue, 5 Jan 2016 12:37:39 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 05 Jan 2016 12:37:39 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=EbQgPqXDOSk0uzY pNEdEQWXSFfo=; b=hN/1XvyyPp25bQf8siP2bTp++XNblFrjTr4vd6T2vhrmQV+ jyh9x1Xcveu7RBxpJxQza5zHOdqzSLStlwYfesM9rrpBbJ+heqfofGyzuZDVgGR6 JqSltLWjAwP5pE+LFXz8qM9hoHuIMut+mudh8QBWyR60V2dNyseRvwsJXPgU= X-Sasl-enc: 1FczmJ8lrOA7J//Nx7mqa0yll9YDsNy/kR5f5sgy6ARm 1452015459 Received: from Crells-MacBook-Pro.local (unknown [63.250.249.138]) by mail.messagingengine.com (Postfix) with ESMTPA id 4C85D680136 for ; Tue, 5 Jan 2016 12:37:39 -0500 (EST) To: internals@lists.php.net References: <568AE803.1080209@gmail.com> <568B0C8E.3080206@eliw.com> <568B1041.1060601@gmail.com> <568B1DA8.3060908@gmail.com> <568BD0CA.7040909@php.net> <568BE845.2090102@php.net> Message-ID: <568BFF63.3080403@garfieldtech.com> Date: Tue, 5 Jan 2016 11:37:39 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: larry@garfieldtech.com (Larry Garfield) On 1/5/16 11:08 AM, Pierre Joye wrote: >>> Anyway, I don't say that it cannot happen, I just say that, AFAIK, we >>> never got such concerns in the PHP community. >> Sorry - not true. I can name several issues from various PHP related >> conferences. Although not directly under the "control" of the PHP >> developers team (and hence not influenced by a proposed CoC), they're >> certainly part of the community. > Same here. And in the core as well. Even relatively recently. > > I would love to see more focus on how to make this out in a fork we can all > agree on instead of arguing about the rights of one or the other, all > parties will have the same rights. Or to argue about whether such bad event > can happen or not. It will too late to do it when it will happen again. > This alone is a good enough reason to do it, now. > > About anonymity, it is also critical during the whole investigation and > afterwards. The reasons are rather obvious for both parties and have been > explained here. > > A quick but well thought reaction is vital. In case of an harassment, the > group can take measure and "officially" request to stop any private contact > with the victim. Whether the accused person is guilty or not is not > relevant at this stage. It will help to protect both parties. > > I am also convinced that we need one now more than ever before. Not > because we have more issues (or less) but because we are in a position now > to actually setup such CoC in a good way. And we are also the leading web > programming language. We must ensure that we act accordingly. I also trust > us to have the structure to manage such situations in a fair manner. > > Cheers, > Pierre Who would like to be connected with the Drupal people in this space, if I can get their time? I figure Anthony and Stas are good to include there (proposer and someone with well-reasoned concerned). One or two more people? -- --Larry Garfield