Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103954
MIME-Version: 1.0
References: <ea4db034-e866-79b7-ed1d-1bef5b2578bf@gmail.com>
 <CAEYWF=60iJucVP=HB+h1T0f94LA7OJyboRzMO-ok-Kv6N+OWRw@mail.gmail.com> <dbcf81f2-d010-eece-e477-81e8e23643c3@gmail.com>
In-Reply-To: <dbcf81f2-d010-eece-e477-81e8e23643c3@gmail.com>
Reply-To: bishop@php.net
Date: Thu, 31 Jan 2019 15:45:49 -0500
Message-ID: <CAEYWF=6g9LVM_skbwggE_gJOvtrP-8Csf4ryMa5pMLZFAJn68g@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001d59b40580c71e46"
Subject: Re: [PHP-DEV] PHAR maintainer?
From: bishop@php.net (Bishop Bettini)

--0000000000001d59b40580c71e46
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 31, 2019 at 3:13 PM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > I've been fixing phar bugs here and there over the last year, and I'm
> > happy to take on a more diligent process to maintain ext/phar officially.
> >
> > Do we have, anywhere, a maintainers guide that talks about the
> > maintainers' responsibilities?
>
> First of all, thanks for volunteering!

There's no real formal guide, but basically maintainer should monitor
> the tickets filed against the extensions and provide fixes for them.

There seems to be a bunch of open ones:
>
> https://bugs.php.net/search.php?search_for=&boolean=0&limit=30&order_by=&direction=DESC&cmd=display&status=Open&bug_type=All&project=All&package_name%5B%5D=PHAR+related
>
> so making a pass over them, seeing which ones still exist and confirming
> them, closing those that don't happen anymore and starting fixing those
> that still happen would be a good start. If you need somebody to review,
> I'd be glad to help with whatever I can.
>

Excellent, that's exactly what I had started to do, before pausing to
welcome my son into the world. Being back at it, I've set a goal to triage
one bug a week, which positions us to be potentially phar bug free in about
a year. (Assuming the ingress rate of about 6/year remains stable.)

Some I've triaged quite a while ago, and I felt a more comprehensive
refactor would be appropriate. I'll leave those alone until I have more
total experience with the code and focus my first efforts on the low
hanging fruit.

Do I need to request any special git access or just keep doing the usual PR
process?

bishop

--0000000000001d59b40580c71e46--