On Mon, Apr 16, 2012 at 3:01 PM, Tom Boutell <t...@punkave.com> wrote:
> Such a vote would make sense if it were clearly expressed that the > final RFC would also be subject to a binding vote, so there is no risk > of being forced to accept an implementation whose particular details > are unacceptable to you. > > On Mon, Apr 16, 2012 at 5:48 PM, Arpad Ray <array...@gmail.com> wrote: > > Please excuse me for butting in without immediate context. I'd just like > to > > support the idea of a vote on this concept without getting into > specifics. > > > > If the vote is positive then we can argue the various merits of the > > competing RFCs knowing that we at least agree in general. On the other > hand > > if the vote is negative, we can save a significant amount of time and > > effort, and can concentrate on more plausible subjects. > > > > Cheers, > > > > Arpad > > > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Problem is, the RFC voting process currently does not allow for this. You could take an informal vote, but I honestly don't see much value in that given that we've already invested ourselves in this. Any opinions on my idea of creating an RFC to expand the voting procedures? I'd be more than happy to draft one, but only if it's something people would actually be interested in. So far, the lack of response suggests to me that there is no interest in that, in which case we should accept the voting process as-is and vote on each RFC as a whole after the prescribed 2-week minimum discussion period. --Kris
