Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105523 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 99871 invoked from network); 30 Apr 2019 21:23:35 -0000 Received: from unknown (HELO tbjjbihbhebb.turbo-smtp.net) (199.187.174.11) by pb1.pair.com with SMTP; 30 Apr 2019 21:23:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=php.net; s=turbo-smtp; x=1557253548; h=DomainKey-Signature:Received: Received:MIME-Version:References:In-Reply-To:From:Date: Message-ID:Subject:To:Cc:Content-Type; bh=qtyndCbjY94SjiWhZUlsMC 2OW/ME7eoq62bWcumnHws=; b=g6cRpk5RDwFB+mtVIaddkAGCwbTDVCk5/5+DqS g3DkvPwAvDQQvEwm4ia8gAlBbLMGgTb+cot3Zav85JWL7bbav8HWRf0ljcRpvjr4 xQDSLdrgaZeMBkR9kl5TvemCozMqqwnLSI0A7N9ar+53PExPWxrc8YXW4UcLVezS ppKv8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=turbo-smtp; d=php.net; h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type; b=kQp+6z83/wN9FnSAx//xeRlBhysCtwVxZefic5SetJQR97y8tA5f5KodbXNYPH 8KqrXjhqA5ypkG3CQQwr9Jf14cQssiObzN7y/k7dHLvS4ySEUd8Qr8NJA0TLegMz KXqF6cKpr7glo4ebgBOmmInpLDtzWkw8dOadzGIe86FeA=; Received: (qmail 521 invoked from network); 30 Apr 2019 18:25:47 -0000 Received: X-TurboSMTP-Tracking: 5002781603 X-Gm-Message-State: APjAAAUNKaRajqQ30INXp1litcrHY1S6TxnYCDUqionkrWxFe/XfPFDl y4Sv+8c/HdNlBn+TAs6nqDS/yleP7vHNVeZQX/w= X-Google-Smtp-Source: APXvYqy27SOKegYxdw/HpUEDyGGN5K2M0MA5TuFkJMpS1YWs7j092c16QM0RUmSUjdDveHDrJt2JgO+W8lmzQ1oGaSg= X-Received: by 2002:ad4:430d:: with SMTP id c13mr9645428qvs.169.1556648747379; Tue, 30 Apr 2019 11:25:47 -0700 (PDT) MIME-Version: 1.0 References: <49A4B76C-4C62-4CBE-BA20-FBE56CA29AB0@cschneid.com> <609E93CF-099B-446C-AD28-04F1D802C9F0@cschneid.com> <000401d4fac8$ae592cf0$0b0b86d0$@roze.lv> In-Reply-To: Date: Tue, 30 Apr 2019 21:25:35 +0300 X-Gmail-Original-Message-Id: Message-ID: To: Derick Rethans Cc: "G. P. B." , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000a0af900587c387a7" Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags From: zeev@php.net (Zeev Suraski) --000000000000a0af900587c387a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 30, 2019 at 8:14 PM Derick Rethans wrote: > On Mon, 29 Apr 2019, Zeev Suraski wrote: > > > On Sun, Apr 28, 2019 at 11:32 PM G. P. B. > wrote: > > > > > I think this just boils down to what is an acceptable majority, if > > > 2/3 is not enough then 3/4 but this is another debate altogether. > > > > > > > I've argued in the past that it would make sense to require a 9/10 > majority > > for RFCs. Very few RFCs that passed - only cleared a 2/3 majority. > > Usually (in the vast majority of cases), it either clears a nearly > > unanimous vote - or it doesn't even come close to 2/3. > > > > RFCs that have a high number of votes (i.e., that people feel strongly > > about), and barely pass the 2/3 mark - are controversial and saw > division. > > Yes, it means that out of the (almost random) group of people who are > > currently enabled to vote by our (flawed) voting system > > If you think it's flawed It's not that I think it's flawed - I know it's flawed. It doesn't implement what was agreed upon when the Voting RFC was enacted. > , you know that the RFC process is there for > anybody to change it. Joe already managed twice towards what you > suggested in your stalled RFC: > > - https://wiki.php.net/rfc/abolish-short-votes > - https://wiki.php.net/rfc/abolish-narrow-margins (btw, you voted > against this one to raise the barrier from 50%+1 to =E2=85=94rds). > I'm well aware of it. In doing that, I think we greatly complicated the prospects of fixing the voting eligibility - which is an infinitely hotter potato to handle. Both 'abolish' RFCs enjoyed popular support and had very little touchy subjects - unlike the topic of who gets to vote, or the prospect of moving to a consensus-based system. > It's absolutely fine to dislike short tags. It's absolutely fine to > > believe it shouldn't have been introduced. But the gap between that, > > and thinking it's fine to remove it - is very, very big. > > But the fact is that the RFC passed. And retroactively changing rules > because somebody don't agree with a decision is making a farce out of > the process. > I've detailed the issues with the RFC in my other reply. I'm well aware that I'm spending quite a bit of 'credit capital' by weighing in on this, and I'm enjoying it roughly as one would enjoy having their tooth pulled out without anesthesia (which still pales in comparison to what it would take to fix our voting process, which will probably be akin to having an entire set of teeth pull out in the same way). The reason I'm still doing it is that it's clear this RFC was flawed in its voting options, its substance, and the level of discussion that surrounded it (the last one is my opinion, the first two are facts) - and it will have HUGE implications on hundreds of thousands if not millions of users. So as I said when I first engaged this thread - as much as I'm 'enjoying' this, I prefer to take the personal hit and do whatever I can to prevent our users from taking the hit. If we are to inflict this hit on our users - we need to have each and every t crossed and i dotted. Zeev --000000000000a0af900587c387a7--