Documentation build overview

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

  🔍 Preview build  

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

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

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. 😅

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.)

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