Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65438 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58315 invoked from network); 29 Jan 2013 21:31:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 21:31:37 -0000 X-Host-Fingerprint: 217.114.211.68 unknown Date: Tue, 29 Jan 2013 16:31:34 -0500 Received: from [217.114.211.68] ([217.114.211.68:22638] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 42/5E-10721-6BF38015 for ; Tue, 29 Jan 2013 16:31:34 -0500 To: internals@lists.php.net References: <76a9565b2a095a72063a68f106a6b457@mail.gmail.com> User-Agent: slrn/0.9.9p1 (SunOS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-Posted-By: 217.114.211.68 Subject: Re: Voting periods From: dsp@php.net (David Soria Parra) On 2013-01-28, Zeev Suraski wrote: > --e89a8fb1fbd85c066a04d455d2d7 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > > The specific case in point is > https://wiki.php.net/rfc/propertygetsetsyntax-v1.2 - which while has more > supporters than opposers, consistent fell short of the 2/3 majority it > needs to be approved. The vote should have ended on Wednesday =E2=80=93 4 = > days > ago, but for some reason it=E2=80=99s still open. It=E2=80=99s time to clo= > se it. I agree. We need a defined period for voting. The past RFCs have seen very short voting periods to very long, depending on what the RFC creator wanted and usually worked in his favor. To make it more objectiv and actually concentrate on code instead of votings I tihnk a 1 week or 2 week period after calling for votes is okay and shouldn't be able to be extended. Concerning the property syntax, I agree that this vote should be closed already. David