Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128808
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>
In-Reply-To: <CAEZPtU6NJfxjckrpikVfmFcJ2OyhhKg3YJdqTkpvPaU_uMeyGg@mail.gmail.com>
Date: Fri, 10 Oct 2025 12:36:42 +0200
Message-ID: <CAEKnhAEsGS+k7Mg4Z1z-fbWh4hsAbkpgTxsdJEYaG7N1+F=Ddg@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="0000000000002545550640cb7fb6"
From: bukka@php.net (Jakub Zelenka)

--0000000000002545550640cb7fb6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Fri, Oct 10, 2025 at 12:01=E2=80=AFPM Pierre Joye <pierre.php@gmail.com>=
 wrote:

> Hi James,
>
> On Fri, Oct 10, 2025, 3:29 PM James Titcumb <titcumbjames@gmail.com>
> wrote:
>
>> On Thu, 9 Oct 2025 at 21:39, Christoph M. Becker wrote:
>>
>>> Apparently, this RFC has been withdrawn in the meantime.  I would like
>>> to know why. :)
>>
>>
>> I absolutely agree with you - a discussion took place on the PHP
>> Foundation slack. I raised a concern that it should be discussed here on
>> the list for transparency. I am frustrated that it was not.
>>
>> The short version of that discussion is that PEAR is maintained by
>> someone else; the PEAR group apparently is separate from the PHP group, =
as
>> I understand it.
>>
>
>
> I don't remember the reason back then but it was basically maintained by
> core devs at some point, including myself.
>
>
Is that still the case though? 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?

Alternatively we could potentially propose here move that away from the PHP
domain if we think it's not good for PHP image but that could mean that we
might completely shut it down without any deprecation if there is no
agreement with the current maintainers.

So the ideal case would be to put together some plan how to either get it
deprecated and moved away. But for that we need to first here from the
current maintainers and get them on board.

If here is anyone who has access to PEAR and can comment on this, that
would be great! I also CC'd Chuck as I think it's crucial to get his
opinion on this.

Kind regards,

Jakub

--0000000000002545550640cb7fb6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail_quote gmail_quote_co=
ntainer"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 10, 2025 at 12:0=
1=E2=80=AFPM Pierre Joye &lt;<a href=3D"mailto:pierre.php@gmail.com">pierre=
.php@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"auto"><div><div>Hi James,</div><div><br></div><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 1=
0, 2025, 3:29 PM James Titcumb &lt;<a href=3D"mailto:titcumbjames@gmail.com=
" target=3D"_blank">titcumbjames@gmail.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"=
><div dir=3D"ltr"><span><div><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Thu, 9 Oct 2025 at 21:39, Christoph M. Becker wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Apparently, this RFC has been withdrawn in the meantime.=C2=A0 I would like=
<br>
to know why. :)</blockquote></div><br></div></span><div>I absolutely=20
agree with=C2=A0you - a discussion took place on the PHP Foundation slack. =
I=20
raised a concern that it should be discussed here on the list for=20
transparency. I am frustrated that it was not.</div><div><br></div><div>The
 short version of that discussion is that PEAR is maintained by someone=20
else; the PEAR group apparently is separate from the PHP group, as I=20
understand it. </div></div></div></div></blockquote></div></div><div dir=3D=
"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">I don&#39;t =
remember the reason back then but it was basically maintained by core devs =
at some point, including myself.</div><div dir=3D"auto"><br></div></div></b=
lockquote><div><br></div><div>Is that still the case though? I don&#39;t th=
ink that any current core developer has access to their GH organizattion. O=
r do you still have access / control to do any changes there and make it de=
precated? My main issue with this RFC is that it&#39;s about project that w=
e 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?</div><div><=
br></div><div>Alternatively we could potentially propose here move that awa=
y from the PHP domain if we think it&#39;s not good for PHP image but that =
could mean that we might completely shut it down without any deprecation if=
 there is no agreement with the current maintainers.</div><div><br></div><d=
iv>So the ideal case would be to put together some plan how to either get i=
t deprecated and moved away. But for that we need to first here from the cu=
rrent maintainers and get them on board.</div><div><br></div><div>If here i=
s anyone who has access to PEAR and can comment on this, that would be grea=
t! I also CC&#39;d Chuck as I think it&#39;s crucial to get his opinion on =
this.</div><div><br></div><div>Kind regards,</div><div><br></div><div>Jakub=
</div></div></div>

--0000000000002545550640cb7fb6--