Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30814 invoked from network); 28 Jan 2015 20:06:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2015 20:06:54 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wg0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:34692] helo=mail-wg0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/9C-44076-B5149C45 for ; Wed, 28 Jan 2015 15:06:52 -0500 Received: by mail-wg0-f50.google.com with SMTP id b13so22555409wgh.9 for ; Wed, 28 Jan 2015 12:06:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=wknFCmCEtGkZG0QAiRVdxhSEp4voTb8e1YuaA6sco1E=; b=uwwBB4sEXsAFSllradwiCLrZt071+8YcNY9TTuSdTg6tEkSrB2eCS+rpizbfyL1QO5 o5nT4NpsT0m2Iq19Yvw8aqUdFe1bVg0empZX3D651k4OV4w9WZJs54uw2UGXu7hoX9iV 9Z28V2OJ8wUhhyAI1+7ZhSL/8d3O8M7Ry8bGNCPEGsu419/Hv3eJuN726I224L7fW/nX IK/122Hkaepwt2Vne4JYkeIqjSM6AUhjC663sQ73uwgKIhAo9NhKuzdi0dDPX+83D4iY u35STy2gjU1Zi27By+PT//w9fkx4rKZlE+wgzU6OcThhNcc0GzISDyoalPpqLG/MFa0w mDLA== X-Received: by 10.194.219.68 with SMTP id pm4mr11136038wjc.71.1422475608417; Wed, 28 Jan 2015 12:06:48 -0800 (PST) Received: from [192.168.2.120] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by mx.google.com with ESMTPSA id da2sm7488109wjb.21.2015.01.28.12.06.47 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jan 2015 12:06:47 -0800 (PST) Sender: Michael Wallner Message-ID: <54C94156.9050200@php.net> Date: Wed, 28 Jan 2015 21:06:46 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Levi Morrison CC: PHP Internals References: <54C8D36E.7010803@php.net> <54C92683.6020305@php.net> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [VOTE] pecl_http From: mike@php.net (Michael Wallner) On 28/01/15 21:03, Levi Morrison wrote: > On Wed, Jan 28, 2015 at 11:12 AM, Michael Wallner > wrote: > > On 28/01/15 18:58, Levi Morrison wrote: > > On Wed, Jan 28, 2015 at 10:53 AM, Levi Morrison > > >> wrote: > > > > Discussion has been very low on this topic since it was > proposed on > > August 19th, so I just opened the vote on the RFC whether > to add > > pecl_http to the core. The vote will be open until about 12:00 > > UTC on > > Friday, February 6th. > > > > https://wiki.php.net/rfc/pecl_http#vote > > > > > > I wish you had pinged the list before opening the vote. I know > there > > were a few people who wanted to make comments but have just been > > very busy. For example, I have been dealing with the return types > > RFC which has soaked up all of the time I have for working on PHP > > projects. > > > > Some feedback: I feel the RFC is not clear about the > advantages and > > disadvantages of including this package. Mostly, the RFC is "hey I > > have this package can we include it in core?" I feel like it's > > fairly incomplete as to *why* we should include it. There is a > fair > > amount of work done in user-land for these types of utilities, > and I > > think without a more balanced discussion we'd be giving this > > extension a distinct advantage. > > > > If we allow it to remain in voting phase despite these issues, I > > have to vote no simply because I don't feel like there is enough > > information presented in the RFC for anyone except current > pecl_http > > users to make a good decision; that's hardly a good situation for > > the language as a whole. > > > > > > Oh, one more item: has anyone had time to review the pieces and > how they > > all interact, as well as reviewing the quality of each component? I > > should hardly think in the time given this has been done. I'm not > saying > > this extension is bad; I am saying that I don't think there's been > time > > for anyone to properly evaluate whether it is or not. > > Well, there's been hardly any activity on the RFC for over five months, > if one didn't have the chance for review in this time frame then the > topic is probably not interesting enough for her. > > But I already guessed, that there wouldn't be a real discussion until I > slapped the label VOTE on this RFC. > > > I always send an email to the list before putting something to vote to > gather more feedback. It usually solicits one or two more points of > discussion. This is not technically a requirement, but if it has has no > activity for 5 months what are the chances that it is on my mind? (Hint: > exactly zero) > > As an RFC author if you want people to think about your RFC and discuss > it then on occasion you need to bring it up now and again. Yep, I re-started discussion on January 22nd. Gathered the same participants than the first discussion round. -- Regards, Mike