On 18-6-2026 18:33, Juliette Reinders Folmer wrote:
On 18-6-2026 13:34, Rowan Tommins [IMSoP] wrote:
On 18 June 2026 09:05:58 BST, Derick Rethans<[email protected]> wrote:
On 18 June 2026 07:13:13 BST, Nick Sdot<[email protected]> wrote:
Perhaps it would make sense to disable editing old and adding new proposals,
and remove the spam.
I think it's safe to conclude that there is no PEAR team, the entire project is
abandoned, and we need to decide what to do with the pear.php.net domain to
protect the reputation of PHP.
Probably that means setting up a read-only mirror somewhere and pointing the
DNS at it so that clients don't break overnight.
Just a heads-up: I would very much favour some form of a readonly
version of the site to stay available - probably with a banner that
this is only still available for archive purposes (and disable any
logins and form-submissions except admin).
I, for one, still semi-regularly have to go back to the issue tracker
on the PEAR site to dig up the reasoning/motivation for decisions
taken long ago for an old codebase, where the commit messages,
especially for older commits, are not great.
Not being able to do so anymore would definitely have some impact on
the work being done on that codebase.
Was just trying to dig up the background of some old bugfixes on the
PEAR website and when I click to see the details of an individual bug
report, I now get an "ERROR: the user who submitted this bug has not yet
confirmed their email address" page instead of seeing the bug details.
Example: https://pear.php.net/bugs/bug.php?id=20093
Clearly this is not helpful.
Not sure when this changed, but felt like something related to last
month's conversation, so I figured I'd flag it.
Smile,
Juliette
