Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84892
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <bc4d2110a723924349c67ccb8d6f8990@mail.gmail.com>
References: <BLU436-SMTP63B4758D2D902644C6BB24E2050@phx.gbl>
	<d29a6faab8dd07ce62f6df153c400b03@mail.gmail.com>
	<CALwr1GnMyQrJno24k+hC5WobE29VsQJqcirBYm5XucjW2dxWQA@mail.gmail.com>
	<6e268626bc6b84a3886f39442c827bb6@mail.gmail.com>
	<CAAyV7nEOpN74zNbc9maU9z-LUcOGN4xyAYi2_EGvv04brezdkQ@mail.gmail.com>
	<bc4d2110a723924349c67ccb8d6f8990@mail.gmail.com>
Date: Sun, 15 Mar 2015 21:05:57 +0100
Message-ID: <CAF+90c-uWP0RKsuHRAx0pPOj9wrysthjgouTc4SECaZgkujJGg@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bfceb40ffb0c905115942c6
Subject: Re: [PHP-DEV] [RFC] [INFO] Basic Scalar Types
From: nikita.ppv@gmail.com (Nikita Popov)

--047d7bfceb40ffb0c905115942c6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Mar 15, 2015 at 8:21 PM, Zeev Suraski <zeev@zend.com> wrote:

> > -----Original Message-----
> > From: Anthony Ferrara [mailto:ircmaxell@gmail.com]
> > Sent: Sunday, March 15, 2015 9:11 PM
> > To: Zeev Suraski
> > Cc: P=C3=A1draic Brady; PHP Internals
> > Subject: Re: [PHP-DEV] [RFC] [INFO] Basic Scalar Types
> >
> > Zeev,
> >
> > On Sun, Mar 15, 2015 at 3:07 PM, Zeev Suraski <zeev@zend.com> wrote:
> > >> -----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 <zeev@zend.com> 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) tak=
e
> > >> > 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 'finis=
h
> > > voting', and as is typically the case when something is unclear, the
> > > most lax interpretation is acceptable.
> >
> > By your own words: http://marc.info/?l=3Dphp-
> > internals&m=3D142451267910615&w=3D2
> >
> > > Following Adam's analysis of the timeline, taking the more 'strict' (=
no
> > > pun
> > intended!) interpretation of the timeline RFC, we still have until
> > tomorrow to
> > start the discussion and still target it for 7.0, no?  Given the
> > importance of
> > this topic, I'd go for the more lax interpretation that allows for vote=
s
> > to
> > begin by March 15, giving us all a bit more time to discuss.
> >
> > **votes to begin by March 15**. That was the interpretation you used a
> > month ago.
>
> Anthony,
>
> I did not read my own words and therefore didn't notice an even more lax
> interpretation was possible.  What you can see is that I always lean
> towards
> the lax interpretation, by my own words.  The fact that this wasn't even
> brought as an option was an oversight, but doesn't change the fact that t=
he
> timeline RFC doesn't mention anything about voting, but about lining up
> RFCs.  Again, I don't pretend to remember what I meant when I wrote it -
> but
> I would say that if I intended for it to be related to voting - whether
> it's
> voting begins or voting ends - I would have likely wrote that explicitly =
in
> the RFC, instead of using the lax 'line up' term.
>

Sorry, but ... even though your original RFC was very unclear about this,
everybody went by the "all votes must start by the 15th" interpretation
that has been discussed in that thread. Do you think it's an accident that
a whopping six RFC votes started today? It isn't.

Please don't start reinterpreting things to fit your needs. I am personally
totally fine with extending the PHP 7 timeline by say one month - but if we
do that, let's make it official and applying to everyone, not just some
particular RFC. I know for sure that there are a number of additional RFCs
that would have been submitted for PHP 7 had anyone known that it'll be
allowed.

Nikita

--047d7bfceb40ffb0c905115942c6--