Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90380
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9AC4BF2A-870F-46A1-AE13-454189FFCFD6@gmail.com>
References: <BE0EB5B804BC488AAD1344BF9D3B9277@gmail.com>
	<66E04ACF-7363-4E47-BFFD-E380E5B1EA23@gmail.com>
	<CAL=_i_kspY_v0Z-WvPdUAc3-_YfNC_a=59nUrLuW65G97+qZTg@mail.gmail.com>
	<6D.39.21755.3576D865@pb1.pair.com>
	<1AD1B991-A3E5-4D6C-A532-5F0FCCC2ED61@gmail.com>
	<CAObuZdtKyJXVEAtJzvZENf+Da6S+BFCnXaErvmiHJXen9DCDmA@mail.gmail.com>
	<568D7C5D.9020405@php.net>
	<CAAyV7nFYYxZELZhgo_wrhr9u2+Lww1jQAw+3O=fGqLJJdg7GkA@mail.gmail.com>
	<1e6a13607a3a1c8b20a4649f8a5ef767@mail.gmail.com>
	<CAEZPtU5BaogkrJ4H9o1x9ENWXOVqnAye8Oh535aTHOefMuJz6w@mail.gmail.com>
	<3AB5AA82-4F17-40C3-B8B5-33697A8DBEC2@gmail.com>
	<CAEZPtU6T14yr8UN1F0goY=7sme-iKgXLECSL7yiAqFLf_xPchw@mail.gmail.com>
	<FD56BF25-0825-4666-AEF9-06996E59C514@gmail.com>
	<CAEZPtU7nNuEQehisOZK3nC4AuafrahQbvLgZOGteR1jt4cWV_w@mail.gmail.com>
	<B1697F0F-883C-4D49-8CB6-4DF152662886@gmail.com>
	<8D90A4F6-4E3E-4283-B8E3-152E4707EF4E@moonspot.net>
	<568F4E81.1020205@garfieldtech.com>
	<2732F2A4-51F7-42CC-A7E7-1EC7B26CDF97@gmail.com>
	<CAObuZdvd2JhFG2QKVbaGwqfc4gMAkJCSgGO7Xp1uCP7C2Hi--w@mail.gmail.com>
	<9AC4BF2A-870F-46A1-AE13-454189FFCFD6@gmail.com>
Date: Fri, 8 Jan 2016 11:02:02 -0700
Message-ID: <CAObuZdsiX0Q14YbnzK9NgbF=WyRynWzqrsNWq7nYTzB45bf8rg@mail.gmail.com>
To: "Paul M. Jones" <pmjones88@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e014935f46c26310528d662af
Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct
From: derokorian@gmail.com (Ryan Pallas)

--089e014935f46c26310528d662af
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 8, 2016 at 10:58 AM, Paul M. Jones <pmjones88@gmail.com> wrote:

>
> > On Jan 8, 2016, at 11:51, Ryan Pallas <derokorian@gmail.com> wrote:
> >
> > I would prefer to see the team picked for the next occurence immediately
> after one happens.
>
> (/me ponders)
>
> That leads to an interesting hypothetical situation: if you know in
> advance that there's a particular team in place, you can (if a malfeasor)
> send bogus reports until a team you like is in place, then send your
> intended report.
>
>
> > 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).
>
> (/me nods)
>
> I think it leads to a similar situation: if you know the team that's in
> place, and you are a malfeasor, you can time your false-accusation to a
> team that is friendly.
>
> Granted, I am paying attention to ways to game the system, but since we
> can be sure it will be gamed, I think it's prudent to do so.
>
> Overall, I still assert that a reporter should not know in advance who
> will handle their report, other than "5 randomly chosen voting members"
> (similar to a jury pool).
>
>
These are good points, and I fully agree - which brings back the idea of a
dispatcher. Someone who receives a request, and press a button that
forwards it to 5 random people (preferably with mixed powers as mentioned
before).

OTOH, I don't really want to ever be randomly selected (but would fulfill
the duties required if selected, as I hope anyone on this list would).

--089e014935f46c26310528d662af--