Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94562
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.181 as permitted sender)
To: Derick Rethans <derick@php.net>
References: <5bad172a-4570-78f8-814e-987299241a2b@gmail.com>
 <alpine.DEB.2.20.1607181227360.16349@whisky.home.derickrethans.nl>
Cc: PHP Internals <internals@lists.php.net>
Message-ID: <d3267472-9961-e4b1-cf9c-c8ccae6adf4c@gmail.com>
Date: Mon, 18 Jul 2016 12:44:20 -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
In-Reply-To: <alpine.DEB.2.20.1607181227360.16349@whisky.home.derickrethans.nl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] orphaned extensions in 7.1?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Don't presume that "no updates" does not mean "not in use", or "not 
> maintained" though. 

True. I am not concerned about having many updates though but rather
having somebody who would make updates if needed. For those two, we
officially don't have anybody. I suspect there is a number of extensions
which unofficially are in the same positions, due to nobody listed as
maintainers, or people listed as maintainers having moved on since and
not really interested in being maintainers, or just us having no idea
about whether somebody is maintaining or not.

We have 20 extensions listed as "Unknown" and among those listed as
maintained, also some that nobody officially listed as maintainer has
touched the bugs filed for the extension for many years.

This is not to imply somebody's fault or make a judgement on the quality
of code or importance of the extensions. It is a natural process that
maintainers change. But I think we should realistically evaluate what is
really maintained and what is not, identify where we have gaps and
either solicit help to close these gaps or admit that we don't have the
resource to maintain it right now.

-- 
Stas Malyshev
smalyshev@gmail.com