Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95278
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender)
To: Stanislav Malyshev <smalyshev@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
 <351c6035-2428-5296-2429-69145f7da841@gmx.de>
 <db0ff6bd-8f49-1fc8-5f99-d9253e8dd02e@gmail.com>
 <b073742e-e6a5-b8ad-66ce-f2ef66216c95@gmx.de>
 <781c9731-0700-cfb3-f4c7-26396627f698@gmail.com>
Message-ID: <e6fd16f0-6b50-01d0-576b-432f6548fd03@gmx.de>
Date: Thu, 18 Aug 2016 01:13:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <781c9731-0700-cfb3-f4c7-26396627f698@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] orphan extensions cleanup
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi!

On 15.08.2016 at 22:39, Stanislav Malyshev wrote:

>> Maybe it would be better to first check the current status quo of
>> maintainership, and after that taking care of the insufficiently
>> maintained extensions.
> 
> I think we can do both in parallel. I'll try to write the second RFC
> soon (hopefully I'll have time) and we can do the maintainer list
> refersh together with deciding what to do with unmaintaned extensions.

Sounds good to me.  If I can be of assistance, please let me know.

-- 
Christoph M. Becker