Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90401 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24626 invoked from network); 8 Jan 2016 20:17:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2016 20:17:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=derokorian@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=derokorian@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: derokorian@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wm0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:34668] helo=mail-wm0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BD/AD-55593-15910965 for ; Fri, 08 Jan 2016 15:17:21 -0500 Received: by mail-wm0-f52.google.com with SMTP id u188so150264830wmu.1 for ; Fri, 08 Jan 2016 12:17:21 -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=XZCNQREoYlmtvceUfTIfgOBxRxUkgSGUA0rya2ZtXF4=; b=Qvr8XW9RYTyAX85i+Xd9/e50veAzHAoKXA82aNWzcawupTgeHvndRrz8EyOUXanMmP /WeUronkDG0WmC6/6zbX/qakqv+1rwWscElaPjBLzFLEsA/GiOuz+zP2VurBLmv3yZab S2qz9flxLkQ0z8yAikNiDBJhZL3S3Igt+f+tjMU4SfjpdCKQkOP/lyRWTTb1hHoVOSAC sNOQNApzYYRqPgPB+B5PJvJ5WASxmGliswRGY3pX6gDtg+cyGZlRm/OszVjB2deszQEW IpK4u0YlJb9kh1rADVvrFiLDlP+tovgsmXC6ytIu3ptN1i/o38qQUPwXvMF/hycb1Psq vT0w== MIME-Version: 1.0 X-Received: by 10.28.68.68 with SMTP id r65mr726024wma.95.1452284238507; Fri, 08 Jan 2016 12:17:18 -0800 (PST) Received: by 10.28.98.133 with HTTP; Fri, 8 Jan 2016 12:17:18 -0800 (PST) In-Reply-To: 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> Date: Fri, 8 Jan 2016 13:17:18 -0700 Message-ID: To: "Paul M. Jones" Cc: Larry Garfield , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1148ea962639a00528d84601 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: derokorian@gmail.com (Ryan Pallas) --001a1148ea962639a00528d84601 Content-Type: text/plain; charset=UTF-8 On Fri, Jan 8, 2016 at 1:06 PM, Paul M. Jones wrote: > > > On Jan 8, 2016, at 13:50, Larry Garfield wrote: > > > > 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. > > (/me nods) > > If there must be a response team, I would prefer the "mediator" approach, > as you note. > > However, the RFC as I last saw it is not a "mediator" approach, but a > "judicial" one. If it is to be a "judicial" approach, my suggestion stands. > If/when the RFC changes to a "mediator" approach, I will change my > suggestions to fit the modified RFC. > Agreed, I think a mediator approach works best. I also agree with Zeev, that said mediator(s) should be picked not at random but for their ability to diffuse a situation. If a situation requires a "judicial" process, then I think at that point it should be a community decision. --001a1148ea962639a00528d84601--