Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95219
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
Sender: kalle.php@gmail.com
In-Reply-To: <CADxrgCO=vG_KGjoH5yH4reEfE61xhn-j5a93EbARsc183nAbpg@mail.gmail.com>
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
 <CAJW__o29+y02aWjzHqLEdXJG9-=GtgiexU8v_hctTP=gqtQGgg@mail.gmail.com> <CADxrgCO=vG_KGjoH5yH4reEfE61xhn-j5a93EbARsc183nAbpg@mail.gmail.com>
Date: Tue, 16 Aug 2016 00:20:09 +0200
Message-ID: <CAJW__o13wN2HQAyGTrTF8sRdQzurAaxipWPv9ODLargf2JEnUQ@mail.gmail.com>
To: Adam Baratz <adam.baratz@gmail.com>, Anatoliy Belsky <ab@php.net>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, Pierre Joye <pierre.php@gmail.com>, 
	Christopher Jones <sixd@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] orphan extensions cleanup
From: kalle@php.net (Kalle Sommer Nielsen)

Hi Adam

2016-08-15 23:34 GMT+02:00 Adam Baratz <adam.baratz@gmail.com>:
> As one of those two people, it would help to have an official maintainer for
> this extension. The path for "something's broken" or "something should be
> different" to "committed fix" has been pretty murky.

First of all, great job on the recent pdo_dblib activity, its great to
see someone is actively interested in keeping this alive.

> I'm interested in putting my name forward for this. It would help to know
> more about what's expected. In particular, when PRs poke at broader design
> questions with the extension, what's the maintainer's role? One example:
> https://github.com/php/php-src/pull/2017

As for expectations, I think its generally expected that the
maintainer oversees bugs, and future development of the extension. An
example could be that a security issue is present in the extension and
having someone that understands the code able to review, fix and work
on it is good, instead of (like Stas mentioned), having someone look
into the code without fully understanding it, and potentially breaking
something else (kinda like what happened to ext/exif).

As a maintainer, you are pretty much the one that oversees the
extension, making sure its in working condition (to continue being in
the core), having tests passes, bug reports and PRs. Ofcourse other
core developers may from time to time touch the extension to fix
something, and in that case make sure to double check that there is no
obvious regressions (we all do make mistakes!).

From seeing your past commitment to pdo_dblib, I'm a +1 keeping this
extension with you as a maintainer, and I'm sure Anatol (cced) who
seems to also be active in some of the PRs say yes to that too.


-- 
regards,

Kalle Sommer Nielsen
kalle@php.net