Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101894 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89880 invoked from network); 21 Feb 2018 09:23:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2018 09:23:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.196 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.128.196 mail-wr0-f196.google.com Received: from [209.85.128.196] ([209.85.128.196:42412] helo=mail-wr0-f196.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/BA-22623-38A3D8A5 for ; Wed, 21 Feb 2018 04:23:16 -0500 Received: by mail-wr0-f196.google.com with SMTP id k9so2398363wre.9 for ; Wed, 21 Feb 2018 01:23:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=G2Ar5vSwMTTlrfbbp2aq8Nqr97jzT4uc2I0Dgvnsdaw=; b=SdKAOsYTrW0F21+lSr1ErFNl191JgZWTtIm3REINSxFK/Om497F0AfRmTY4vn7/46M xvFdwicxOib8VME9/EnC0IIWO5mjKLQfraOIIN392LRfU4QTVrFeQzCPh7zMKkVwdkKW WNiMxOSUou7mB0pPB79bTr9C6KXIQt0pax/mrE8kXnBIk+owA88Zmp2o0dkI8WoM9EPQ 0ulPqhSdtWqpV/QF1kgYHl1qyVMXahQBmvEhuPzp15K6VGg9ZAAIHp7Qlb3G5gxItL/I eiaxvPVP58Dm313faHJe9soZ2Or7SVJQtMG9jJuQ+M1gg0DJ9QYB4p08mWGMK2S8T8Wo Kb4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=G2Ar5vSwMTTlrfbbp2aq8Nqr97jzT4uc2I0Dgvnsdaw=; b=X01lxumW7Xnikm/te8M/SR41UdA0M8Mlv8qvT5pK29zQQw9ZaDvXME4v7ZzwKkUg5L +5mJWvtf63ua9+D2kAZJeArTfW7e28BFLXDhxNjTDpjfWT1Og7QUnHeBSlja7ytI3J5M OQjGkzHJbe26I2fyh8OyEt07i+oRHIKqwstqnA9V9lNPH1/Kbxv3vSfxqzhFFYdYn+RC hthhMZHUlmmyetOMGlj8M+aNsqwHn8Ms6XtYm29+F+uHgoOc0J94GfU4loc7E+hlAIB8 f6TzPFsFl/Ex8MsdjeyuA+JO/d1jVIRad3SyTKPPIlQEn+BhtIs9HmrBOMZTFT/KpQdw DL1Q== X-Gm-Message-State: APf1xPDRr5XL2Ih3YcA5fKhLBo5fJ8w1bk4xSEfS8wCkh4LCmYezpeN9 jJAM+Rakc41hxLhDCsAzXhoZoKOS X-Google-Smtp-Source: AH8x225CWvjwUXqsg27g0HPUAh0zZQBaL0ZSg/e3onjdbDk8M1hDtS5Dc/vy1Ou/YBEbsP2sSIvUEQ== X-Received: by 10.80.143.38 with SMTP id 35mr3896540edy.183.1519204992302; Wed, 21 Feb 2018 01:23:12 -0800 (PST) Received: from [192.168.2.11] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by smtp.googlemail.com with ESMTPSA id p14sm23457187edj.46.2018.02.21.01.23.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Feb 2018 01:23:11 -0800 (PST) Sender: Michael Wallner To: internals@lists.php.net References: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com> Message-ID: Date: Wed, 21 Feb 2018 10:21:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8dFZT2TNVKous59qO42vfqdQoQUEymoOl" Subject: Re: [PHP-DEV] FPM maintainership? From: mike@php.net (Michael Wallner) --8dFZT2TNVKous59qO42vfqdQoQUEymoOl Content-Type: multipart/mixed; boundary="6cJ5s5yCuX75jrVYINUlH34NxzxGqJHpR"; protected-headers="v1" From: Michael Wallner To: internals@lists.php.net Message-ID: Subject: Re: [PHP-DEV] FPM maintainership? References: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com> In-Reply-To: <861e4190-1cb8-eeb6-740a-45485192034a@gmail.com> --6cJ5s5yCuX75jrVYINUlH34NxzxGqJHpR Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 21/02/18 01:42, Stanislav Malyshev wrote: > Hi! >=20 > 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 (mayb= e > 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'd like to second that. Given the past development of heading away from SAPIs loaded into the webserver to FastCGI being preferred, we should be giving FPM the deserved priority. Does anyone have stats about the popularity of our SAPIs? I also have a patch I'd like to discuss with the new maintainers, which attempts to fix FPM's SIGUSR2 graceful restart behaviour, and which we've been running for half a year now IIRC. --=20 Regards, Mike --6cJ5s5yCuX75jrVYINUlH34NxzxGqJHpR-- --8dFZT2TNVKous59qO42vfqdQoQUEymoOl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEHsPHHd1jWDGjN9aESA4+FLCkx8cFAlqNOh0ACgkQSA4+FLCk x8e3GAgA1X448Li0UR7u4n5CypL+sAkJo+/hVFpUxKEvo1p3sKvmcgOTrZ4ReBbv F9brNZb+DM1iMs+KHEx/eDqGFnGcTdp4dCd7jqNgFL5Usfn9TZIn7pnC2ebsmPlX xZciKX3/U25N7jrC6YCTlEv7HESp1iT5W5tX5XLpfB/ceabhyiqk6DN5kz1g+Ssx y2KEjLzJVhHKQgIW+82MYEVjKjMrCp2CK23rVt0OY3yr5b0bY+vZcKOKfJin2kVs aNbhU87rZtBFyA4hH6cdFk9bCUXscXcGhDqDVbwYHHWx8xVfPWtchCW7HefACF64 Pv3E09MddAx4Xj4eGH+yCZIkAU0kNA== =hjsE -----END PGP SIGNATURE----- --8dFZT2TNVKous59qO42vfqdQoQUEymoOl--