Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90377 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82295 invoked from network); 8 Jan 2016 17:51:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2016 17:51:59 -0000 Authentication-Results: pb1.pair.com header.from=derokorian@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=derokorian@gmail.com; spf=pass; 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: derokorian@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-wm0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:33068] helo=mail-wm0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/15-55593-E37FF865 for ; Fri, 08 Jan 2016 12:51:58 -0500 Received: by mail-wm0-f54.google.com with SMTP id f206so145124871wmf.0 for ; Fri, 08 Jan 2016 09:51:57 -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=6uwlbhGgu27ChJcu0gibKrfvRiHUNLGTmrXTj2KM2Nw=; b=dZsL1BePKUEtuCcWtwcPXn7Jc/6HuOtKqkoEGg3rsCyM2mgzRgGJQhYP/RwyxQl5a+ XDuog0KsTs/TnQCHcl1nY+gmzFkrhQXXQIQ8TXjROKOrf/BvtioYhmPgbJHSHzC8Vvdv 8DxD3bbw5F0F0/d5uG4jzmGiKao+gV1ZQhGRqhVgRV0KGBtaNCEsRv0SEMNyvVDzcgrV kDZ8P7mnUBqTlhQCR0H0BOAgPTUA1gx6iICiVq2/v/7aI5BQyXRMva2NqDXgk/8P39me OcYzOCJQtGPuihsDJEc01V6Thlr1hAGtv8YFC5TGNcSwyeBjSwx+PeL9+5TB2UQaPhn4 AzMA== MIME-Version: 1.0 X-Received: by 10.194.216.100 with SMTP id op4mr102228624wjc.85.1452275515191; Fri, 08 Jan 2016 09:51:55 -0800 (PST) Received: by 10.28.98.133 with HTTP; Fri, 8 Jan 2016 09:51:54 -0800 (PST) In-Reply-To: <2732F2A4-51F7-42CC-A7E7-1EC7B26CDF97@gmail.com> References: <66E04ACF-7363-4E47-BFFD-E380E5B1EA23@gmail.com> <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> Date: Fri, 8 Jan 2016 10:51:54 -0700 Message-ID: To: "Paul M. Jones" Cc: Larry Garfield , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e014935f432fc5e0528d63ee4 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: derokorian@gmail.com (Ryan Pallas) --089e014935f432fc5e0528d63ee4 Content-Type: text/plain; charset=UTF-8 On Fri, Jan 8, 2016 at 10: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? > I would prefer to see the team picked for the next occurence immediately after one happens. This way, if the resolution can be handled by just having a calm conversation with the interested parties, then there is no need to make it public. Instead, the mediators would say "A conflict has occurred and a new team needs to be in place". Or maybe something like 1 month duty at a time, but team membership may last beyond a month, if no conflicts were had during that month. IE, you get put on the team, you may "serve" for a year if no conflicts arise. Or you may only server for a month, if a conflict does arrive (I think an upper bounds when no conflicts may not be required, but should be considered if this suggestion is taken to heart at all). > > > -- > Paul M. Jones > pmjones88@gmail.com > http://paul-m-jones.com > > Modernizing Legacy Applications in PHP > https://leanpub.com/mlaphp > > Solving the N+1 Problem in PHP > https://leanpub.com/sn1php > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --089e014935f432fc5e0528d63ee4--