What plans and does the Omeka S development team have for moving away from the Laminas MVC component which is scheduled for end-of-life by December 31, 2025 since the Laminas Technical Steering Committee (TSC) have decided to discontinue active development of Laminas MVC.
We’re aware of Laminas’s recent announcement about their MVC component.
We haven’t made a decision yet on what our way forward is going to be there. Moving to another paradigm is possible, but obviously would be a pretty disruptive change for modules. Since this was only publicly announced recently, the landscape also isn’t quite settled in terms of possible migration paths, forks to continue maintenance of the MVC component, etc.
This is going to be a very difficult decision and process, I don’t envy you in trying to make the right choices here.
I will admit my one big reservation about choosing Omeka S was it’s being based on Laminas MVC and how inactive it was, especially compared to the likes of Symfony, Laraval or even Django. Even were someone to fork it, the viability of that fork beyond a transitional ‘escape’ period would be have to be questionable.
That said, it sounds like they will support the PHP 8.5 release in November, which gets 2 years active support and 2 years security support, so that’s a 4 year window before actually running it in a secure environment becomes difficult (although any eventual removal from Packagist may be a bigger issue).