# Does the Nov 16 - Nov 30 voting timeframe still work? **URL:** \ **Category:** Committers\ **Created:** [November 13, 2018, 2:41pm UTC](https://discuss.python.org/t/does-the-nov-16-nov-30-voting-timeframe-still-work/434 "2018-11-13T14:41:58Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![njs](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/njs/32/204_2.png) [@njs](https://discuss.python.org/u/njs)\ **Post date:** [November 14, 2018, 2:35pm UTC](https://discuss.python.org/t/does-the-nov-16-nov-30-voting-timeframe-still-work/434/10 "2018-11-14T14:35:22Z")
> [@Python Governance Electoral System](https://discuss.python.org/t/python-governance-electoral-system/290/120): > > Wait, what? Why? I don’t see this decided anywhere. The original PEP 8001 specified explicitly that people are free to change their mind for the period of the vote. To change this we would need to have an explicit discussion about why this is an issue, there was none. > > If you mean “ Allow voters to write in new choices.” then I understood this as the inability for people to _add new options_ to the poll. This is of course uncontroversial. No, that’s not what I mean :-). I mean that PEP 8001, the one that’s currently in the PEP’s repo, has been revised to make it so that you cannot change your mind after you cast your vote. (Or, well, you can change your mind, but if you do then sucks to be you, because you can’t change your vote.) You probably want to read this thread: > [@PEP 8001: Public or Private Ballots?](https://discuss.python.org/t/pep-8001-public-or-private-ballots/374/20): > > I too would like it better if people could change votes, as often as they like, before the election ends. Against that, CIVS has battle-tested software to get everything else right. So, if we use CIVS, that’s a tradeoff: people need to be aware that they cannot change their vote. And so they’d be well advised to delay voting until near the end of the voting window. A good point: CIVS does not close the election on its own. Our election supervisor has to close it “by hand”. So if a slew … So uh, I don’t want to put words in your mouth, but putting that fact together with what you wrote, it sounds like you’re saying that PEP 8001 requires further discussion? > [@Python Governance Electoral System](https://discuss.python.org/t/python-governance-electoral-system/290/120): > > there was a [non-disputed deadline for original PEP submissions](https://mail.python.org/pipermail/python-committers/2018-September/006127.html) of October 1st that was later extended by a week “Non-disputed” feels a bit revisionist? [1](https://mail.python.org/pipermail/python-committers/2018-August/005963.html), [2](https://mail.python.org/pipermail/python-committers/2018-August/005965.html), [3](https://mail.python.org/pipermail/python-committers/2018-August/005966.html), [4](https://mail.python.org/pipermail/python-committers/2018-August/005973.html), [5](https://mail.python.org/pipermail/python-committers/2018-August/005985.html), [6](https://mail.python.org/pipermail/python-committers/2018-August/005993.html) > [@Python Governance Electoral System](https://discuss.python.org/t/python-governance-electoral-system/290/120): > > Exactly right: pushing it by even “one week” will likely mean we are pushing the vote to 2019. I mean, I know it’s no-one’s favorite outcome, but if the end result of all this is that the vote schedule slips once and things are resolved in January, then that’s not the end of the world? Even if we pick one of the proposals that requires a followup vote and that takes a month, then we’ll still be done by the end of Februrary, well ahead of Guido’s deadline of PyCon (which is May 1-9). And everyone who’s been pushing for voting ASAP will still get to feel satisfied that their work kept things moving well enough to keep us down to a single schedule slip :-). --- _[View the full topic](https://discuss.python.org/t/does-the-nov-16-nov-30-voting-timeframe-still-work/434)._