> -----Original Message----- > From: Benjamin Morel [mailto:benjamin.mo...@gmail.com] > > > And we could change the RFC process to either: > > - require a 2/3 majority of votes *in each category* > - *or *require a 2/3 majority in the *average of all three categories* > - *or *give a weight to each category (like 50% to core members, 30% to OSS > developers and 20% to the rest of the world) and calculate the result > accordingly > - *or even* something like require a 2/3 majority in at least 2 of these > categories > > ... or any other rule we could think of. > > I quite like this idea of splitting voters into 3 categories, where each > category > has a weight that does not depend on the number of people who voted inside > it. > > Something like this would seem fair to me. Thoughts?
The problem in this is that - what good is a vote/RFC if no one is there to implement it? Like you could get and overwhelming majority/weight in all the non-developer groups but what then? Are you then forcing someone to write the code? Pick someone from the group(s) who voted for or pay someone to do it (quite valid though)? IMO even now all the discussion in the internals@ (hence the name) for the developer (RFC author) is just to see if any other code contributor has something to say about his idea. The rest can voice their concerns but as long you don't really contribute yourself I doubt you get to choose in the end.. rr -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
