Re: RFC: RFC Workflow & Voting (2019 update)
| From: | Andrey Hristov | Date: | Sat, 02 Feb 2019 10:10:21 +0000 |
| Subject: | Re: RFC: RFC Workflow & Voting (2019 update) | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104019@lists.php.net to get a copy of this message | ||
On 2.02.19 г. 3:41 ч., Johannes Schlüter wrote:
On Do, 2019-01-31 at 14:28 -0500, Bishop Bettini wrote:How do you define "top 13 committers"? How do you prevent people from playing the system by committing typo changes in comments etc.? Will somebody who rewrites a larger change into a single commit be negatively ranked compared to somebody who creates a small fix which requires multiple small fixes afterwards? I don't think quantity of anything (lines changed, commits, ..) is a good metric in any way. Either the list of contributors has to be inclusive or people have to be elected (with all the issues of electing people) johanes2. Core developers are defined as the top 13 committers within the period of two years since voting began. A core developer is a defactocommunity member, but caucuses as a core developer.--- a.txt 2019-02-02 12:09:50.405436313 +0200
+++ b.txt 2019-02-02 12:09:46.733163725 +0200@@ -1 +1 @@ -johanes +johannes you mean? Cheers, Andrey