Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91111
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.161.179 cause and error)
MIME-Version: 1.0
Date: Mon, 8 Feb 2016 14:13:29 +0000
Message-ID: <CA+kxMuTnxPj0dk+YupOz9ij+qZiEON=D=mLx73m=c7s8nWA3Bg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Add 'Requires RFC' to bugs.php.net was [PHP-DEV] Close some old issues
From: danack@basereality.com (Dan Ackroyd)

On 30 January 2016 at 07:19, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>
> As far as I can see, the only way to do it is to edit local database, so
> somebody with shell access and DB password is needed.

What is the process for adding new status to those available at
bugs.php.net ? Does anyone know who has access to the box, and are
they allowed to add a new status by themselves, or do they need to get
'approval'?

Just to reiterate, adding a 'Requires RFC' would be useful to help
clear the backlog of feature request issues that have been open for
years, and are just not going to be done, unless someone proposes an
RFC for it.

But it would have more use going forward. It allows issues that are
feature requests to be moved out of the 'Open' state quickly, so
people looking for actual bugs won't be shown issues which would
require an RFC.

Just as an example, there is a feature request to "add ini setting
that will toggle between old and new behavior, giving developer an
option to choose between better debugging capabilities and better
performance" - https://bugs.php.net/bug.php?id=71543

This seems quite unlikely to happen....not only are there very few
people who could implement this change, they are very unlikely to want
to do it, and all RFCs introducing new ini settings seem to receive a
poor response.

Having that issue sit open, means that all of the lovely people who
look to fix bugs will be wasting time reading that issue. While the
issue is open, the reporter also has the incorrect expectation that
someone might be looking to do that issue "any day now" when
realistically, it's not likely to happen.

So who/how should I be chasing, to get that done?

cheers
Dan