Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101897
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.172 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com>
References: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com>
Date: Wed, 21 Feb 2018 10:52:47 +0000
Message-ID: <CAEKnhAGC6DqMxnBDWfhSFX2V82cB=52Q4H8ZSrzWFq6ws56vZA@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005512600565b6ba1d"
Subject: Re: [PHP-DEV] FPM maintainership?
From: bukka@php.net (Jakub Zelenka)

--0000000000005512600565b6ba1d
Content-Type: text/plain; charset="UTF-8"

Hey

On Wed, Feb 21, 2018 at 12:42 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> I'd like to raise the question of FPM SAPI maintainership. Is it still
> maintained? If so, by whom? Jerome Loyet is listed as a maintainer, but
> his last commit has been in 2012, as far as I can see, and I see no
> activity from him on the bug tracker for the last couple of years (maybe
> more). FPM is a pretty important module and widely used, and we have
> over 100 bugs in the bug DB for it, not being addressed. Would anyone
> like to step up for his module? If not, what's the plan for keeping it
> alive and well?
>

I actually work on some parts of FPM and trying to help with some PR's
already. Currently I work on the rewrite of zlog and as part of that I
completely rewrote the test framework which is inconvenient for some
scenarios (especially logging but there are other parts that the current
tests are not good for). All work is currently done on my FPMi project repo
[1] which is meant to be a dev version of FPM and potentially separated
SAPI that can bring the next features sooner to users on the older PHP
versions. I also started working to the tool for better testing some time
ago [2]. It's currently just a simple fastcgi client but plan to resume
work on it and extend it so it can be used for regression testing and
recreating some bugs that are not possible to do in PHP tests.

The zlog part is more or less working but needs optimization (better
buffering) and some final improvements and fixes. That's probably most
wanted feature especially for Docker execution. Then I would like to use
the new testing framework for all tests and look to other issues.

I already work on it and not sure if there is any other dev actively works
on it so I would be happy to step up as a maintainer whatever it means :) I
want however keep working on my plan so the current priority is to sort the
logging out because it is causing many issues.

[1] https://github.com/bukka/fpmi/compare/0.1.0...next
[2] https://github.com/bukka/fpmt

Cheers

Jakub

--0000000000005512600565b6ba1d--