Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65239 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91594 invoked from network); 28 Jan 2013 12:53:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2013 12:53:31 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.179 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.217.179 mail-lb0-f179.google.com Received: from [209.85.217.179] ([209.85.217.179:64803] helo=mail-lb0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0C/18-28517-9C476015 for ; Mon, 28 Jan 2013 07:53:30 -0500 Received: by mail-lb0-f179.google.com with SMTP id j14so3766401lbo.24 for ; Mon, 28 Jan 2013 04:53:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SZS+wW/0VQ3LA4gT6N0kIz8ZLcLi6bqkLtgmtegvMP8=; b=Kos1s3sAc8IIi0aoVJ5fyrdxx+KsgXMVTfjEA+vty8gI2q+6yRx8npliyel6imjv1r +WNfAjjRs/NbmnwxZMKH5SglEnezlOA7DleIWzaJ+XOI+5K/skMWTYzvTsj0XQRmbjmo OJCbtHCYJtOasdHbIa2C33nmmyDU9kMZ6doZm6IwJpwXxqiPQH5o8JU0Inh/YIg2/9CY nvWLTSLx0TNowWV7JDB+pdGHWkrCJ0WHTUc5tLJ0+PbRhY7HdA7XbnbNRp9gJRYFGgUX /5s+aVGcmHyM4FXEkD1vWDR3FJIqDtQcKR5q/tc7rMenZE3NU2LNyr69Wfm6jgR0YYzc DzWw== MIME-Version: 1.0 X-Received: by 10.152.102.177 with SMTP id fp17mr13217271lab.0.1359377606582; Mon, 28 Jan 2013 04:53:26 -0800 (PST) Received: by 10.112.2.69 with HTTP; Mon, 28 Jan 2013 04:53:26 -0800 (PST) In-Reply-To: <5106690E.6040908@zerocue.com> References: <76a9565b2a095a72063a68f106a6b457@mail.gmail.com> <5ed6711b24349c82b7c17dd450ff7c80@mail.gmail.com> <7165e8331e1070234771f7ae9573cdf8@mail.gmail.com> <5106690E.6040908@zerocue.com> Date: Mon, 28 Jan 2013 13:53:26 +0100 Message-ID: To: Clint Priest Cc: Zeev Suraski , PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] Voting periods From: pierre.php@gmail.com (Pierre Joye) hi Clint, Zeev, On Mon, Jan 28, 2013 at 1:03 PM, Clint Priest wrote: > > On 1/28/2013 5:19 AM, Zeev Suraski wrote: >> >> 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. > > > Actually, it was not done on purpose but was mimicking what many other RFC > "vote sections" do, I thought it was the way it was supposed to be done, > see: > > https://wiki.php.net/rfc/incompat_ctx > https://wiki.php.net/rfc/array_column > > If you're still worried about this making it in, don't worry. Nikita and I > have given up, to the determinant of the community. This is horribly wrong, totally wrong. Zeev, for one, was one of them asking to have a 2/3 majority for any language related RFC. That's what applies to this RFC, and it is, as of now, accepted. I don't see how the vote is remotely close to a tie. There is something very bad going on right now. I'd to think how to solve that as it is the worst thing that can happen to our project, accepted RFCs being "rejected" because of the pressure. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org