Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77542 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28476 invoked from network); 23 Sep 2014 15:57:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2014 15:57:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.43 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.43 mail-qa0-f43.google.com Received: from [209.85.216.43] ([209.85.216.43:53355] helo=mail-qa0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/91-20247-D7891245 for ; Tue, 23 Sep 2014 11:57:50 -0400 Received: by mail-qa0-f43.google.com with SMTP id i13so1772749qae.2 for ; Tue, 23 Sep 2014 08:57:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kaSSiJNPAuYQBK56DfNaZqYyOq2sgVFp7UR+uXPCFLY=; b=GkAUXEKk3hHcKbHNfhrlQv8Gj+Y2X8TOwbpVSS6DLo1hLzprvcViXZxbQYFF5JnRuz XnwuNAI84I3MqAQUZkFYyL24fQm3nbsQBlcpRORlXUl3fzgOlGuVXSlbZQlMrHE3KOK5 DYU+Pw98ealedl+i/sOsgFIqL/AowEk9bIYHH/7j7mR/XZfv/bM+8IiSGwS6mqiKXjPD yj4JVTowHCo+1ugajLIRXNpdDZfelPSap2W0V9jJ1WcRACxn6lM79+9QLpwPLAhtzKqq +BBuaFCQIfRtI4CBb16GQ/UTjN2xVKZ4/c261gjq96Pk/WWj1P5Y8gPo4dGiIXRhkvhm Q8uw== MIME-Version: 1.0 X-Received: by 10.224.7.197 with SMTP id e5mr849022qae.58.1411487867475; Tue, 23 Sep 2014 08:57:47 -0700 (PDT) Received: by 10.140.91.14 with HTTP; Tue, 23 Sep 2014 08:57:47 -0700 (PDT) In-Reply-To: <54208461.8020906@sugarcrm.com> References: <4D27A10E-6EC6-4806-94DB-1BF1B976CA7D@ajf.me> <600A7E27-7E6F-4ECF-805F-D62814AA3AB2@ajf.me> <54208461.8020906@sugarcrm.com> Date: Tue, 23 Sep 2014 17:57:47 +0200 Message-ID: To: Stas Malyshev Cc: Andrea Faulds , PHP internals Content-Type: multipart/alternative; boundary=001a11c223f4f227c30503bda092 Subject: Re: [PHP-DEV] [VOTE][RFC] Integer Semantics From: tyra3l@gmail.com (Ferenc Kovacs) --001a11c223f4f227c30503bda092 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Sep 22, 2014 at 10:19 PM, Stas Malyshev wrote: > Hi! > > > I didn=E2=80=99t close it because the time suited me most. I made an ho= nest > > mistake and closed it 22 or so hours early because I forgot I=E2=80=99d > > opened the vote at ~23:00 and not ~02:00. Unfortunately, I realised > > my mistake after merging the patch. This was definitely not > > intentional. > > That's why we should not rush to merge changes on a vote when there are > significant objections. There's nothing that mandated this change to be > merged immediately after the voting closing, as far as I can see. Yes, > we do not want to make the process endless, but it's better to wait just > a bit and ensure everybody is satisfied or at least reasonably listened > to. Begging people off-list to retract the votes and then close it > earlier on a very marginal result definitely looks like gaming the > system, even if the intent was not to do that. But the intent is only > known to one person, and the actions can be seen by all, so I think it's > better to take extra care here. We want the voting to be means of > enhancing the consensus, not something that would leave people losing > the confidence in the whole process. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > yeah, and when there is like 12 minutes between the last required vote casted and the vote being casted(almost a day earlier), it is easy to jump to conclusions. but putting that aside, what do we do now? Personally I agree that it is a valid concern that some people could have missed the voting period because of this: We already discussed recently that even a week is a bit short (anybody can have a week of vacation etc.) but that is the minimum mandated by the voting rfc, and seeing how close the vote was, I think it would be a good idea to extend the voting. What do you think? ps: I would prefer not reverting the change to save some work/history obfuscation in case if the result stays. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a11c223f4f227c30503bda092--