Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60495 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2303 invoked from network); 6 May 2012 15:23:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 May 2012 15:23:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitri200@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitri200@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender) X-PHP-List-Original-Sender: dmitri200@gmail.com X-Host-Fingerprint: 209.85.214.170 mail-ob0-f170.google.com Received: from [209.85.214.170] ([209.85.214.170:49291] helo=mail-ob0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/43-17543-75796AF4 for ; Sun, 06 May 2012 11:23:03 -0400 Received: by obbuo13 with SMTP id uo13so7479347obb.29 for ; Sun, 06 May 2012 08:23:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UpgH0z9DgXP5YtIjwRh+uiUGnjyrOtYQFT9j5Kfjx6E=; b=RuQ34n1tg6/tRmQX28VNlhmPVbLFfY8nWUP58PPWwRY4Bvdj8DEak7TrthPkTJa8y/ 43l7CbC4Gh0NRLPxxsKgYTMy45dGvpRic6ssUx6kvW5P/iWJAUnyhHQ2eEK7PiwGXT6C myVAiLJJOv3kbM1/sYCC1UFOjvblNe9evKPN+acYdNWO548FJTXrgl9u92YnKIlBFGUo J2rD6VSvQAy6YM71vpMhO0IuoKu5NCQpwK1fks3fkCKp+y+HMs9GMpscTmkGPuuASRjz +A8kgutXk4H1koTbMZLUhXYNXfvW04Xc2s2PfVBSXooPRYSf4xWx5NQdClPLBir61/Zr dGgQ== MIME-Version: 1.0 Received: by 10.182.72.38 with SMTP id a6mr18038022obv.38.1336317780374; Sun, 06 May 2012 08:23:00 -0700 (PDT) Received: by 10.76.151.69 with HTTP; Sun, 6 May 2012 08:23:00 -0700 (PDT) In-Reply-To: <4FA68CCE.6050001@lerdorf.com> References: <4FA68CCE.6050001@lerdorf.com> Date: Sun, 6 May 2012 11:23:00 -0400 Message-ID: To: Rasmus Lerdorf Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] Are feature request bugs ever looked at? From: dmitri200@gmail.com (Dmitri Dmitrison) On Sun, May 6, 2012 at 10:38 AM, Rasmus Lerdorf wrote: > > We don't have the resources to go through and thoroughly evaluate each > feature request. A couple of developers will read each one and if it > resonates with them personally they will do something about it. > Otherwise they leave it for another developer to address later. > > Some numbers. We have had 2899 feature requests submitted. Out of these, > 605 are still open. 1134 have been implemented. 705 rejected because > they weren't valid features. 322 rejected as "Won't fix" for various > reasons. The rest are in various other states such as Duplicate, and > awaiting feedback. So feature requests do get processed eventually. > > -Rasmus That is actually a promising statistic. However, is there a predictable process for picking some requests over others? If it's based on whether it resonated with the PHP dev who happened to look at it, why even have a voting feature (and suggest that it somehow affects the bug's priority)? I understand this is a free software project, and that resources are limited. And that you can't force contributors to work on features they don't personally like. But I would have expected the bugs with hundreds of votes and/or comments to be inspected first... Or at least after 10 years... Am I being unreasonable? On Sun, May 6, 2012 at 11:07 AM, Ferenc Kovacs wrote: > Just a quick reply from my phone: > anybody can register a wiki account and anybody can get rfc karma after > sending a mail to the php-webmaster mailing list (this is a basic spam > protection). > about the rfc vs bug tracker: the wiki and the rfc process came later than > the bugtracker. > I would open a feature request ticket if I don't know how to proceed further > or I don't have the time to create and push an RFC. Otherwise I would go > with an rfc: albeit it requires more work from the reporter but makes up for > it because it provides much bigger visibility and guranteed response from > the developers. Thank you, that makes more sense to me.