Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104009 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 34002 invoked from network); 2 Feb 2019 05:01:04 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 2 Feb 2019 05:01:04 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-120-213.dynamic.mnet-online.de [188.174.120.213]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 72628523FC; Sat, 2 Feb 2019 02:41:19 +0100 (CET) Message-ID: <1549071678.26811.6.camel@schlueters.de> To: bishop@php.net, Zeev Suraski Cc: PHP internals list Date: Sat, 02 Feb 2019 02:41:18 +0100 In-Reply-To: References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] RFC: RFC Workflow & Voting (2019 update) From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Do, 2019-01-31 at 14:28 -0500, Bishop Bettini wrote: > >    2. Core developers are defined as the top 13 committers within the >    period of two years since voting began. A core developer is a de > facto >    community member, but caucuses as a core developer. 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) johanes