Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102788
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.18 as permitted sender)
To: Stanislav Malyshev <smalyshev@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <662b497a-6829-cc55-190e-1e36e0280ef5@gmail.com>
Message-ID: <7b9a8b8e-b472-2a8b-7ac2-a67f8d57805d@gmx.de>
Date: Thu, 12 Jul 2018 16:31:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <662b497a-6829-cc55-190e-1e36e0280ef5@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: Maintainership dates
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 03.07.2018 at 07:53, Stanislav Malyshev wrote:

> Following up the proposal from Sara, I've made a patch to add dates to
> maintainership status in EXTENSIONS:
> https://github.com/php/php-src/pull/3357

Thanks!

> I didn't touch SAPIs because it's not clear what to do with them (to me).

I do not see much of an issue there, so I suggest to postpone any action.

> Please check it out and comment. We have a bunch of extensions where
> official maintainers haven't touched the code for 10+ years, so we need
> to think what to do about it.

In my opinion, these should be treated basically like unmaintained
extensions, i.e. issue a call for maintainership.  It seems to be
appropriate to explicitly CC the listed maintainers, though.

However, I would prefer to issue the calls for maintainership one by
one, or more likely in small chunks, to avoid excessive flooding of the
mailing list.  It also might be sensible to wait until 7.3 feature
freeze, or at least until the traffic on internals@ abates.

-- 
Christoph M. Becker