Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 13: Add STAR voting and misc tidbits #3958

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions peps/pep-0013.rst
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,11 @@ A council election consists of two phases:
must be nominated by a core team member. Self-nominations are
allowed.

* Phase 2: Each core team member can vote for zero or more of the
candidates. Voting is performed anonymously. Candidates are ranked
by the total number of votes they receive. If a tie occurs, it may
* Phase 2: Each core team member can assign zero to five stars to each
candidate. Voting is performed anonymously. The outcome of the vote
is determined using the `STAR voting system <https://www.starvoting.org/>`__,
modified to use the `Multi-winner Bloc STAR <https://www.starvoting.org/multi_winner>`__)
approach. If a tie occurs, it may
be resolved by mutual agreement among the candidates, or else the
winner will be chosen at random.

Expand Down Expand Up @@ -270,6 +272,10 @@ It is granted by receiving at least two-thirds positive votes in a
core team vote that is open for one week and is not vetoed by the
steering council.

.. note:: The devguide has a `suggested template
<https://devguide.python.org/core-developers/become-core-developer/#poll-template>`__
to use for such votes.

Core team members are always looking for promising contributors,
teaching them how the project is managed, and submitting their names
to the core team's vote when they're ready.
Expand Down Expand Up @@ -301,6 +307,10 @@ Changing this document
Changes to this document require at least a two-thirds majority of
votes cast in a core team vote which should be open for two weeks.

No vote is required to update note blocks and the "Current steering
council" and "History of council elections" sections with current
information.


History
=======
Expand Down Expand Up @@ -343,6 +353,7 @@ History of amendments
---------------------

2019-04-17: Added the vote length for core devs and changes to this document.
2024-XX-XX: Adopted Multi-winner Bloc STAR voting for council elections.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remember to fill in the actual date the PR was approved by a Discord poll (or some other significant date, maybe just the date the PR is merged).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@AA-Turner AA-Turner Oct 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This suggestion uses a footnote -- I couldn't think of a nice way to incorporate the link other than linking the whole line or having a '(link)' trailer, which we try to avoid.

Suggested change
2024-XX-XX: Adopted Multi-winner Bloc STAR voting for council elections.
2024-10-09: Adopted Multi-winner Bloc STAR voting for council elections. [1]_
.. [1] https://discuss.python.org/t/64971

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the PEP metadata, the dates in post-history are links to changesets, so the date could be made a link here too, unless you think it’s not intuitive.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's more appropriate for this to link to the vote that approved the change. The changeset/PR can easily be retrieved using GitHub or git blame; there's no easy wat to find the voting thread without explicitly linking it here.




Expand Down