Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65233 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77742 invoked from network); 28 Jan 2013 11:19:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2013 11:19:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.214.177 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.214.177 mail-ob0-f177.google.com Received: from [209.85.214.177] ([209.85.214.177:57793] helo=mail-ob0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E2/06-28517-3DE56015 for ; Mon, 28 Jan 2013 06:19:48 -0500 Received: by mail-ob0-f177.google.com with SMTP id wc18so1294391obb.22 for ; Mon, 28 Jan 2013 03:19:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:references:in-reply-to:mime-version:x-mailer :thread-index:date:message-id:subject:to:cc:content-type :x-gm-message-state; bh=u6rccsInd/F/QDU2tNUVvsG5kJWIOIBpm2AAduxTooY=; b=L6snh98zMzoO73sNV0ywb/H2tRaE+Dhc93FKtpgvbzu2A8lt5XZeNyjlxGEVUgSnOH Tw1Pqee4MLLoTcwpJ83KysePCdrDHqIIaDRq3mqTeOjDj0Hf91iPYcz/B/hhs00T67Uu tnKfofYlS5YKkmbOWxSYjlPNM0YhQh02UTLjNvjI/l3MnnAPHjrjTziPJ+RaiAasKOeL 3imPlhaNib5TDt/MS831fb1jJboF7QVLwU3+p/HPYYuCfUW53uW7l1ZXlcSq35lzVe7E Go7g2nJrXZAuI4cXYsit7rz2WQrfB1779+2m4vPWHjkpk2z3TTN/mKIqQ5WBjrzzyA0Q agAQ== X-Received: by 10.60.169.205 with SMTP id ag13mr10957467oec.40.1359371985239; Mon, 28 Jan 2013 03:19:45 -0800 (PST) References: <76a9565b2a095a72063a68f106a6b457@mail.gmail.com> <5ed6711b24349c82b7c17dd450ff7c80@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQItj407fvbyyHusXdfq7WqB3TBWzwH/50DcAYH7XhQC750pEZdr5U5w Date: Mon, 28 Jan 2013 13:19:44 +0200 Message-ID: <7165e8331e1070234771f7ae9573cdf8@mail.gmail.com> To: Pierre Joye Cc: PHP internals Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQk9sV9bWTQ1CP0FAGJv/Ku7MFob+MzTF8WFmJAlTbvPIkZslgtGVbH/e/SpYW5CKMnZ+rbFobmWzEwD8utBBCOP0lBGEXi0FdVy6tUXt4nyPofJLobIM/seba9tRo00gyV4BCAl Subject: RE: [PHP-DEV] Voting periods From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Pierre Joye [mailto:pierre.php@gmail.com] > Sent: Monday, January 28, 2013 1:07 PM > To: Zeev Suraski > Cc: PHP internals > Subject: Re: [PHP-DEV] Voting periods > > hi, > > On Mon, Jan 28, 2013 at 11:57 AM, Zeev Suraski wrote: > >> > My suggestion is for voting periods to be limited to one week, > >> > regardless of the topic. It should be more than enough. > >> > Regardless, > > an 'open > >> ended' > >> > voting period is unacceptable IMHO. > >> > >> You were one of the person who requested to have at least two weeks, > >> so nobody can miss a vote due to various reasons (on the road, off > >> time, or whatever else). I'd to keep two weeks. > > > > Well the way it is right now it's a 'one week by default', unless > > there are reasons to extend it, which IIRC was the compromise. I find > > it difficult to believe that had this particular RFC been in an 'accepted' > > position back on Wednesday the 23rd, the vote wouldn't have > > immediately closed... > > I find somehow disturbing that you raised that for the RFC you don't like, that > has to be said :) That's fair, but it's the only one of 6 open RFCs right now that has an intentional open-ended ending date. > You also, if I am not mistaken, changed your vote during the > week. I was never in favor of this feature, in all of its different incarnations. I did not change my vote. > That's all good, but changing rules to get the results we wish is not going > to happen. I feel that this is what was done in this particular case, not the other way around. That what brought me to bring up that subject here in the first place. This particular RFC was the only RFC where I noticed this weird 'no sooner than' language, and it seemed intentional to me - given the fact it's a very controversial feature opposed by most core devs. If we want to change the default voting period to two weeks, that's fine - but IMHO it should be for future RFCs after it gets approved. > > In my opinion - based on our actual experience now as opposed to > > theoretical predictions which we had back then - one week should be > > enough as the default. But I'm fine going with two weeks. I guess > > we'll vote on that too :) It's more important to have a definite end > > date than whether it's one week or two weeks. > > One week is too short, I'd to go with two weeks minumum, end date must be set > when a vote begins, to avoid any confusions. > > I will add a vote on that in the voting RFC, as un update, so we will a clear(er) > position for the next RFCs. OK, please put a one week as an option too. To put things in perspective, elections that effect the fate of billions of people typically end in 24hrs. Zeev