Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101898 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99819 invoked from network); 21 Feb 2018 11:18:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2018 11:18:48 -0000 Authentication-Results: pb1.pair.com header.from=dzuelke@salesforce.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dzuelke@salesforce.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain salesforce.com designates 209.85.214.48 as permitted sender) X-PHP-List-Original-Sender: dzuelke@salesforce.com X-Host-Fingerprint: 209.85.214.48 mail-it0-f48.google.com Received: from [209.85.214.48] ([209.85.214.48:37634] helo=mail-it0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/4C-22623-7955D8A5 for ; Wed, 21 Feb 2018 06:18:47 -0500 Received: by mail-it0-f48.google.com with SMTP id d10so1878295itj.2 for ; Wed, 21 Feb 2018 03:18:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cwLQKy8XoavhtuPmdMEeE0VAuNbHUI4QV45nU2SHtHc=; b=a2DkvUfj2ahr7HSIh3HgbW1nUdiLCbc08Z1pXZ044YUVGPjqDodefCJFz1MoMpsSth bEMbRchPNQn1qhLMZ/x+UVapgErNgUro1gLyQB9XdhXdRP8myNiKs+71DeIBZCMkfCUJ YmVOJCP+BpTyDyd06doXXAyBYRTVYVH+ACCeI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cwLQKy8XoavhtuPmdMEeE0VAuNbHUI4QV45nU2SHtHc=; b=HjFixp4A6ZEEi2OEF9UDR3R+rgIpMw3IglFCoAK4RscnyrzgP4WAVtk/yfce6C5uZg gSE+IexwzrXbtL0NedBMMmLJud1oc9rAoumI8V3MmKHP+fRxnSfDyJ2t8yjsetMNWcQk ky52gKH/OBqo5hGBq2U3oKhNjIpWdyNDWiU/9+XqTA0U1n527HBzSOnbzwsvb75SFtDQ gyiCqdpIam/45h67IQdYJkIW5O61X92vTC/SEqbyWpxepdRsXKR8rE3atZCFCAfYyHYJ XVped/70U6M+TJoV4ZC7JZn8ojMoxxYEfq9zngOqOXI68qalRiAu3tZPp133bfpKvAdG 9+Dg== X-Gm-Message-State: APf1xPAJXrBfMFEQWbvrbbSdgqJen8t4mJz8C6Lj7XTIhJgzWFoLlvxH WUa1Aw7e9p2iiy6fXGHdrI288Y215sQalr925Q6loQ== X-Google-Smtp-Source: AH8x227t/nxzsoNlVjcLd74sgH3L7btpu1LDf7vxZ20fNxXxTVA8l6pB05Ua7ENz5TCZpQfrqO2MjsEydaNBXxACH0A= X-Received: by 10.36.46.23 with SMTP id i23mr2845511ita.55.1519211924504; Wed, 21 Feb 2018 03:18:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.53.131 with HTTP; Wed, 21 Feb 2018 03:18:43 -0800 (PST) In-Reply-To: References: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com> Date: Wed, 21 Feb 2018 12:18:43 +0100 Message-ID: To: Jakub Zelenka Cc: Stanislav Malyshev , PHP Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] FPM maintainership? From: dzuelke@salesforce.com (David Zuelke) Yeah I was going to say: work with Jakub, he has some good stuff in flight! :) On Wed, Feb 21, 2018 at 11:52 AM, Jakub Zelenka wrote: > Hey > > On Wed, Feb 21, 2018 at 12:42 AM, Stanislav Malyshev > 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