Hi Daniil On Sat, Mar 14, 2026 at 7:32 PM Daniil Gentili <[email protected]> wrote: > > Submitting for discussion the php-community RFC, for a faster-moving, > community-driven PHP: https://wiki.php.net/rfc/php-community
I understand and appreciate your desire to accelerate the development speed of PHP. However, this proposal would put a completely unrealistic burden on php-src maintainers. By design, it would become very easy to add new features to the community branch. However, code isn't merged and forgotten; it requires continued maintenance. Features interact, bugs need to be fixed, code will diverge from release branches and require conflict resolution, development of features through PRs would still require reviews by maintainers, etc. The additional effort to keep all of this working correctly for underspecified and questionable features would be immense. There's no real veto for php-src maintainers, a single internals member can overrule the "veto" mentioned in the RFC. If a problematic feature is accepted, it must be supported for at least 6 months, further burden falls on php-src maintainers to propose the removal of the problematic feature, and it might not even be removed unless: > Adoption is negligible, as evidenced by Packagist statistics. I honestly think this would be catastrophic. I think this development model works much better with authoritative working groups or a benevolent dictator, along with a coherent roadmap. And crucially, failed ideas would be removed before this community edition becomes a cemetery of failed ideas. Ilija
