Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84873 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73509 invoked from network); 15 Mar 2015 19:07:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2015 19:07:13 -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 209.85.212.177 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.212.177 mail-wi0-f177.google.com Received: from [209.85.212.177] ([209.85.212.177:33637] helo=mail-wi0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/8A-29489-068D5055 for ; Sun, 15 Mar 2015 14:07:13 -0500 Received: by wixw10 with SMTP id w10so19083686wix.0 for ; Sun, 15 Mar 2015 12:07:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Ita5RAc6w/Cy/4DFvIGEm3cM1Aig/tfL22VSPvlufgk=; b=ScEUrCTBX5pukwQ5qSly+p5nTiajEgao3juXIOK0TsDTPnj8ZlOnMxemkoT/vmWprc dOAvLTLY8yNTVnzqERU/bH8t8ZUdhgs38n4QrRSllKrlWDIuCcSIeH/IC7vKqO5f7EB4 3Q0fgKtlY7QdzX01ELdehQBJ2f22xc+aqSXHfObNrtmNCmr19o5+EmTvNpqQN3BdRU3e nFwIfT7DyMA1QpM/UYR8cr5nk0iUF7fprsxFP2SloaRUfxcFKkRC8Oi//tbzEqnwtjyK VOnPqzOrx6xemrXpqBWivHn2pNXwU0HhWbnzSApMVZmag9aSHcDVxgdFcAN3HV2//Y1y DObg== X-Gm-Message-State: ALoCoQkIZjap6EHAyC4D9CSKfB7kLMWeYeqraTYBoR+UiLu/nXwTK9YegpGurRjKiDGx3+f5kb7LvnA0iSa/oxI8RwccRpTAE9e+NPw12nlbEZtQWTtbvuGkJqfluFrjarfZxfI0cPPQWaaXekO+4ClPgnRs9gy1Vw== X-Received: by 10.180.207.200 with SMTP id ly8mr31875315wic.58.1426446429592; Sun, 15 Mar 2015 12:07:09 -0700 (PDT) References: In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKV59C6R/g00R7Uu5aQCj/uhXIapAFVjcT/AZ4zTjObezdYEA== Date: Sun, 15 Mar 2015 21:07:08 +0200 Message-ID: <6e268626bc6b84a3886f39442c827bb6@mail.gmail.com> To: =?UTF-8?Q?P=C3=A1draic_Brady?= Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: RE: [PHP-DEV] [RFC] [INFO] Basic Scalar Types From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: P=C3=A1draic Brady [mailto:padraic.brady@gmail.com] > Sent: Sunday, March 15, 2015 9:00 PM > To: Zeev Suraski > Cc: Bob Weinand; PHP Internals > Subject: Re: [PHP-DEV] [RFC] [INFO] Basic Scalar Types > > On 15 March 2015 at 16:55, Zeev Suraski wrote: > > Bob, > > > > Thanks for the update. This time, though, although I completely > > respect your decision not to put your RFC into a vote unless the Dual > > STH mode fails, I'd like to either (with your permission) take over > > the RFC or propose my own copy and move it to voting as soon as > > allowed. This, under a commitment that if I see that Basic STH is > > failing to garner a clear majority, I'll retract it and move to > > support the Dual STH RFC instead for the sake of unity. > > No one individual has the right to break the existing rules around voting= . > There has been more than sufficient time to date to rewrite the voting > rules, > debate voting rights, extend PHP7's deadline, or propose the basic RFC so > described. A vote in contravention of the voting rules at the last > possible > minute cannot, by definition, be recognised at this time. I wouldn't even > vote > since it might lend it an air of ill deserved legitimacy, forgetting for = a > moment whether a few PEAR contributions make me any more deserving of > a vote than others. No rule is being broken. The PHP 7 timeline RFC (wiki.php.net/rfc/php7timeline) states the following= : Line up any remaining RFCs that target PHP 7.0. | Now - Mar 15 (4+ additional months) As Bob pointed out, what 'Line up' means - whether it means vote ends, vote begins, or discussion begins - is completely open to interpretation. I don't remember what I meant when I wrote it, but arguably, 'line up' is a lot closer to 'start discussing' than 'finish voting', and as is typically the case when something is unclear, the most lax interpretation is acceptable. Zeev