PEP 772: Packaging governance process

[pradyunsg]

Basic requirements (all PEP Types)

• Read and followed PEP 1 & PEP 12
• File created from the latest PEP template
• PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
• Title clearly, accurately and concisely describes the content in 79 characters or less
• Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
• Author, Status (Draft), Type and Created headers filled out correctly
• PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
• Required sections included
  • Abstract (first section)
  • Copyright (last section; exact wording from template required)
• Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
• PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
• Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

• PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
• Suggested sections included (unless not applicable)
  • Motivation
  • Rationale
  • Specification
  • Backwards Compatibility
  • Security Implications
  • How to Teach This
  • Reference Implementation
  • Rejected Ideas
  • Open Issues
• Python-Version set to valid (pre-beta) future Python version, if relevant
• Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
• Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

---

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

[warsaw]

I thought we would put this in PEP 8800 (or other 8X00 range) to rhyme with the Steering Council PEPs in the 8100s?

[willingc]

Overall, nice work on this PEP. I'm happy to see it moving forward. I've made some comments based on my governance experience. YMMV.

[hugovk]

I thought we would put this in PEP 8800 (or other 8X00 range) to rhyme with the Steering Council PEPs in the 8100s?

Hmm, no objection, although this is replacing 609, and the other recent council/WG/board PEPs didn't go in 8xxx:

	PEP	Title	Authors
PA	609	Python Packaging Authority (PyPA) Governance	Dustin Ingram, Pradyun Gedam, Sumana Harihareswara
PA	729	Typing governance process	Jelle Zijlstra, Shantanu Jain
PA	731	C API Working Group Charter	Guido van Rossum, Petr Viktorin, Victor Stinner, Steve Dower, Irit Katriel
PA	732	The Python Documentation Editorial Board	Joanna Jablonski

https://peps.python.org/topic/governance/

[pradyunsg]

Thanks everyone for the reviews here!

Given that there's over a hundred comments on this PR already... I have a couple of "housekeeping"-style requests:

• I'd appreciate if we avoid extended discussion outside of inline review comments.
  • Replies outside of inline "review comments" are much easier to lose track of when the discussion gets really long with reviews from multiple individuals (which is what is going on here, right now).
  • I'm marking things as resolved to close out relevant subtopics in our discussions here.
• If I've marked one of your comments as resolved and haven't actually addressed it (and it wasn't a nit pick), please feel welcome mark it as unresolved and add a reply there!

There's still more stuff to be addressed from these reviews... I'll come around to those in my next burst of addressing review comments here (it's late today).

[hugovk]

I think my suggestions have been addressed. Thanks for working on this!

[willingc]

I'm good with where things stand right now. Thanks @warsaw and @pradyunsg for moving this forward.

[warsaw]

Thanks @willingc ; I'm going to get the last few things resolved and get this PEP published.