Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90030 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38017 invoked from network); 5 Jan 2016 01:14:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 01:14:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.82.47 mail-wm0-f47.google.com Received: from [74.125.82.47] ([74.125.82.47:36022] helo=mail-wm0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/F5-07292-BF81B865 for ; Mon, 04 Jan 2016 20:14:36 -0500 Received: by mail-wm0-f47.google.com with SMTP id l65so5643733wmf.1 for ; Mon, 04 Jan 2016 17:14:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oqHV4AaEJUnNxFMMhH2Al+lOlh4ojEeIVeEs/CX7sos=; b=LDtRYB2L3ifNj4UbMiiJNU4SX+Qvh65UkLONFCIG6AR2Rt6oVRe79Dry8Adb+OIl31 8oNPXWEjsWYZ8tb8MikvFKBa1lbSWfSx/n/mBmJc0nGOig/4MCqsqMK/W9SI0LYoFpKW 6mnXL4hFMOKF7rto/q/T9xtieZW2wCe/R6LdcNkV80uUb7JdVgBIcPGw1QAIhH1NId4I AgfH/34G0PJaNS7uqDana+j+uW9m50GojRP5NTFPvDQmVj4ScAKN30ljwMHgHhzamuDi /Q9Zi/b2hln6vy+/dpYJBVg1Ubi5RCrQJ8YcOFY0pCARLq3shzBPkqJS73LaU8rQHO0T SZ4g== MIME-Version: 1.0 X-Received: by 10.194.120.226 with SMTP id lf2mr98485337wjb.108.1451956472938; Mon, 04 Jan 2016 17:14:32 -0800 (PST) Received: by 10.27.86.202 with HTTP; Mon, 4 Jan 2016 17:14:32 -0800 (PST) In-Reply-To: <568B149C.50902@gmail.com> References: <568AE803.1080209@gmail.com> <568B0C8E.3080206@eliw.com> <568B1041.1060601@gmail.com> <568B149C.50902@gmail.com> Date: Tue, 5 Jan 2016 02:14:32 +0100 Message-ID: To: Stanislav Malyshev Cc: Pierre Joye , Eli , PHP internals Content-Type: multipart/alternative; boundary=089e0117738fcc8a8805288bf56f Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: tyra3l@gmail.com (Ferenc Kovacs) --089e0117738fcc8a8805288bf56f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 5, 2016 at 1:55 AM, Stanislav Malyshev wrote: > Hi! > > > currently I (and a bunch of other people) could revoke anybody's karma, > > how is this any different(ofc. it would be reverted and I would get a > > scolding)? > > The difference is that those 5(3) people get a special stand, while > right now everybody is equal (well, there are RMs but that is more > functional role). What these people are doing is assumed to be "fighting > harassment", and their target is assumed to be an offender, and thus in > the wrong. Moreover, they are empowered to silence that person just by > their own decision, without seeking consensus about it upfront. If you > or I did that - even in case where it is justified - it would raise some > eyebrows and get some scolding, as you correctly noted. So that's my > problem with it - that by this RFC, 3 people can do it with no consensus > at all. > > I can understand where are you coming from. > > we just have to make the process transparent and as mentioned in the RF= C > > any permanent action would require an RFC and consensus from the projec= t: > > "f the CoC team determines that a longer temporary ban or a permanent > > ban is necessary, they shall institute a temporary ban and raise an RFC > > to the general project to effect the desired ban. Once the RFC is > > issued, the temporary ban's lifetime will be tied to the RFC's lifetime > > (will expire when the vote is finished)." > > Which means while this RFC is discussed, the accused person remains > banned (thus unable to participate in any discussion). And, CoC is not > required to disclose much: > > The CoC shall report a redacted summary of the incident > /.../ > All incidents are to be kept in the strictest form of confidentiality. > The CoC team shall be the only group to know about the reporter and the > precise details of any incident. > > I.e. if 3 persons in CoC hate N and want to chase her our of the > project, they vote internally that she is guilty of "Other unethical or > unprofessional conduct", ban her from all community spaces and then tell > the rest of the community anything they like about what happened and > demand permanent ban. I don't think it is a good idea. > > for that to happen you need a corrupt CoC team, a fairly unknown N (otherwise there would be a bunch of people talking for him/her on the list to demand proof for the sanctions), the yet to be drafter part of the privacy part to allow the details to be kept back even if N wants it to be public and eventually N could still go public and prove his/her innocence while I can understand that he would be in an unfavorable position version the CoC team. but still, this to happen would need all of the above and the first controversial case would reveal the corruption of the members or the flaws of the process and we could fix that. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --089e0117738fcc8a8805288bf56f--