Hi!
As long as it is completely obvious what is being voted on and the process is followed, the voting RFC rules are fine. It would be nice though if we could iterate in order to get 2/3 approval on most proposals. It is these 50/50 ones that are problematic and often boil down to half the people voting, "We want this feature!" and the other half voting, "Yes, but this implementation, as proposed, is half-baked."
This is exactly the problem. Most of the people vote for generic idea, but later it's taken as approval of specific design and specific patch attached to the RFC - even though I'm willing to bet most of the voters didn't actually read the patch and verified it even works. Which would be fine if there would be additional layer of supervision from core - but "equal vote for all" precludes that, and I see a problem with that.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
