Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90204 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50719 invoked from network); 6 Jan 2016 16:59:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2016 16:59:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.48 mail-wm0-f48.google.com Received: from [74.125.82.48] ([74.125.82.48:35427] helo=mail-wm0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/74-21755-DD74D865 for ; Wed, 06 Jan 2016 11:59:10 -0500 Received: by mail-wm0-f48.google.com with SMTP id f206so66717027wmf.0 for ; Wed, 06 Jan 2016 08:59:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=AHePdBFqvGM5zVeisyjUH16KzO+xZwxuMabW39uXsLQ=; b=MEYrpQwIf37rH8jTZmHT3x3d5h+f4X3CDy5wCmWpt1AjWI8EaJlR3qGA/55uho0Wnj 5YQWwYPOlKt/L0RFpAGVlBBrcydmIeaLxMVHK68ZKdIMF6Z7OcwwTzm9zry75wQZkFz/ /SMavgPCKr80YeBnpcSVUk9uF8NpPXRriEwJW71uZbGF311tmPq40ts0qEylpGS1qEzM QH/tr/VRBzGZjbRQ71mRg5ggKoT16TfHpfLF6M84NIrf754johzGzRtatLvJ8bczqXYm cxVLEIXz/wjeLKWFZMnxA/yxkvvBR2KfLGlz28LNea1L1X7B0cZRUVddPoTcUPid2v2G a24A== X-Received: by 10.28.0.79 with SMTP id 76mr12098786wma.27.1452099546826; Wed, 06 Jan 2016 08:59:06 -0800 (PST) Received: from [192.168.0.137] ([93.188.182.58]) by smtp.googlemail.com with ESMTPSA id e9sm96898193wjp.18.2016.01.06.08.59.05 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Jan 2016 08:59:05 -0800 (PST) To: internals@lists.php.net References: <568C9ED7.30504@gmail.com> <568D4220.3050309@php.net> Message-ID: <568D477A.9090402@gmail.com> Date: Wed, 6 Jan 2016 16:57:30 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <568D4220.3050309@php.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct From: rowan.collins@gmail.com (Rowan Collins) François Laupretre wrote on 06/01/2016 16:34: > So, let's analyze what happened when I was accused of 'sabotage' and > 'strong-arming' because I had sent a supposedly offending mail to > Sara. In my reply, I published the mail in question so that everyone > could judge by itself whether it was offending or not. I'm glad we > didn't have a PHP official SJW team because it would have probably > denied me the right to publish the message, for confidentiality > reasons. So, instead of putting the case in the public space where > everyone could see that the accusation was highly exagerated, I would > have been judged by 5 people who could have banned me on subjective > matters (let's not underestimate cultural differences here). Just to play devil's advocate: the flipside of this is that you posting the message in the public sphere could be seen as appealing to the crowd to back up your interpretation. Just because more people are looking at the message, doesn't mean they're looking at it more objectively. Note that I am absolutely not saying this is what you were doing, just extrapolating to a hypothetical situation where the same action could have a very different motivation and impact. I'm also not sure what the solution is, but there's a compromise to be made somewhere between "all accusations will be discussed in an unaccountable private court" and "all accusations must be discussed in full public view". Regards, -- Rowan Collins [IMSoP]