Hi Alessandro, Larry asked me to just jump in and clarify this (the legalese part of the spec was mostly from me and this also relates to existing bylaws).
It's based on the current wording (and rounding rules) in the current Voting Protocol where no tie is possible, the burden of proof, so to speak, lies with the person calling for a motion to pass and rounding is clarified through examples. This appears to be the easiest way to do it to be honest without lots of verbosity which has the ability to hinder understanding than improve it. If you have any alternative suggestions for wording they would be most welcome although I suspect a similar discussion occurred when the original Voting Protocol was written (PMJ: Perhaps you could confirm this?). I would draw note to the current voting protocol, in particular points 5 and 6: https://github.com/php-fig/fig-standards/blob/master/bylaws/001-voting-protocol.md -- Michael Cullum FIG Secretary On 24 August 2016 at 22:26, Alessandro Lai <alessandro.la...@gmail.com> wrote: > Larry, it think that the part about vote rounding is not clear enough; > it's understandable through the examples, but the rule is somewhat > "implicit" in there. > > Il giorno mercoledì 24 agosto 2016 15:51:27 UTC+2, Larry Garfield ha > scritto: >> >> Can you note anything in particular that is clumsy to read? We were >> aiming for explicitness and lack of vagueness, which in prose does tend to >> lead to verbosity. To me it still reads fairly well, but as the author I >> am of course biased on that front. :-) >> >> --Larry Garfield >> >> On 08/24/2016 05:27 AM, 'Alexander Makarov' via PHP Framework >> Interoperability Group wrote: >> >> Well, clarity of the document. It takes time to find what you need so >> maybe wording or structure could be improved for better comprehension, >> cross-linking introduced etc. >> >> On Wednesday, August 24, 2016 at 1:07:40 AM UTC+3, Alessandro Lai wrote: >>> >>> Well, the vote has now been canceled. I've just now finished reading >>> again the full diff, and I've found clarifications about possible tie >>> votes: majority must be +1 with 50%: https://github.com/php-fig/fig >>> -standards/pull/752/files#diff-a7e6254aa839471064951898e0ebb021R17 >>> >>> So basically no tie is possible. >>> >>> Are there any other doubts to be settled? >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/php-fig/1878ff62-fb7a-458d-b83a-5cfdb9a7733b%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/1878ff62-fb7a-458d-b83a-5cfdb9a7733b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAqcDMjVMBTB8t%3D0tzZ5PF5FTqhzkBrNTDVT%3D8fBaapKFQq89w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
