Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102234 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39853 invoked from network); 12 Jun 2018 11:54:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jun 2018 11:54:32 -0000 Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.18 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.15.18 mout.gmx.net Received: from [212.227.15.18] ([212.227.15.18:57319] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B5/51-27729-764BF1B5 for ; Tue, 12 Jun 2018 07:54:26 -0400 Received: from [192.168.2.105] ([79.222.35.93]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MhQxO-1ffPRW3DgA-00MfE2; Tue, 12 Jun 2018 13:54:12 +0200 To: Stanislav Malyshev , PHP Internals References: Message-ID: Date: Tue, 12 Jun 2018 13:54:14 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:QtfwQ8r1DhmqpIdAuzcWCUDhRPz7jiWxO1iu7mdkVY7TPQXZTxZ ngiT9QjPeVfSoNSDg0dZ/kRDrGq/t2QHM6ZTMzb62zhdAITw87dHkuFEIyGF1exGZ/xi0JT gnVTXxI/ldBhM6UuBv3PAXvk6BQmgTC3CyzKS/XqSsvfW7YUw4+1nh3kCzXB70xdNvIr4Ly /3nA6qNesxLR5jjp77NPQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:8BPRRo9S6Jo=:S2uCi6F7TB9qcO4ngsdYWH 4p0XvQn4vBAEzfdqHrlTi6Ii3VN6TSuM+PDBsm3v81oAF1uQhj1hnk4b91I52lXahmlorT+v5 ApHhya+eUA8XmOPkHUhb9wjq8koM1WfmfKR1wFW+kA9D1eP0z3gEyzfZi3M0vGDzefT8/GkOU apzxyo3eLKYU0yOLxyIp5LHIliIZ64fTnzo1j4Lae27rJOpnfNawvSwNxwZYWSgKrw6u/8Ix+ LOKfe/5MpdhHcWYpJUA/XI0ed+WFgOcJugVCL2IlQFNZqwsZEGArVe8+eWFSP3y8lE9GmzIVP 0FPdhcLcqG+WZgYCqqCrgqH4XVWjRkr0EXQtmdleAthACqfs8GG97HiW0eMOPXu/iAsl0w1d/ whfC2sF/2oH4fQSz8Idjv51TDxFbWNxacPeDEMnpSKbC7ntt3Oga0fK2u18fn/ZVvr8Uygq7K DRGdd3EL4bRqYtRXvKHruRggcpNb5uryjuxrMWlC1InKfDlj43844YJ67Nxj1sahJOHQctlDS 7fiuXC+j5xq55uDZn5sxPwfrBTexIXm8NimYtEVMxH7l9XK+h59hzvgDg2+LSIAEERgz93j6l odiYnX6IHtLHjjJKJwYuxlKw8MxHZ+e41ny8gdTusdjMOTHICB+fhpG9NoS53CtbsoSEVTr0G VOEYVWDjK7y+MAZ96sA9fusaTfm9a4hQsw1ryJITcC1s1wqiBE1E5BZ5TV/BDWucL3tf0lZG4 /UzwxlFUjqjQh80ONF/zSJ4PYEnVJDSQvW+PZFj4geL44dlCY7VtMwJ2wEqSxk+yNtxhV+hCe Adwa29y Subject: Re: [RFC] orphan extensions cleanup From: cmbecker69@gmx.de ("Christoph M. Becker") Hi Stas! On 15.08.2016 at 07:53, Stanislav Malyshev wrote: > I'd like to propose an RFC to deal with extensions that currently have > no maintainer: > > https://wiki.php.net/rfc/umaintained_extensions > > The main goal of the RFC is to initiate the process that by the time of > 7.1 release will result in no extensions in PHP core being unmaintained. > The process would be as follows: > > 1. Issue a call for maintainers (specific details of how, where, etc. > are to be discussed, ideas welcome). > 2. Wait for suitable time and hopefully find new maintainers for most or > all extensions. For some stable ones not much commitment is needed > beyond declaring you are willing to be responsible for them, should the > need arise, for others some bugfixing may be in order :) > 3. If after suitable time we can not find anybody to care enough for the > extension to be responsible, move the extension from core to PECL. > > Please note that the ideal result is 2, not 3, but the goal is still to > have no unmaintained extensions in core. I think it is *very* important to finally tackle this topic. Since it is rather late for actually moving several extensions to PECL for PHP 7.3, and since this would be an ongoing process anyway, I suggest to turn the RFC into a general RFC regarding “Process and Policy” – basically, to decide on clear rules regarding maintainership of extensions and moving of orphaned extensions to PECL. Individual extensions could than be handled without the need for much discussion and be resolved with a simple RFC/voting (or maybe even without). -- Christoph M. Becker