Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95172
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.53 as permitted sender)
To: PHP Internals <internals@lists.php.net>
Message-ID: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
Date: Sun, 14 Aug 2016 22:53:42 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: [RFC] orphan extensions cleanup
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

I'd like to propose an RFC to deal with extensions that currently have
no maintainer:

https://wiki.php.net/rfc/umaintained_extensions

The main goal of the RFC is to initiate the process that by the time of
7.1 release will result in no extensions in PHP core being unmaintained.
The process would be as follows:

1. Issue a call for maintainers (specific details of how, where, etc.
are to be discussed, ideas welcome).
2. Wait for suitable time and hopefully find new maintainers for most or
all extensions. For some stable ones not much commitment is needed
beyond declaring you are willing to be responsible for them, should the
need arise, for others some bugfixing may be in order :)
3. If after suitable time we can not find anybody to care enough for the
extension to be responsible, move the extension from core to PECL.

Please note that the ideal result is 2, not 3, but the goal is still to
have no unmaintained extensions in core.

Please comment and discuss!

Thanks,
-- 
Stas Malyshev
smalyshev@gmail.com