On 09/11/2013 02:35 PM, Johannes Schlüter wrote: > On Wed, 2013-09-11 at 12:44 +0200, Florin Patan wrote: >> - having a RFC to make a language change requires to have a patch >> which if you don't know C and internals you got no chance of doing. > > Well, so what should happen? An RFC without patch is accepted and then? > Somebody has to write a patch at some time. Whom of the people spending > their free time do you want to force to do that even though they might > not be interested in the feature?
That's a point I keep on hearing on this list (and I actually agree) - but how do other projects manage that? Is there a core team that's more inclined to "step up" and just clean a mess someone else left or handling cruft that somehow pops up? Unless you have an entity (non-profit or for-profit) that's handling everyday chores/tasks/steering the vision and demands from its members to do stuff they don't take up on your own... I don't see how it could be done in another way :) Greetings, Florian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
