Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-19 Thread Yasuo Ohgaki
On Tue, Jun 19, 2018 at 9:37 PM, Johannes Schlüter wrote: > Hi, > > On Di, 2018-06-12 at 13:54 +0200, Christoph M. Becker wrote: > > > > https://wiki.php.net/rfc/umaintained_extensions > > > > I think it is *very* important to finally tackle this topic. Since > > it > > > It's a good subject to

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-19 Thread Johannes Schlüter
Hi, On Di, 2018-06-12 at 13:54 +0200, Christoph M. Becker wrote: > > https://wiki.php.net/rfc/umaintained_extensions > > I think it is *very* important to finally tackle this topic.  Since > it It's a good subject to think about, but we should be careful not to end with a process and then foll

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-14 Thread Nikita Popov
On Thu, Jun 14, 2018 at 4:00 PM, Christoph M. Becker wrote: > On 14.06.2018 at 00:47, Stanislav Malyshev wrote: > > >> That said, in my opinion it is too late for 7.3 to move a bundled > >> extension to PECL, except perhaps for unresolved or even unresolvable > >> security reasons. ext/wddx come

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-14 Thread Christoph M. Becker
On 14.06.2018 at 00:47, Stanislav Malyshev wrote: >> That said, in my opinion it is too late for 7.3 to move a bundled >> extension to PECL, except perhaps for unresolved or even unresolvable >> security reasons. ext/wddx comes to mind, and maybe there are others. > > I'd be happy to move wddx i

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-13 Thread Stanislav Malyshev
Hi! > That said, in my opinion it is too late for 7.3 to move a bundled > extension to PECL, except perhaps for unresolved or even unresolvable > security reasons. ext/wddx comes to mind, and maybe there are others. I'd be happy to move wddx if nobody steps up to maintain it. It has tons of secu

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-13 Thread Christoph M. Becker
On 12.06.2018 at 22:09, Stanislav Malyshev wrote: > Yes, I think having some rules on maintainership would be nice, right > now I haven't even considered extensions which have maintainers listed > but no longer active, etc. - though I suspect those exist too. […] >From looking at current EXTENSIO

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-13 Thread Christoph M. Becker
On 13.06.2018 at 16:48, Sara Golemon wrote: > On Tue, Jun 12, 2018 at 4:09 PM, Stanislav Malyshev > wrote: > >> I'm not sure it's too late for 7.3. If we see that the extension is >> unmaintained, we could move it out for 7.3 I think. > > Well, you and cmb are the RMs for 7.3, so you get the lar

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-13 Thread Christoph M. Becker
On 12.06.2018 at 23:33, Stanislav Malyshev wrote: >>> I'm afraid this might be misused.  It's too easy to update the year >>> number, without actually doing *any* real maintenance work (“I'll come >>> back to that later” …).  Some automated process would be nice, but >>> manually checking the bug

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-13 Thread Sara Golemon
On Tue, Jun 12, 2018 at 4:09 PM, Stanislav Malyshev wrote: > I'm not sure it's too late for 7.3. If we see that the extension is > unmaintained, we could move it out for 7.3 I think. > Well, you and cmb are the RMs for 7.3, so you get the largest say in that, but IMO we won't finish sorting out th

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Stanislav Malyshev
Hi! >    I'm afraid this might be misused.  It's too easy to update the year >    number, without actually doing *any* real maintenance work (“I'll come >    back to that later” …).  Some automated process would be nice, but >    manually checking the bug tracker for maintenance work (particularly

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Rowan Collins
On 12 June 2018 at 16:01, Christoph M. Becker > wrote: I'm afraid this might be misused.  It's too easy to update the year number, without actually doing *any* real maintenance work (“I'll come back to that later” …).  Some automated process would be nice, but

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Stanislav Malyshev
Hi! > Per issue #1, I'd suggest an OWNERS file per ext/*/ dir with names and > year ranges. Continued ownership demarked by explicitly incrementing > the end year BY THE MAINTAINER. An extension is considered abandoned > if the end year is not updated by the following January. Example: Makes s

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Stanislav Malyshev
Hi! > 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 I'm not sure it's too late for 7.3. If we see that the extension is unmaint

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Christoph M. Becker
On 12.06.2018 at 16:15, Sara Golemon wrote: > Per issue #1, I'd suggest an OWNERS file per ext/*/ dir with names and > year ranges. Continued ownership demarked by explicitly incrementing > the end year BY THE MAINTAINER. An extension is considered abandoned > if the end year is not updated by t

Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread Sara Golemon
On Tue, Jun 12, 2018 at 7:54 AM, Christoph M. Becker wrote: > 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

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2018-06-12 Thread 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

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2016-08-17 Thread Christoph M. Becker
Hi! On 15.08.2016 at 22:39, Stanislav Malyshev wrote: >> Maybe it would be better to first check the current status quo of >> maintainership, and after that taking care of the insufficiently >> maintained extensions. > > I think we can do both in parallel. I'll try to write the second RFC > soon

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2016-08-15 Thread Stanislav Malyshev
Hi! > Maybe it would be better to first check the current status quo of > maintainership, and after that taking care of the insufficiently > maintained extensions. I think we can do both in parallel. I'll try to write the second RFC soon (hopefully I'll have time) and we can do the maintainer lis

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2016-08-15 Thread Christoph M. Becker
Hi! On 15.08.2016 at 18:46, Stanislav Malyshev wrote: >> Generally, I'm all for moving unmaintained extensions to PECL. >> However, I wonder on what information the concrete selection of >> unmaintained extensions in the RFC is based. If it is >> php-src/EXTENSIONS, the RFC is moot, in my opinio

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2016-08-15 Thread Stanislav Malyshev
Hi! > Generally, I'm all for moving unmaintained extensions to PECL. > However, I wonder on what information the concrete selection of > unmaintained extensions in the RFC is based. If it is > php-src/EXTENSIONS, the RFC is moot, in my opinion, as this file is > grossly out-dated. It seems that

[PHP-DEV] Re: [RFC] orphan extensions cleanup

2016-08-15 Thread Christoph M. Becker
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