Skip to content

PPC: add the packaging-council repository - #1909

Draft
henryiii wants to merge 3 commits into
python:mainfrom
henryiii:patch-1
Draft

henryiii wants to merge 3 commits into
python:mainfrom
henryiii:patch-1

Conversation

@henryiii

@henryiii henryiii commented Sep 18, 2026

Copy link
Copy Markdown

This is the repository for the PPC (Python Packaging Council) we are preparing.

Currently in draft until this repo has something in it and is made public.

Should the typing-council repo be mentioned here too?

This is the repository for the PPC being prepared.
@read-the-docs-community

read-the-docs-community Bot commented Sep 18, 2026

Copy link
Copy Markdown

Documentation build overview

📚 CPython devguide | 🛠️ Build #34651489 | 📁 Comparing 9970cc1 against latest (f4a4d46)

  🔍 Preview build  

2 files changed
± genindex/index.html
± developer-workflow/development-cycle/index.html

@JelleZijlstra

Copy link
Copy Markdown
Member

This is a "for example" list, I don't think it needs to include all repos.

@hugovk

hugovk commented Sep 19, 2026

Copy link
Copy Markdown
Member

I agree it doesn't need adding to the example list.

Let's instead add it to this governance table:

https://devguide.python.org/developer-workflow/development-cycle/#governance

And see the policy for adding new repos to the GitHub org:

https://devguide.python.org/developer-workflow/development-cycle/#organization-repository-policy

@pradyunsg

pradyunsg commented Sep 19, 2026

Copy link
Copy Markdown
Member

And see the policy for adding new repos to the GitHub org:

https://devguide.python.org/developer-workflow/development-cycle/#organization-repository-policy

I'm reading this as an ask to follow the process quoted below.

Before adding a new repository to the organization, open a discussion to seek consensus in the Committers Discourse category. Once people are satisfied with that, ask the Python steering council to grant permission.

I think we'd be happy to (it'd be a bit surprising if anyone says no!) but just want to confirm that I'm not misreading. 😅

@hugovk

hugovk commented Sep 19, 2026

Copy link
Copy Markdown
Member

Yes, I suggest to follow the process, and expect it to be a quick yes.

I think the SC came up with this policy because:

Note that several repositories remain in the organization for historic reasons, and would probably not be appropriate to add today.

And we'd like to avoid repeating that. So let's follow it for the (hopefully!) clear cases. (Also it gives visibility to the process, which has been skipped recently in less clear cases.)

@pradyunsg

Copy link
Copy Markdown
Member

https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135

Signed-off-by: Henry Schreiner <henryfs@princeton.edu>
Comment thread developer-workflow/development-cycle.rst
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