Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89954 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79122 invoked from network); 1 Jan 2016 20:27:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jan 2016 20:27:19 -0000 Authentication-Results: pb1.pair.com header.from=jbafford@zort.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=jbafford@zort.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zort.net designates 96.241.205.2 as permitted sender) X-PHP-List-Original-Sender: jbafford@zort.net X-Host-Fingerprint: 96.241.205.2 nova.zort.net Received: from [96.241.205.2] ([96.241.205.2:52015] helo=nova.zort.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 97/41-06661-421E6865 for ; Fri, 01 Jan 2016 15:27:16 -0500 Received: from [10.0.1.2] (pulsar.zort.net [96.241.205.6]) (authenticated bits=0) by nova.zort.net (8.14.5/8.14.5) with ESMTP id u01KRD7X027498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jan 2016 15:27:13 -0500 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) In-Reply-To: <1451679654.4160.6.camel@kuechenschabe> Date: Fri, 1 Jan 2016 15:27:12 -0500 Cc: bishop@php.net, PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <9292F1F8-8344-4AFC-8102-EA147D081848@zort.net> References: <1451679654.4160.6.camel@kuechenschabe> To: =?utf-8?Q?Johannes_Schl=C3=BCter?= X-Mailer: Apple Mail (2.2104) Subject: Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team From: jbafford@zort.net (John Bafford) > On Jan 1, 2016, at 15:20, Johannes Schl=C3=BCter = wrote: >=20 > On Fri, 2016-01-01 at 13:28 -0500, Bishop Bettini wrote: >> Hi, and happy New Year! >>=20 >> Now that the big push for PHP 7 is done, I'd like to revive earlier >> discussions >> = >> on the *GitHub PR triage team* RFC = . >=20 > ... and we don't have the issue with GitHub only, but also with > bugs.php.net. But frankly I don't see the need for the RFC. This = simply > needs people to do the work. Anybody can leave comments and pester > committers. Everybody with php.net account additionally can close bus > and prs and assign bug issues. >=20 > Even if there is an RFC those volunteers are needed and could run away > any time.=20 >=20 > So if you have the spare time simply start! Be brave! I think the particular advantage of having an RFC (or if not an RFC, a = document somewhere describing the contents of the RFC) is so that = there=E2=80=99s a framework for the PHP project saying, =E2=80=9Cthis is = a desired thing we=E2=80=99d like to have as part of our normal = process=E2=80=9D, and in the event the people working on it step aside = from lack of time, it provides a much easier way of getting someone else = to pick up the mantle, since there=E2=80=99s already a document written = describing what we want to have happen. At the least, this is a request for comments, even if it doesn=E2=80=99t = actually require a vote, and there didn=E2=80=99t really seem to be a = better place to put the document at the time. >=20 > johannes >=20 >=20 >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php