Ivan Enderlin @ Hoa wrote (on 23/07/2014):
My idea was to constitute a **PHP Consortium** (yes, the name is classy but it reflects the reality), responsible to maintain and edit the PHP Specification. With what members? Members from the PHP Group (maintainers of php-src), from Facebook (maintainers of HHVM), from HippyVM, from JPHP etc. and from others important projects (e.g. Symfony, Zend etc.), just like the PHP Group does with the RFC votes.
This sounds like a nice idea, but there would then be an awkward relationship between this process and the existing RFC process.
Currently, an RFC can be proposed and discussed within internals@ which makes changes to the language as implemented by the de facto reference implementation.
If that process is not allowed to change the specification directly, then the Zend/php.net implementation would cease to conform to the specification, until such time as The Consortium also accepted the change, and updated the specification to match. If the change was rejected, there would be a power struggle: either the RFC process would have lost power over the language, or the specification would disagree with its oldest and most popular implementation.
On the flip side, there is definitely value in representatives from other implementations having a voice in changes that affect them, but that could just mean ensuring that members of those projects are involved within the current framework.
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
