Hi there (especially patka aanderse piotrkwiecinski talyz)
I think it might make sense to do a small, sync here, now that Pol left.
First of all, are you all still interested in maintaining the PHP subsystem?

Now, a few points about the ecosystem:

• the only issue on interpreter-level I'm aware of is https://github.com/NixOS/nixpkgs/issues/353135 which I may fix eventually (though it has pretty low prio on my end). Is there anything else I (or someone else in the team) may not be aware of?
• regarding php interpreter updates: I did the backports and the last few updates together with Pol and I intend to carry on. Since I'm only running PHP applications these days, packaging alphas (and don't do any development anymore), I probably won't spend time on adding alphas of new minors/majors, if somebody else wants to do taht - feel free.
• are there any other issues in the ecosystem we maintain? I didn't find much more open issues, though it seems as if a lot of stuff isn't labeled in the issue tracker.
• what are we going to do with all the CLI applications? so far, I let Pol take care of this since I'm not a PHP dev and thus not very invested into a lot of these. My ideal would be to phase out as much as possible (e.g. Composer is carrying the ecosystem, so it can stay, but I don't see a reason why standalone applications like psysh or phpunit should be maintained by us) and transfer it to individuals. If we don't find anybody who's interested in keeping thsoe up-to-date, I'd consider to drop them entirely.

Anything else we need to talk about?

thanks for the message @ma27:nicht-so.sexy

these days i am more interested in just ensuring the ecosystem stays viable... i don't intend to do much work on it but am happy to be pinged on issues and if no one else more active is able to i can help out

i agree we should stick to stable releases and not try to take on too much unless someone is committed to actively maintaining that

personally i am not keen on nixpkgs dropping a bunch of software but it seems that is the direction we're heading so if you want to follow the trend and drop a few pieces over time i understand

personally i am not keen on nixpkgs dropping a bunch of software but it seems that is the direction we're heading so if you want to follow the trend and drop a few pieces over time i understand

yeah, that's understandable. I wouldn't be too hapyp about this, but it's still better than having outdated, hardly maintained pakcages for that.

the problem-infrastructure is still not mreged, right? otherwise an option would be to add "X is looking for maintainers" notes onto a bunch of those packages.

are there any other issues in the ecosystem we maintain?

I just found this one: https://github.com/NixOS/nixpkgs/issues/277285. To me it's not that important, but perhaps someone else here finds it interesting enough to look into?

the version of invoiceplan (which is the latest btw) only tests against php 8.1. considering that a lot of projects fail to reasonably express their php constraints ("php": ">=7.4" absolutely doesn't count and is for me equivalent to no constraints at all), that's the only information I actually care about.

and I mean, if nobody stood up to upgrade the versions tested to something that's not security-fixes-only in years, then I think it's absolutely fair to drop the package from nixpkgs.