Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81675 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1369 invoked from network); 3 Feb 2015 00:39:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2015 00:39:03 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:32776] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 82/00-01173-3A810D45 for ; Mon, 02 Feb 2015 19:39:00 -0500 Received: by h1123647.serverkompetenz.net (Postfix, from userid 33) id EA21823D6002; Tue, 3 Feb 2015 01:38:56 +0100 (CET) Received: from 87.159.48.115 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Tue, 3 Feb 2015 01:38:56 +0100 Message-ID: <91bfe6c6c4508c7c7695e6267eecbe1a.squirrel@webmail.klapt.com> In-Reply-To: <32916F11-0988-45BD-81B5-6BBFEF2D0D9F@ajf.me> References: <32916F11-0988-45BD-81B5-6BBFEF2D0D9F@ajf.me> Date: Tue, 3 Feb 2015 01:38:56 +0100 To: "Andrea Faulds" Cc: "Dan Ackroyd" , "Anatol Belski" , "internals@lists.php.net" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC][VOTE] Removal of dead or not yet PHP7 ported SAPIs and extensions From: anatol.php@belski.net ("Anatol Belski") Hi Andrea, On Mon, February 2, 2015 23:54, Andrea Faulds wrote: > Hi Danack, > > >> On 2 Feb 2015, at 22:50, Dan Ackroyd wrote: >> >> >> On 2 February 2015 at 19:11, Anatol Belski >> wrote: >> >>> The voting ends on 2015-02-09 at 21:00 CET. >>> >> >> This is a ridiculously short voting period for a major decision. >> Although the minimum voting time for an RFC is one week, that should >> only be used in extremis. > > I wouldn’t say one week is “in extremis” - it’s reasonable for small, > self-contained, BC break-less new features. Although at least 10 days is > usually better. This topic was spoken long before the discussion was started. It's also not that the subjects would be erased from existence, they'll be moved to a separate branch, that's all. Furthermore, they're available for a while in the lower branches (non PHP7 ported, so almost the same state). And anyone interested is free to resurrect something or put into PECL. > > That being said, I agree. This kind of thing shouldn’t be taken lightly, > and this RFC should have a longer voting period. > >> The people affected by this decision are not likely to read PHP >> internals every day or even every week. > > Yeah, I agree here. The fact there’s not been much discussion attests to > that. > > +1 > > We could hold this open far much longer, that's true. However that obviously wouldn't help us to find maintainers for that stuff. On the other hand - it would really bring PHP7 forward getting rid of things where everyone agrees. As not having to do --disable-all all the time is a certain plus. One needs not much time to check that. I'd really suggest to put a "yes" or "no" at this point and have it done. Whereby some "no" from an active developer in this case IMHO would mean not just "no, that should stay in the core", but "yes, i'll help to port and maintain it". However nobody is forced to mean or guarantee that, just that at the end we can end up with some non ported pieces of core. IMHO we should kick out what obviously doesn't fit anymore and move forward, as the PHP7 deadline is quite tight. Regards Anatol