Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90008 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82558 invoked from network); 4 Jan 2016 21:45:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2016 21:45:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.178 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.178 mail-pf0-f178.google.com Received: from [209.85.192.178] ([209.85.192.178:36621] helo=mail-pf0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CC/0D-07292-708EA865 for ; Mon, 04 Jan 2016 16:45:44 -0500 Received: by mail-pf0-f178.google.com with SMTP id 65so163202312pff.3 for ; Mon, 04 Jan 2016 13:45:43 -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=CJdB0CQO6A5ctbJTeJ3Ng4ZzzzCwuwTUkFZeTYYBuB0=; b=riLgwhzlNkiu0v+1KAroIdCCWo0J5YY9j0T9wCGHJ8Ko7KkO7CKUgAnDi9CnlMi+v9 JT57k2BaUC2kK1ewY0fmFlo6+meRtYntYXmT0AFtZV1w/MYuUeQ48/9jZr+gQET2UBiP 12d4cFNi5uBRXsBZTYNSezLy4ce0rw4U+Cnp57o/748uEQOfi+8dBZ2W7s851+ChAis3 drG9miL04Mtb8xJcou5H3fBqQBtQKvE0Umxkw/VWBD9HPxe1b5JtGmWs82BWRWqEIFEA RMpFIQhJUq50oz5U9GgGARvfsCRFgoUqDMDpxZ43RAA3vNOv0PRJw3Tx0Jy8ZHOrv4Go pQHw== X-Received: by 10.98.64.27 with SMTP id n27mr85320027pfa.141.1451943941126; Mon, 04 Jan 2016 13:45:41 -0800 (PST) Received: from Stas-Air.local ([205.154.255.147]) by smtp.gmail.com with ESMTPSA id e67sm93513559pfd.7.2016.01.04.13.45.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jan 2016 13:45:40 -0800 (PST) To: Anthony Ferrara , "internals@lists.php.net" References: X-Enigmail-Draft-Status: N1110 Message-ID: <568AE803.1080209@gmail.com> Date: Mon, 4 Jan 2016 13:45:39 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct > > Let me know what you think or if there are any concerns Looks to me like solution in search of a problem. I'm with PHP project since 90s, and maybe it is my biased view, but with all heated and sometimes very controversial discussions, people rage-quitting and swearing oaths to never have anything to do with PHP again, etc., that we have had over these years I can remember maybe a handful of instances where there were - at least in public spaces of the mailing lists - comments that may be suspicious within the framework described in http://contributor-covenant.org/version/1/3/0/code_of_conduct.md. Even in those instances, I'd be hard pressed to remember any instances that would constitute actual intentional harassment. Maybe I'm biased, but as it looks to me, we may have a lot of issues with discussions on the list and in general about how we conduct things, and there was a lot of critique about that over the years, but this does not seem to be the problem we have. Going into the specifics of the RFC, we can already do all things the CoC committee is proposed to do, and I don't remember any case where it was needed - i.e., where a commit had to be reverted or commit karma had to be revoked for harassment, over 20 years history. Was there such a case? If it happens that this is needed, we have mechanism to police commits & pulls. We do not have any mechanism for instituting bans (again, I don't remember us ever needing one - maybe my memory is faulty?) but I think such thing should not be done by 5 people. It should be an exceptionally broad consensus. That consensus would be especially hard to reach when, as RFC states, nobody but those 5 people (and, I assume, the author of the complaint) would not even know the details of the issue, and as the accused would be banned from wikis and mailing lists, thus unable to provide explanations or defend themselves, no semblance of due process can be preserved. If we ever need the procedure for such measures - which I highly doubt - it should be only performed with very broad consensus (minimum 2/3 with high quorum requirement so 4 people voting on holiday week-end couldn't pass such decision) and allow for the accused the chance to explain and provide their point of view. -- Stas Malyshev smalyshev@gmail.com