Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52963 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62503 invoked from network); 5 Jun 2011 20:05:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2011 20:05:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.199.177.89 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 212.199.177.89 il-mr1.zend.com Received: from [212.199.177.89] ([212.199.177.89:48677] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/0D-26000-D81EBED4 for ; Sun, 05 Jun 2011 16:05:34 -0400 Received: from il-gw1.zend.com (unknown [10.1.1.22]) by il-mr1.zend.com (Postfix) with ESMTP id 8FE6A606DB; Sun, 5 Jun 2011 23:04:28 +0300 (IDT) Received: from IL-EX2.zend.net ([fe80::60b2:93c9:cabf:4659]) by il-ex2.zend.net ([fe80::60b2:93c9:cabf:4659%15]) with mapi id 14.01.0255.000; Sun, 5 Jun 2011 23:05:13 +0300 To: Pierre Joye CC: Philip Olson , Stas Malyshev , Derick Rethans , PHP Internals Thread-Topic: Voting Process (was: [PHP-DEV] Re: Voting does not belong on the wiki! (Was: [PHP-DEV] 5.4 moving forward)) Thread-Index: Acwju4mMVI/geX/lRt2X0REy1lGzyw== Date: Sun, 5 Jun 2011 20:05:12 +0000 Message-ID: <887FE7CFF6F8DE4BB3A9535F53AFD06A4930609E@il-ex2.zend.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.199.177.84] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: Voting Process (was: [PHP-DEV] Re: Voting does not belong on the wiki! (Was: [PHP-DEV] 5.4 moving forward)) From: zeev@zend.com (Zeev Suraski) Pierre, I'm happy that we agree pretty much completely about the clarifications & u= pdates needed for the RFC. I do however want to point out that the problematic way the short array syn= tax RFC was executed was the key reason that made me feel these updates wer= e in fact necessary - I don't think that the way it was done was exemplary = in any way... Pretty much each and every point in my email is based on things that I felt= went wrong with how we handled the short array syntax RFC: - There wasn't sufficient time, or nearly any time at all - between when Br= ian pulled it off the attic, and when a vote was called. If my proposal is= accepted, there'll have to be at least two weeks between when a clearly ma= rked [RFC] email hits internals@, and when a vote is called. - There wasn't a clearly marked, separate [VOTE] email. - There wasn't a clear or easy way of voting. - No voting period was announced, instead, people were told to stop mess ar= ound and go vote. - The author of the RFC wasn't actively involved in the whole process (as f= ar as I could tell); There was no official replacement proposer. I just want to make sure we're on the same page. If you feel that the arra= y syntax RFC was 'done right' then we have a bit of a gap :) In my opinion= , given the lacking process, the short array syntax RFC needs to be redone. I'd still like to hear from others what they think about my proposal. I'd = like to update the Release Process RFC with these suggestions if people lik= e them. Zeev