Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86400 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99028 invoked from network); 27 May 2015 13:29:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2015 13:29:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:39101] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/D0-26265-6C6C5655 for ; Wed, 27 May 2015 09:29:43 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 0A7106D2045; Wed, 27 May 2015 15:29:38 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on h1123647.serverkompetenz.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.5 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from w520phpdev (p579F3035.dip0.t-ipconnect.de [87.159.48.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 1B53D6D2044 for ; Wed, 27 May 2015 15:29:38 +0200 (CEST) To: "'Internals'" Date: Wed, 27 May 2015 15:29:28 +0200 Message-ID: <063f01d09881$2bbf12d0$833d3870$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdCYe+dK7v1H+glZS6CSIRkaLYRjdA== Content-Language: en-us Subject: Pull request labels handling From: anatol.php@belski.net ("Anatol Belski") Hi, the PRs on github are already being labeled. Multiple labels are possible. However the github ACLs lack on granularity https://help.github.com/articles/permission-levels-for-an-organization-repos itory/ . Due to that, while being a useful feature, labeling is only available for project admins or alike. Now with PHP7 such labeling becomes probably even more sense as we'll need to handle BC breaks and other situations which would need more testing and care. So the amount of work to evaluate and review PRs will grow while the "work team" probably not. To improve this, here's an idea originally coming from Ferenc. And it is simple - the labeling feature could be integrated with our systems using the github API. That would allow to achieve more granularity on who is allowed to label. AFAIR there was already some people willing to do labeling, so that were a great possibility to build such a team. Such pre evaluating and labeling could possibly prevent some awkward situations, help to sort out potential issues and BC breaches. Thus asking for opinions. As it stands completely open - does this idea sound eligible, how can it be integrated, who is yet up for the pre evaluation/labeling job? Or any other propositions. Regards Anatol