hi Philip, On Sat, Jun 4, 2011 at 3:29 PM, Philip Olson <phi...@roshambo.org> wrote:
> - RFC: Request For Comments Thanks for the reminder. But RFC got approved at some point as well. See the numerous W3C RFCs for some known examples. > And while doing so, not revert to a vote (RFV?) simply because discussing a > topic can get messy. What got messy? That instead of simply rejecting the RFC instead of constantly adding new ideas to the stack. It is a perfectly valid flow to block a RFC because it is considered as not well designed, not desired or simple not fully compliant. It happened many times in php in the past and in other projects as well. > Voting has clear winners and losers with potential loss for improvements. > That and you must then worry about who can and cannot vote (i.e., > non-inclusive community). It's rare that we've required a formal vote, so I > fear we will now implement voting at inappropriate times rather than allow a > consensus to be reached. I'm sorry to not be powerful enough to achieve my ultimate goal, have the most open processes and decissions in the OSS world within PHP. That is, to include the communities in the decision processes and not only to propose things. Now you can keep arguing that voting is pointless, unfair, that consensus can be reached easily, etc. etc. What we see is a total different picture which is more related to dictatorial decisions or puchists. None of these ways are good. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
