Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95182
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
Date: Mon, 15 Aug 2016 12:41:04 +0200
Message-ID: <CAF+90c8Qjze6ttRj1F0ZsX=aFfheuHZnLr7t0Y0D-SH79xS6jg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c07e31e7dfbac053a19de41
Subject: Re: [PHP-DEV] [RFC] orphan extensions cleanup
From: nikita.ppv@gmail.com (Nikita Popov)

--94eb2c07e31e7dfbac053a19de41
Content-Type: text/plain; charset=UTF-8

On Mon, Aug 15, 2016 at 7:53 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> 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!
>

Is the a list of extension maintainers somewhere?

As others have mentioned, tokenizer is effectively core-maintained, but if
you need an explicit maintainer, you can put me in.

I think the interbase extension is missing from this list, I don't think it
has an active maintainer.

Nikita

--94eb2c07e31e7dfbac053a19de41--