Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78565 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80023 invoked from network); 2 Nov 2014 21:55:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Nov 2014 21:55:18 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.115 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.115 smtp115.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.115] ([108.166.43.115:54728] helo=smtp115.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/32-62688-548A6545 for ; Sun, 02 Nov 2014 16:55:17 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp23.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 740732801FC; Sun, 2 Nov 2014 16:55:14 -0500 (EST) X-Virus-Scanned: OK Received: by smtp23.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 214EC2801EA; Sun, 2 Nov 2014 16:55:14 -0500 (EST) X-Sender-Id: smalyshev@sugarcrm.com Received: from Stass-MacBook-Pro.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net [108.66.6.48]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.3.2); Sun, 02 Nov 2014 21:55:14 GMT Message-ID: <5456A841.8050001@sugarcrm.com> Date: Sun, 02 Nov 2014 13:55:13 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: John Bafford CC: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] GitHub Pull Requests Triage Team From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! >> I would like to propose the creation of a team to triage the pull requests >> on GitHub, to help ensure that the pull requests are handled in a timely >> manner. I am also volunteering to lead such a team, should the RFC be >> approved. I've read the proposal, and the idea of labeling the PRs and having reports looks good. The only thing I would be more careful about is closing the requests - 2 weeks sounds a bit too aggressive, I'd chose something like a month. Inactive pull does not consume any resources, and it's much better to have a pull lie around for some time and be picked up when somebody has time to look at it than to bury it and lose a contribution. Many PRs also get stuck in limbo because they either need some minor modification that the original author does not provide because he either lost interest or unaware of the need, or need somebody interested to push the discussion forward. In the former case, it would be nice for someone to make the minor change, which is mostly the question of time investment. In the latter, it's more the question of need - does somebody need this change enough? Closing such requests would be ok provided it'd be easy to resurrect them in case somebody gets interested. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/