Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90011
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.173 as permitted sender)
To: bishop@php.net, John Bafford <jbafford@zort.net>
References: <CAEYWF=7LiYDJ1-YU=QYzWsXBewMy_AxZgp=SOqaLRGs5UuawNg@mail.gmail.com>
 <15D9C342-0BF3-4476-8473-A82E858781E3@zort.net>
 <CAEYWF=6b3iyDkBt7ke=v7LCR22kPPrF+hewm3vz4cPE7+kx70w@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <568AEBF8.1020508@gmail.com>
Date: Mon, 4 Jan 2016 14:02:32 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CAEYWF=6b3iyDkBt7ke=v7LCR22kPPrF+hewm3vz4cPE7+kx70w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Warn at 2 weeks, close at 4?  There's no real harm in closing it unmerged:
> the submitter can always resubmit.

That sounds way too short. I mean if we did process all worthy pulls in
matter of days, then fine (but see below) but we are very far from that.
And when we take a long time to get to it, we should allow some leeway
for them to respond too. So I'd say a year-old stale pull is might be
too old, but 1 month seems to be too soon. Somewhere between those
should be the optimal point :)

And I think RFC pulls should have longer time. Of course, people should
rather work in their private forks, but some people feel more
comfortable collaborating in pulls, and some RFC pulls take way longer
than 4 weeks, and people may take breaks and come back. Having a handful
of long-lived open pulls is not too much trouble.

-- 
Stas Malyshev
smalyshev@gmail.com