2015-03-10 16:02 GMT+01:00 Anthony Ferrara <ircmax...@gmail.com>: > Patrick, > > My viewpoint is that options in an RFC are dangerous. I would much > rather have a single RFC, with a single vote (yes/no). I think we > should be discouraging the options as much as possible. > > The reason is simple: an RFC should be an encapsulated idea, not a > menu of options. The author should take a stance. If there are details > that the author can't decide on, then either take a straw poll in the > mailing list, or create a separate RFC for that option. > > The problem with options is that it makes the vote much more > confusing. With 3 options, you have 3 different proposals. Some recent > votes have had upwards of 12 different proposals built in to a single > RFC (2 options + 3 options + 2 options). It's enough to ask someone to > read and understand one proposal completely without having them have > to comprehend all the possible permutations of voting outcomes. > > It also encourages weird voting patterns. Take your example of No/Yes, > A/B/C. In that case, you have 4 permutations as you pointed out. But > what's deeper, is how should someone vote if they are opposed to B? I > mean opposed, not just preferring a different one? The tendency would > likely be to watch the vote and if it looks like B will pass, vote no > on the entire proposal. > > Can we please come down to a single RFC, with a single vote yes/no? > It's easier to understand, easier to manage and has less possibility > of gaming. > > Anthony
That is much more stricter than my thoughts but I can't agree more with you on all the points you mentioned. You even presented cases I had in mind, thanks for the verbosity :) We should probably add this to https://wiki.php.net/rfc/voting which should probably RFC'ed... Thanks! Patrick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
