Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90129 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62315 invoked from network); 5 Jan 2016 19:08:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 19:08:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=peter.e.lind@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=peter.e.lind@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: peter.e.lind@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-wm0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:33363] helo=mail-wm0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/7F-12097-1C41C865 for ; Tue, 05 Jan 2016 14:08:49 -0500 Received: by mail-wm0-f54.google.com with SMTP id f206so34752440wmf.0 for ; Tue, 05 Jan 2016 11:08:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WtY/dS95/e+MbNHc84/RMxvWtnr18An6NhhVyNKbuHY=; b=Q+jv8+ZAHgvihARHqqxeDEtqZY/xDyjtqfTZSqfvQvoIX6yQFO3iHxDIXoz474oH5I 1ELon4vsyp6hVEhBXfi+ZHOfwFODuHQVjFbtYGZEjJAsZZFlQ0wlnTJolXBI4fOA5qdx mcNq26vziGcwIajL0BiFfrDSQSWi4w9v1O4kBFxxHkMQQdVU3Qr+8Rvw/w4cMwOCG/G0 6OvL7O5WAd7EWoVIJmkV8EMmw+yXiFLHyk7ub65/CohOj8axripfQz33CXcKjrnDpZWm bJfOKe0HwCiFAUxJqjwbYo6rULzkFyifbdrg43+Vwq2x0PdCg/vz6y3bzds3gGJ9o1q5 JcHw== X-Received: by 10.194.238.231 with SMTP id vn7mr117567884wjc.109.1452020926519; Tue, 05 Jan 2016 11:08:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.21.78 with HTTP; Tue, 5 Jan 2016 11:08:26 -0800 (PST) In-Reply-To: <568C0EA9.4080800@gmail.com> References: <568AE803.1080209@gmail.com> <568B0C8E.3080206@eliw.com> <568B1041.1060601@gmail.com> <568B1DA8.3060908@gmail.com> <568C0EA9.4080800@gmail.com> Date: Tue, 5 Jan 2016 20:08:26 +0100 Message-ID: To: Stanislav Malyshev Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c37a3a881ddf05289af7ab Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: peter.e.lind@gmail.com (Peter Lind) --001a11c37a3a881ddf05289af7ab Content-Type: text/plain; charset=UTF-8 On 5 January 2016 at 19:42, Stanislav Malyshev wrote: > Hi! > > > It's interesting to note how few people in this thread consider the > > perspective of potential harassed or abused people - instead only > > focusing on how to protect the accused. > > We do not discuss it much because it is a) covered in the RFC thus > forming context of the discussion and b) most of it is non-controversial > - we know hurting people is bad, we should not do it, and we should not > accept such behavior in our community. It is *how* we achieve that which > is the question for discussion. > > That is the problem: you cannot discuss how to protect the accused without having the context of the abused. As you have yourself pointed out with examples, it is a tradeoff. > > Quick check: how many times in the history of PHP has someone been > > called out, wrongly, for being abusive or harassing others? If, as seems > > There was some amount of "meta" discussions, in which all kinds of > complaints and counter-complaints were voiced, many times. But since we > have no formal mechanism for "accusing" or for determining "wrong", we > can't really know how many of such cases there were. > > > to the argument ("we're such a great and tolerant community, we don't > > need this"), this hasn't happened - what's with the paranoia behind > > assuming it will suddenly happen constantly and that people will be > > banned left and right for no reason? > > Because unfortunately we have witnessed, in other communities, how > applying such things too hastily and without due consideration can cause > damage. While abuse is undeniably damaging, doing more damage, this time > by ourselves, is not the right way to fix it. > > That is a truism: doing more damage is not fixing anything. However, unless I am mistaken, you yourself put forward the lack of explicit problems as an argument in favour of not doing anything. A middle way could be - like we're doing now - discuss options that amount to more than doing nothing (status quo) and less than voting in the worst possible option. > > voting is allowed. Even in the most clearcut case where someone is being > > a complete asshole, you're then either allowing them to continue the > > harassment or ignoring your own point. It's hard to see how either > > option benefits PHP, let alone the abused person. > > In most clearcut case where somebody is obviously misbehaving, we have > plenty of people that can revert commits or remove people from ML. That > happened in the past. We do not need a special troika for that. > Ah, I mistook the idea of using the RFC to handle problems with conduct to be a general way to deal with things. -- WWW: plphp.dk / plind.dk CV: careers.stackoverflow.com/peterlind LinkedIn: plind Twitter: kafe15 --001a11c37a3a881ddf05289af7ab--