Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78864
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain requinix.net designates 209.85.220.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1415641205.23992.20.camel@kuechenschabe>
References: <EB032A39-EB24-4BBE-A2D3-14BF63809873@zort.net>
	<1415641205.23992.20.camel@kuechenschabe>
Date: Mon, 10 Nov 2014 12:06:15 -0800
Message-ID: <CAAg69rkRibqPbDX736L3qGpty+BkjScsDe9NtJiDi_NcLTj2pQ@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: John Bafford <jbafford@zort.net>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team
From: php@requinix.net (Damian Wadley)

On Mon, Nov 10, 2014 at 9:40 AM, Johannes Schl=C3=BCter
<johannes@schlueters.de> wrote:
> The second issue is that we're doing a bad job at handling bug reports,
> (https://bugs.php.net/stats.php) there are only very few guys who go
> through reports and handle those. This simply is a lot of work affecting
> areas which reviewers probably don't really know. For helping there when
> doesn't have to be a code contributor i.e. requinix afaik never proposed
> a patch (sorry if I missed it!) but does a very good job answering to
> bug reports.
Thanks. While I know C fairly well and don't have a problem reading
the PHP source, I wouldn't trust myself to write a patch for anything
more than a trivial fix :(

And I figure there are a decent number of people like me too: they may
not be able to contribute to the source but they have been working
with PHP for years, know it well, and would be able to help triage
bugs. The main problem that I've heard is that it's not easy to figure
out what they can do without a php.net account; I generally tell them
that they can ask for more details or backtraces when needed, test on
their own systems, make documentation patches in the DOE, even trudge
through the old bug reports if they're really bored (I don't mind the
few clicks to close bugs if someone else spends the time to find
them!).

-Damian/requinix