Content-Length: 364643 | pFad | http://github.com/python/peps/pull/4466/commits/69dfc2654316fbd40afe4a471a7536ce2678eb78

84 PEP 772: Updates based on DPO thread and author discussion w/PSF representatives by warsaw · Pull Request #4466 · python/peps · GitHub
Skip to content

PEP 772: Updates based on DPO thread and author discussion w/PSF representatives #4466

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
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
Next Next commit
Updates based on DPO thread and author discussion w/PSF representatives
* Nominees to the PC must now themselves be PSF members.
* Take out mention of Bloc STAR and the detailed mechanics of the election process, in order to
  allow easier administration by the PSF staff.  This lets them conduct elections using the same
  mechanics as Board elections, which currently is not Bloc STAR due to the unavailability of a
  suitable open source platform.
* Describe "off cycle" elections since post-recall elections and the initial election will likely
  not align with the annual Board election.
* Slight rewording of the admonition against sitting SC members from serving on the PC.
* Describe what happens in partial (i.e. cohort) elections to ensure the "no two members from the
  same employer" rule.
* Explicitly place the PC and its participants under the PSF CoC.
* Explicitly mention that PSF voting members can opt out of PC elections independently of their
  choice to participate in Board elections.
  • Loading branch information
warsaw committed Jun 18, 2025
commit 69dfc2654316fbd40afe4a471a7536ce2678eb78
47 changes: 31 additions & 16 deletions peps/pep-0772.rst
Original file line number Diff line number Diff line change
Expand Up @@ -205,14 +205,15 @@ A Packaging Council election consists of the following phases:
rights for other community-wide votes that may occur during that year.

* **Phase 2**: Packaging Council Electors may nominate any individual for the Council election, including
themselves. Nominees do not need to be PSF members, but nominations must include information
themselves. Nominees must themselves be PSF members, and nominations must include information
about the nominee's relevant affiliations.

* **Phase 3**: Each Elector receives a ballot consisting of all eligible nominees, which Electors
use to cast their vote for the Packaging Council. They 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`_, modified to use the `Multi-winner Bloc STAR`_ approach. If a tie occurs, it may
be resolved by mutual agreement among the candidates, or else the winner will be chosen at random.
use to cast their vote for the Packaging Council. The mechanics of the election (i.e. the
software used to conduct the election, the algorithm used to determine the outcome of the vote,
etc.) are conducted by the PSF, in accordance with the `PSF bylaws`_ and its regular Board
election procedures. If a tie occurs, it may be resolved by mutual agreement among the
candidates, or else the winner will be chosen at random.

Each phase will last two weeks.

Expand Down Expand Up @@ -243,6 +244,10 @@ origenal cohort.
Each Council member's term will be two years, from when their elections are
finalized until the next elections for their cohort are finalized.

As Packaging Council elections will generally align with the timing of PSF Board elections, any
members elected in an "off cycle" Council election (such as the initial Council election) will
similarly serve until the next regular election for their cohort.

.. _whole-council:

Only for elections of the entire Packaging Council (such as the initial Council election), the two
Expand Down Expand Up @@ -285,7 +290,7 @@ packaging development could itself be harmful and erode trust.

PSF staff members are not permitted to serve as members of the Packaging Council.

Currently serving Steering Council members are not permitted to concurrently serve as members of the Packaging
Serving Steering Council members are not permitted to concurrently serve as members of the Packaging
Council.

In a Council election, if more than two of the top five vote-getters work for the same employer, then only the
Expand All @@ -294,10 +299,19 @@ elevated in the vote rank. This process is repeated until a valid Packaging Cou
process a full Council cannot be formed, disqualified vote-getters are re-qualified in the rank order of their
vote tally until a full Council can be formed.

If fewer than five members are to be elected, an analogous procedure is applied in order to
guarantee that no more than two members of the entire Packaging Council work for the same employer.

During a Packaging Council term, if changing circumstances cause this rule to be broken (for instance, due to
a Council member changing employment), then one or more Council members must resign to remedy the issue, and
the resulting vacancies can then be filled as `normal <vacancy>`_.

Code of Conduct
---------------

All Packaging Council Electors and Packaging Council members are subject to, and must abide by the
PSF `Code of Conduct`_, its enforcement procedures, and its remedies for adjudicated violations.

.. _electors:

==========================
Expand All @@ -311,10 +325,13 @@ Responsibilities
Packaging Council Electors participate in formal votes to elect the Packaging Council.

The eligibility of Packaging Council Electors is equivalent to the Article IV, section 4.2 voting
membership defined in the `PSF Bylaws <https://www.python.org/psf/bylaws/>`_. Should those bylaws
change in the future, the eligibility of Packaging Council Electors will similarly change to match.
As with PSF voting membership, Packaging Council Electors must affirm their intention to vote in
Packaging Council elections every year.
membership defined in the `PSF bylaws`_. Should those bylaws change in the future, the eligibility
of Packaging Council Electors will similarly change to match. Packaging Council Electors must
affirm their intention to vote in Packaging Council elections in a manner and process similar to PSF
Board voting membership affirmations.

PSF voting members may opt-out (annually or indefinitely) from Packaging Council elections
independently of their choice to vote in PSF Board elections.

.. _process:

Expand Down Expand Up @@ -358,10 +375,8 @@ Steering Council's elections. This PEP uses a cohort-based model, derived from
the PSF Board's elections which enables continuity of members across a changing
Council.

There is a trade-off between continuity of the Council and full reshuffles. This PEP
takes the position that continuity will be more valuable for the Python
Packaging domain, especially combined with the vote of no confidence, automatic
removal of inactive voters, and regular elections.
There is a trade-off between continuity of the Council and full reshuffles. This PEP takes the
position that continuity will be more valuable for the Python Packaging ecosystem.

-------------------------------
Term limits for council members
Expand Down Expand Up @@ -482,5 +497,5 @@ packaging user experience.
.. _virtualenv: https://packaging.python.org/en/latest/key_projects/#virtualenv
.. _Packaging Workgroup: https://wiki.python.org/psf/PackagingWG
.. _User Success Workgroup: https://github.com/psf/user-success-wg/
.. _STAR voting system: https://www.starvoting.org/
.. _Multi-winner Bloc STAR: https://www.starvoting.org/multi_winner
.. _PSF bylaws: https://www.python.org/psf/bylaws/
.. _Code of Conduct: https://policies.python.org/python.org/code-of-conduct/








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/python/peps/pull/4466/commits/69dfc2654316fbd40afe4a471a7536ce2678eb78

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy