Everything

php

Maintainership dates

php.internals

Stas Malyshev

8 years ago

Hi!

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

I didn't touch SAPIs because it's not clear what to do with them (to me).

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.

Thanks,

--
Stas Malyshev
smalyshev@gmail.com

Christoph Becker

8 years ago

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

Stas Malyshev

8 years ago

Hi!

> 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.

Sounds good. Anybody wants to help with writing the text for the call
(it should include some explanations about what it is about and what the
person is to do) and on which venues it should be announced?

--
Stas Malyshev
smalyshev@gmail.com

Christoph Becker

7 years ago

On 12.07.2018 at 21:14, Stanislav Malyshev wrote:

> Sounds good. Anybody wants to help with writing the text for the call
> (it should include some explanations about what it is about and what the
> person is to do) […]

Okay, a first draft for the call for maintainership:

| The <extname> extension which is bundled with PHP is looking for a new
| maintainer, since the former maintainers are inactive for <year-count>
| years now, and although the PHP core developers keep the extension
| alive, there are unresolved bugs and other issues which should be
| adressed.
|
| Requirements:
|
|  * working knowledge of the C programming language
|  * working knowledge of the APIs of the underlying libraries
|  * working knowledge of PHP extension programming
|  * working knowledge of the Linux or Windows build system
|  * some time to actually maintain the extension
|
| Benefits:
|
|  * working on widely used Open Source software
|
| If you are interested, please let us know!  If you already have a
| php.net account, fine!  Otherwise please consider to submit one or
| three pull requests regarding bug fixes and/or other improvements of
| the <extname> extension.
|
| If no maintainer successfully applies within the next <week-count>
| weeks, the <extname> extension is likely to be unbundled and moved to
| PECL.

> […] and on which venues it should be announced?

I think this mailing list and <https://twitter.com/official_php> should
be good – the community will likely spread the word.

--
Christoph M. Becker