Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128818
Precedence: list
MIME-Version: 1.0
References: <CAOD_yv0k=1nBq6LOR9w2pNXHnjtPL5NtBV=SLRsKjpVCK1dFug@mail.gmail.com>
 <fdf1d284-27bf-4bb2-924e-21fa82673c6f@gmx.de> <CAOD_yv2Sga6P1N-Uu2w-nyyY-XMvytWy-_r1v=xZpygQ_67iRQ@mail.gmail.com>
 <CAEZPtU6NJfxjckrpikVfmFcJ2OyhhKg3YJdqTkpvPaU_uMeyGg@mail.gmail.com>
 <CAEKnhAEsGS+k7Mg4Z1z-fbWh4hsAbkpgTxsdJEYaG7N1+F=Ddg@mail.gmail.com>
 <CAEZPtU4PLw7-Tu4vUVqHus71maeTsQuAKQxVbqLxSkY9eErDyg@mail.gmail.com>
 <CAEKnhAFTkrXPdPw3rXbLUPY-shHwTYxTSqM3cLBY7iRCaqrfHA@mail.gmail.com> <CAEZPtU47NHVNty=VKbnAANqhqWzHrh=ztFnGCGQzfAs6QSAf6g@mail.gmail.com>
In-Reply-To: <CAEZPtU47NHVNty=VKbnAANqhqWzHrh=ztFnGCGQzfAs6QSAf6g@mail.gmail.com>
Date: Sun, 12 Oct 2025 10:58:19 +0200
Message-ID: <CAEKnhAG0PmS3VdGZV_9rPF+pokszrNb41jkSRxNz6RoMqkfbvw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Deprecate PEAR and recommend Composer
To: Pierre Joye <pierre.php@gmail.com>
Cc: james@asgrim.com, "Christoph M. Becker" <cmbecker69@gmx.de>, 
	PHP Internals List <internals@lists.php.net>, ashnazg@php.net
Content-Type: multipart/alternative; boundary="000000000000ea37d40640f25a70"
From: bukka@php.net (Jakub Zelenka)

--000000000000ea37d40640f25a70
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 12, 2025 at 5:30=E2=80=AFAM Pierre Joye <pierre.php@gmail.com> =
wrote:

> On Sun, Oct 12, 2025 at 2:13=E2=80=AFAM Jakub Zelenka <bukka@php.net> wro=
te:
>
> > Ok so I guess the current status is kind on unknown... :) But as noted
> by Rowan in other email, there's a mention of the PEAR Group that is the
> governing body of the project although seems expired so I have really no
> idea what the governance there is and if the RFC process should have any
> power over that project.
> >
> >> > I don't think that any current core developer has access to their GH
> organizattion. Or do you still have access / control to do any changes
> there and make it deprecated? My main issue with this RFC is that it's
> about project that we don't effectively control and I'm not sure here is
> anyone who can make any such change to it. From what I see it's currently
> maintained by Chuck who, I guess, also control the project. Or am I wrong=
?
> >>
> >> I do have access, I did not check the role tho'.
> >>
> >
> > I guess this is really the crucial part here. Are you able / willing /
> comfortable to potentially update the website or the tool if we approve t=
he
> RFC about deprecation and are you sure that the current maintainer is ok
> with that (basically respect RFC as the governance method for PEAR)?
>
> To make it simple, PEAR is part of the PHP projects. There was a
> separate group to do the admin work, security releases when needed,
> sync with php releases to bundle it, etc.
>
> For the purpose of fading out pear, and, more importantly, pecl, we
> can handle it here using the normal RFC flow. Most of the group
> members are barely (f.e. me) or not active at all anymore.
>

 Ok, if you say so and can make such change, I think we should put this RFC
back for discussion.

Kind regards

Jakub

--000000000000ea37d40640f25a70
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Oct 12, 2025 at 5:30=E2=80=AFAM P=
ierre Joye &lt;<a href=3D"mailto:pierre.php@gmail.com" target=3D"_blank">pi=
erre.php@gmail.com</a>&gt; wrote:</div><div dir=3D"ltr"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, Oct 12, 2=
025 at 2:13=E2=80=AFAM Jakub Zelenka &lt;<a href=3D"mailto:bukka@php.net" t=
arget=3D"_blank">bukka@php.net</a>&gt; wrote:<br>
<br>
&gt; Ok so I guess the current status is kind on unknown... :) But as noted=
 by Rowan in other email, there&#39;s a mention of the PEAR Group that is t=
he governing body of the project although seems expired so I have really no=
 idea what the governance there is and if the RFC process should have any p=
ower over that project.<br>
&gt;<br>
&gt;&gt; &gt; I don&#39;t think that any current core developer has access =
to their GH organizattion. Or do you still have access / control to do any =
changes there and make it deprecated? My main issue with this RFC is that i=
t&#39;s about project that we don&#39;t effectively control and I&#39;m not=
 sure here is anyone who can make any such change to it. From what I see it=
&#39;s currently maintained by Chuck who, I guess, also control the project=
. Or am I wrong?<br>
&gt;&gt;<br>
&gt;&gt; I do have access, I did not check the role tho&#39;.<br>
&gt;&gt;<br>
&gt;<br>
&gt; I guess this is really the crucial part here. Are you able / willing /=
 comfortable to potentially update the website or the tool if we approve th=
e RFC about deprecation and are you sure that the current maintainer is ok =
with that (basically respect RFC as the governance method for PEAR)?<br>
<br>
To make it simple, PEAR is part of the PHP projects. There was a<br>
separate group to do the admin work, security releases when needed,<br>
sync with php releases to bundle it, etc.<br>
<br>
For the purpose of fading out pear, and, more importantly, pecl, we<br>
can handle it here using the normal RFC flow. Most of the group<br>
members are barely (f.e. me) or not active at all anymore.<br></blockquote>=
<div><br></div><div>=C2=A0Ok, if you say so and can make such change, I thi=
nk we should put this RFC back for discussion.</div><div><br></div><div>Kin=
d regards</div><div><br></div><div>Jakub</div></div></div>
</div>

--000000000000ea37d40640f25a70--