Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

2016-01-04 Thread 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 ge

Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

2016-01-04 Thread Bishop Bettini
On Mon, Jan 4, 2016 at 3:26 PM, Adam Harvey wrote: > On 1 January 2016 at 12:12, Bishop Bettini wrote: > > On Fri, Jan 1, 2016 at 2:53 PM, John Bafford wrote: > >> I think when I brought this up before, the major open discussion point > >> before the thread died was what period of time constitu

Re: [PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

2016-01-04 Thread Adam Harvey
On 1 January 2016 at 12:12, Bishop Bettini wrote: > On Fri, Jan 1, 2016 at 2:53 PM, John Bafford wrote: >> I think when I brought this up before, the major open discussion point >> before the thread died was what period of time constituted long enough for >> closing a waiting-on-submitter PR. 2 w

[PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

2016-01-01 Thread Bishop Bettini
On Fri, Jan 1, 2016 at 2:53 PM, John Bafford wrote: > > > On Jan 1, 2016, at 13:28, Bishop Bettini wrote: > > I think when I brought this up before, the major open discussion point > before the thread died was what period of time constituted long enough for > closing a waiting-on-submitter PR. 2

[PHP-DEV] Re: [RFC] GitHub Pull Requests Triage Team

2016-01-01 Thread John Bafford
Hi Bishop, > On Jan 1, 2016, at 13:28, Bishop Bettini wrote: > > Hi, and happy New Year! > > Now that the big push for PHP 7 is done, I'd like to revive earlier > discussions on the GitHub PR triage team RFC. > Thanks for poking me about this. When I originally proposed the PR triage team a