[python-committers] Vote on governance will happen between Nov 16 - Nov 30

[Donald Stufft]

> On Oct 23, 2018, at 7:06 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> 
> On Tue, 23 Oct 2018 at 06:38, Łukasz Langa <lukasz at langa.pl> wrote:
>> 
>> The voting procedure is described in PEP 8001. I flipped it from "Draft" to "Active" without further changes a few minutes ago. That's in the interest of giving everybody enough lead time as well as resolving the situation "well before PyCon 2019" as per Guido's and Carol's requests.
>> 
>> Please read all the governance PEPs, ask for clarifications, voice all your concerns now. Ideally we will make all of the required changes to the PEPs early and not last minute before the vote.
>> 
>> There were some suggestions on Discourse for changes to the selected model, the biggest being Stefan's suggestion to encrypt the votes and Donald's suggestion to use STAR instead of IRV for counting votes. We ended up not going with those suggestions. See Brett's comment here as to why:
>> https://discuss.python.org/t/pep-8001-python-governance-voting-process/233/46
> 
> My main concern was about the potential for vote-splitting with
> multiple "council" type proposals on the ballot, and IRV is enough to
> address that (having been an Australian voter for ~22 years, I'm also
> very familiar with it, and given the specific set of proposals we're
> voting on, I don't think the case where STAR would give a different
> answer is likely to come up - the various draft PEPs have too much in
> common with either each other or the status quo for it to be likely
> that a significant proportion of the folks voting will find any of
> them completely unacceptable)
> 


We’re using IRV and I accept that, but I just want to point out that IRV still has a form vote splitting (in electoral parlance, vote splitting is the “favorite betrayal criterion” - https://www.youtube.com/watch?v=JtKAScORevQ <https://www.youtube.com/watch?v=JtKAScORevQ>. IRV only protects against vote splitting when you have a very weak or a very strong candidate ranked first.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20181023/6019ba5e/attachment.html>