Skip to content

PEP 772: Updates based on conversations at PyCon #4429

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

Merged
merged 23 commits into from
May 30, 2025

Conversation

warsaw
Copy link
Member

@warsaw warsaw commented May 20, 2025

  • Align PPC Electors with PSF voting members as described in the PSF bylaws. Rather than the previous categories, this approach is generally deemed to be both equitable and workable.
  • Update the mechanics and timeline of PPC elections, into three phases: self-selection of Electors, nominations of Council members, voting
  • Remove the language around initial membership and adding a new member, as these are no longer necessary.
  • Add language about the call for deanonymization of ballots in cases where foul play is suspected.
  • Clarify the PSC's role in approving changes to this PEP, and responsibilities in certain corner cases of the election process.
  • Explicitly disallow PSC members from concurrently serving on the PPC.
  • Clarify language around the expectation of the PSC and PSF to adjust existing standing delegations
  • Unify language around "Packaging Council Electors" rather than "voting members"
  • Added an acknowledgments section
  • Various spelling, grammar, and wording fixes

📚 Documentation preview 📚: https://pep-previews--4429.org.readthedocs.build/pep-0772/

* Align PPC Electors with PSF voting members as described in the PSF bylaws.  Rather than the previous
  categories, this approach is generally deemed to be both equitable and workable.
* Update the mechanics and timeline of PPC elections, into three phases: self-selection of Electors,
  nominations of Council members, voting
* Remove the language around initial membership and adding a new member, as these are no longer necessary.
* Add language about the call for deanonymization of ballots in cases where foul play is suspected.
* Clarify the PSC's role in approving changes to this PEP, and responsibilities in certain corner cases of the
  election process.
* Explicitly disallow PSC members from concurrently serving on the PPC.
* Clarify language around the expectation of the PSC and PSF to adjust existing standing delegations
* Unify language around "Packaging Council Electors" rather than "voting members"
* Added an acknowledgments section
* Various spelling, grammar, and wording fixes
@warsaw warsaw requested a review from pradyunsg as a code owner May 20, 2025 15:19
@warsaw
Copy link
Member Author

warsaw commented May 20, 2025

@pradyunsg @geofft (seems I can't tag Deb). Here's an update that I think captures everything we've been talking about. I'll share with Deb for her approval via Slack.

@hugovk
Copy link
Member

hugovk commented May 20, 2025

(seems I can't tag Deb)

cc @eximious

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

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

The modified paragraphs have been wrapped to ~110 chars, could you rewrap to ~80?

warsaw and others added 3 commits May 20, 2025 10:42
Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
Copy link
Contributor

@geofft geofft left a comment

Choose a reason for hiding this comment

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

Thanks for putting this together, Barry! This looks good with regard to the conversations we had

Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

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

Overall, a much improved document. I've left some comments largely related to simplifying language for better clarity.

warsaw and others added 7 commits May 21, 2025 12:54
Co-authored-by: Geoffrey Thomas <[email protected]>
Co-authored-by: Geoffrey Thomas <[email protected]>
Co-authored-by: Geoffrey Thomas <[email protected]>
Co-authored-by: Geoffrey Thomas <[email protected]>
Co-authored-by: Carol Willing <[email protected]>
Co-authored-by: Carol Willing <[email protected]>
@warsaw
Copy link
Member Author

warsaw commented May 21, 2025

I pushed an update and resolved as much of the conversation as I could, but some of the threads were difficult! Anyway, I'll take another pass through this after a bit, but PTAL.

Copy link
Contributor

@geofft geofft left a comment

Choose a reason for hiding this comment

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

LGTM! Unresolved threads I still see:

  • Carol had a rephrasing for the paragraph starting "Only for elections" that I like.
  • Carol and I had a brief discussion about term limits, but it might be best to hash that out separate from this PR.

@AA-Turner AA-Turner self-requested a review May 22, 2025 05:15
@warsaw
Copy link
Member Author

warsaw commented May 23, 2025

I'm actually going to also change the title of the PEP to: "Packaging Council governance process". I think that'll make it easier to search for both on the interwebs and within the PEP index.

warsaw added 2 commits May 22, 2025 20:36
@warsaw
Copy link
Member Author

warsaw commented May 23, 2025

Carol had a rephrasing for the paragraph starting "Only for elections" that I like.

I can't seem to find this thread any more. @willingc can you comment here and/or check that the current revision of the PEP doesn't address your suggestion?

Carol and I had a brief discussion about term limits, but it might be best to hash that out separate from this PR.

Happy to. I am of mixed feelings about term limits in general and as they would apply here, but would love to hear your thoughts!

Copy link
Contributor

@geofft geofft left a comment

Choose a reason for hiding this comment

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

LGTM, continued thanks for your work on this.

Carol's suggestion was to change:

Only for elections involving the entire Packaging Council (such as the initial Council election),

to

If an election must elect the entire Packaging Council, such as the initial Council election,

Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

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

@warsaw Thanks! I'm good with these changes.

@geofft
Copy link
Contributor

geofft commented May 26, 2025

I went down a mild Wikipedia rabbit hole and ended up on their page about electing admins. The community at large (roughly, anyone with an account in good standing) can vote, so this seems potentially relevant for us.

One thing I learned: the "scrutineers" of the election have powers to see (what they call) PII about the voters, namely the IP address and User-Agent and X-Forwarded-For headers used in casting the vote, in addition to the account name and timestamp. On Wikipedia, a small group of (volunteer) users already have an similar power to investigate regular editing actions, called checkuser, when accounts are suspected of being "sockpuppets" (undisclosed duplicates). The elections procedure involves picking three people who already have checkuser rights as election scrutineers. Note that I don't think that scrutineers can see how people actually voted.

The current draft in this PR gives broad leeway to the Returns Officer as to how to conduct the election, so I don't think we need to change anything in the text itself, but I just wanted to note that it seems like a good implementation choice to retain this information in the software and have it be an option for the Steering Council to request this info (to be released to either themselves or their designee) during certification, if there's a suspicion that something went wrong.

@warsaw
Copy link
Member Author

warsaw commented May 28, 2025

LGTM, continued thanks for your work on this.

Carol's suggestion was to change:

Only for elections involving the entire Packaging Council (such as the initial Council election),

to

If an election must elect the entire Packaging Council, such as the initial Council election,

I think I'll change it to:

Only for elections of the entire Packaging Council (such as the initial Council election)

warsaw added 2 commits May 28, 2025 13:45
* Slight wording changes in Phase 1 regarding ballot requests
* Elaborate in Phase 3 about receiving a ballot
* Small wording change around full-Council elections
@warsaw
Copy link
Member Author

warsaw commented May 29, 2025

Just waiting for a final review from @pradyunsg and @eximious

@warsaw
Copy link
Member Author

warsaw commented May 30, 2025

Thanks all! I got out-of-band LGTMs from Deb and Pradyun, with one small change, now pushed. I will merge, publish, and post once CI completes.

@warsaw warsaw merged commit 44dc1a5 into python:main May 30, 2025
5 checks passed
@warsaw warsaw deleted the warsaw/pep-772 branch May 30, 2025 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants