A vote is a personal thing. Everyone is responsible for their own vote. A vote must implicitly be taken to represent the best effort and intentions of the caster. It follows that a vote should not be questioned and is not up for discussion. That would discredit the caster, which does not compute in the context of the project, Apache and OSS.
If the caster of a vote wishes to 'carry' that vote to a new RC, that means the vote should apply - without reservation - to that new RC. EdB On Sat, Dec 6, 2014 at 6:07 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: > I understood the issue the same way. > > EdB > > > > On Saturday, December 6, 2014, Harbs <harbs.li...@gmail.com> wrote: >> >> I don’t want to prolong discussion, but I think there’s one point which >> needs to be clarified: >> >> Discussion in the VOTE thread made me realize that there might be a >> differing of understanding in what it means to vote and have votes carry >> over. >> >> My understanding and apparently the understanding of Om is that when a PMC >> member asks to carry over their vote, it’s because they are 1) aware of the >> changes between the last RC and the current one, and 2) confident that what >> they checked on the last RC is still valid. It was also my understanding >> that to cast a new vote on a new RC, one must go through the full rigamarole >> of checking the RC from start to finish, while carrying the vote only >> requires being certain that the vote is still applicable. >> >> If I read the emails correctly, Justin understood differently on both >> points. >> >> If my understanding of what it means to carry a vote over is correct, I >> think that resolves Justin’s concerns. >> >> Do I understand the issue correctly? >> >> Thanks, >> Harbs > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
