Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90398 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19593 invoked from network); 8 Jan 2016 20:01:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2016 20:01:14 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.44 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.213.44 mail-vk0-f44.google.com Received: from [209.85.213.44] ([209.85.213.44:33348] helo=mail-vk0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/AC-55593-98510965 for ; Fri, 08 Jan 2016 15:01:14 -0500 Received: by mail-vk0-f44.google.com with SMTP id i129so59443476vkb.0 for ; Fri, 08 Jan 2016 12:01:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zend-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=l7aBVwhuwHx6OybhrSbqJM/idq5jtHEhKGEfEWLaETg=; b=PDqdHABJpzIo7IWhpHKx+9Eahp94JSwb9aB8c9DyjnKAZAf7gjslvOIbkrOA1XPVPS X93uuebtXs8lT9nA7Ph8FKFpjThlYfAAp3VyOubcLBXEGqktolIqojVI6yRNhmcYijdJ nywSHTZhmo3iRpho/VsbNU1HAqF2+rvRadHkOQbupGAbvQsHTHgG8JHYg3gBO9xUOI+w wKTiJoRaF+AjOzERMYPHRSjLzr83a0tHEAwBoOfM1qrMStSM5Csc5oCc2Xpo4El2Y2Iz b0NR+FgGn+Hdg6S3XXbOKpRRZIrKwcKBBboF/Qi4dKqLqPVrH0I2eMwADVylCC3yx02u mUQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=l7aBVwhuwHx6OybhrSbqJM/idq5jtHEhKGEfEWLaETg=; b=FCPyDvbeBjBRmj/aK2NxNf11aM49qNgtMKVMzKJmJPicJAoxsukNu4821UJAmuTMVh AdaVyXnDoFbqc6Dw2L00dbrYZ/w4i33YF5ZH1SIa7nTkcX6LkJDsej05NwW50UIIk+wW jTAgVBEYvFub9ZXtNFgNM5v0Uc5qnlZNUipfLkF9S40DDfDGLZow08ZUTxXT5VoiMYxT OPPn5CQDiaXPrBP5cNKhfyl9jscYd/bey+rV9okjrAtlGatQ0ZoCOU9mG7ykd+EfXNkQ mDAKJbB0CkJHtpyYf+3HQABV4XEoBK5Esq/iCqgt8gUY+QZRpCyVNuFPIv/QJ1vR/17K X6zg== X-Gm-Message-State: ALoCoQkStmHEGYoDWyt/jNWzaOogv+nLTteXgE/cWBpImKYdSs4xIchZlRmd7Hs5ZRGZp5SqbEh+wqKI10EXuuqNgXb/SnvCW4lnTC7NbBv/yGAqHKUhYw8LTpFy8Mm5RqZWRlJlAXkWyyOc4ertoNzbz8t79xzOLgKYiDaJuUfCtvukZ9HrGMjIQnChoeoo7v5W71LgYHllWrDDFymonEnMtCas6JbrvQ== X-Received: by 10.31.164.78 with SMTP id n75mr46967819vke.14.1452283270567; Fri, 08 Jan 2016 12:01:10 -0800 (PST) References: <6D.39.21755.3576D865@pb1.pair.com> <1AD1B991-A3E5-4D6C-A532-5F0FCCC2ED61@gmail.com> <568D7C5D.9020405@php.net> <1e6a13607a3a1c8b20a4649f8a5ef767@mail.gmail.com> <3AB5AA82-4F17-40C3-B8B5-33697A8DBEC2@gmail.com> <8D90A4F6-4E3E-4283-B8E3-152E4707EF4E@moonspot.net> <568F4E81.1020205@garfieldtech.com> <2732F2A4-51F7-42CC-A7E7-1EC7B26CDF97@gmail.com> <568FFD08.1080104@garfieldtech.com> <2718DA23-C14B-427A-9FE8-C86918BAA00C@gmail.com> <5690130A.9050801@garfieldtech.com> In-Reply-To: <5690130A.9050801@garfieldtech.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHu5WcmVO8w6FQExoubxXKsnxz4JgKRMYPmAPmlqBwAvQIn5wIwcEL4ARLx4VMCSazT5QG3aSeRAs5mBhoB6AlwcwE4gUxsAZumLC8BjvV0awI4SH+KAgmqwCoB6UloGgH/aGoLARjvd2ABqNn2n526QBlQ Date: Fri, 8 Jan 2016 22:01:06 +0200 Message-ID: <9b86733fc00a8e2669464e4d2019395b@mail.gmail.com> To: Larry Garfield Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Larry Garfield [mailto:larry@garfieldtech.com] > Sent: Friday, January 08, 2016 9:51 PM > To: internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct > > On 1/8/16 12:31 PM, Paul M. Jones wrote: > >> On Jan 8, 2016, at 12:16, Larry Garfield wrote: > >> > >> On 1/8/16 11:28 AM, Paul M. Jones wrote: > >>>> On Jan 7, 2016, at 23:52, Larry Garfield wrote: > >>>> > >>>> Do you think we can find 5 people in the PHP community that we can > trust to make fair decisions (NOT that we would always agree with, but that > are fair) that don't fall too far into "thought policing", in *any* direction? If > not, then the community is already lost beyond all hope and we should all > just give up now. I do not believe that to be the case, at all. > >>> Too long spent in a position of power, and even the most fair can > become unfair. > >>> > >>> As I have suggested before: *if* there is to be a response team, let it be > randomly selected on per-reported-incident basis from the pool of voters. > Then there is no possibility of a charge of continuing bias, and it distributes > power among the pool, instead of concentrating it into a few members. > >>> > >>> Proponents of the response team: thoughts? > >> Randomly selected: Absolutely not. I wouldn't randomly select someone > to make Ultimate Decision(tm) on a technical RFC, either. But if a question > about, say, a parser bug came up there are absolutely certain people that I > would trust with that question more than others, and defer to their > analysis/opinion more readily. > > Certain people *you* would trust more than others, but that *others* > would not trust more. > > > > Also, this is a social/political realm, and not a technical realm; would you not > trust, say, a randomly-selected jury to hear and decide on a case? If not, why > not? > > As many people, including both you and I, have said, we don't want to focus > on the "jury" aspect. Rather, we want to focus on conflict resolution and > mediation, not on hammer dropping. And conflict resolution and mediation > is not even remotely a universal skill. No, I would not trust a "select a person > at random" as a "defuse a situation" > role, not even a little. As I said in my other note, I agree 100%. I think the problem is that the RFC right now goes well beyond mediation, and so far, I haven't heard willingness to let go of these extra elements or break them into a separate RFC. So we're, in effect, discussing several things at the same time, with this fundamental issue remaining undetermined. If it's a mediation team and not a judicial/jury one, then everything happening in private becomes a non-issue and very natural. Having the most skilled people to mediate becomes a no brainer, as there's no real risk for abuse of power. Deciding how these people get elected and where discussion happens should only happen after we establish what jurisdiction they have in the first place, otherwise, we're discussing it backwards IMHO. Zeev