From 7db6f5c10912bddec8339ba26dd3c73de9ed88d8 Mon Sep 17 00:00:00 2001 From: "Nathaniel J. Smith" Date: Fri, 30 Nov 2018 16:55:31 -0800 Subject: [PATCH] PEP 8001: Add draft of vote details (#844) --- pep-8001.rst | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 70 insertions(+), 2 deletions(-) diff --git a/pep-8001.rst b/pep-8001.rst index 37b957a0b..6a6995b21 100644 --- a/pep-8001.rst +++ b/pep-8001.rst @@ -97,7 +97,75 @@ The election will be supervised by Ernest W. Durbin III, The PSF Director of Inf The results of the election, including anonymized ballots, will be made public on December 17th, after the election has closed. -The following settings will be used for the vote in the CIVS system:: +The following settings will be used for the vote in the CIVS system: + +Name of the poll: ``Python governance vote (December 2018)`` + +Description of the poll:: + + This is the vote to choose how the CPython project will govern + itself, now that Guido has announced his retirement as BDFL. For + full details, see PEP + 8001. Many discussions have occurred under the "governance" + tag on discuss.python.org. +

+ All votes must be received by the end of December 16th, 2018, Anywhere on + Earth. All CPython core developers are eligible to vote. + It is asked that inactive core developers who intend to remain + inactive abstain from voting. +

+ Note: You can only vote once, and all votes are final. Once + you click "Submit ranking", it's too late to change your mind. +

+ All ballots will be published at the end of voting, but without + any names attached. No-one associated with the Python project or + the PSF will know how you voted, or even whether you voted. +

+ If you have any questions, you can post in the Committers + topic, on the + python-committers list, or contact the vote administrator + directly. +

+

Options

+

+ We're selecting between seven PEPs, each proposing a different + governance model. +

+ The options below include links to the text of each PEP, as well + as their complete change history. The text of these PEPs was + frozen on December 1, when the vote started. But if you looked at + the PEPs before that, they might have changed. Please take the + time to check the current text of the PEPs if you read an older + draft. +

+ A "Further discussion" option is also included. It represents the + option of not making a choice at all at this time, and continuing + the discussion instead. Including this option lets us demonstrate + the core team's readiness to move forward. +

+ If you think a proposal is a particularly bad idea, you can + express that by ranking it below "Further discussion". If you + think all of the proposals are better than further discussion, + then you should rank "Further discussion" last. + +Candidates (note: linebreaks are significant here):: + + PEP 8010: The Technical Leader Governance Model (Warsaw) (changelog) + PEP 8011: Python Governance Model Lead by Trio of Pythonistas (Wijaya, Warsaw) (changelog) + PEP 8012: The Community Governance Model (Langa) (changelog) + PEP 8013: The External Council Governance Model (Dower) (changelog) + PEP 8014: The Commons Governance Model (Jansen) (changelog) + PEP 8015: Organization of the Python community (Stinner) (changelog) + PEP 8016: The Steering Council Model (Smith, Stufft) (changelog) + Further discussion + +Options:: [x] Private [ ] Make this a test poll: read all votes from a file. @@ -109,7 +177,7 @@ The following settings will be used for the vote in the CIVS system:: [ ] Allow voters to select “no opinion” for some choices. [ ] Enforce proportional representation -Which will have the effect of: +These options will have the effect of: * Making the election "private", or in other words, invite only. * The results of the election will be released to all voters.