Issue #16
14 July 2026
"Software is shaped not only by the code we write, but by the structures around it: how people find their way into a project, how deeply we understand existing implementations, and what guarantees our infrastructure provides. This issue examines how the PHP ecosystem is organizing its continued development."
— Stefan & Sebastian
ben.ramsey.dev
PHP has people eager to contribute, but it does not always give them a clear place to begin. Ben Ramsey proposes chartered working groups that make responsibilities, membership, communication, and decision-making explicit without introducing a new hierarchy.
Picked by Stefan Priebsch – "PHP does not lack people willing to contribute; it lacks visible paths into the work. Ben's proposal is an interesting starting point for further discussion."
scherzer.dev
Daniel Scherzer rewrote PHP's Reflection extension in Rust as a learning exercise. Examining the existing implementation line by line uncovered an eighteen-year-old bug, missing type validation, documentation errors, and opportunities to simplify and optimize the C code.
Picked by Sebastian Bergmann – "A rewrite can be valuable even when it is never intended to replace the original. Daniel's experiment produced a deeper understanding of the current implementation."
blog.packagist.com
Packagist has made stable version metadata immutable. Once a version has been published, the Git reference behind it can no longer be silently changed, while deleted versions remain visible with an explanation and actions such as blocked retags are recorded in a transparency log.
Picked by Stefan Priebsch and Sebastian Bergmann – "A version number must identify one body of code, forever. Making stable versions immutable removes ambiguity for users, tools, and security processes."