# Adding a python/packaging-council and (possibly) moving packaging.python.org

**URL:** <https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135>\
**Category:** Committers\
**Created:** [September 19, 2026, 8:33am UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135 "2026-09-19T08:33:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pradyunsg](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pradyunsg/32/206_2.png) [@pradyunsg](https://discuss.python.org/u/pradyunsg)\
**Post date:** [September 19, 2026, 8:33am UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135/1 "2026-09-19T08:33:23Z")

</div>

Hi folks!

The inaugural PPC met yesterday, and we’re thinking of:

- Creating a python/packaging-council repository.
- Adding all PPC members to the org, in a team with write (or greater) permissions on the repository.
- Possibly, in the future, moving [packaging.python.org](http://packaging.python.org) under the python org – this needs some more time + discussions before it’ll happen tho.

Making a thread here, as per [Development cycle](https://devguide.python.org/developer-workflow/development-cycle/#organization-repository-policy). I’m hoping this is going to be a quick and easy one to get concensus on!

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [September 19, 2026, 3:06pm UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135/2 "2026-09-19T15:06:41Z")

</div>

Do you also want your own Discourse top-level channel?

---

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [September 19, 2026, 3:26pm UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135/3 "2026-09-19T15:26:36Z")

</div>

#Packaging works well enough for us for now. But if that changes I can easily take care of that.

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [September 21, 2026, 8:25pm UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135/4 "2026-09-21T20:25:36Z")

</div>

> [@pradyunsg](#):
>
> - Adding all PPC members to the org, in a team with write (or greater) permissions on the repository.

Greater permissions than write sounds sensible: we’ve elected you into positions of trust, you should be able to independently administer your repo without hassle, and it’s tied to a team that will be updated after each election.

---

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [September 24, 2026, 8:22pm UTC](https://discuss.python.org/t/adding-a-python-packaging-council-and-possibly-moving-packaging-python-org/109135/5 "2026-09-24T20:22:17Z")

</div>

I opened a SC ticket so they can rubber-stamp this on today’s meeting (if they want to): [`python/packaging-council` repo · Issue #364 · python/steering-council · GitHub](https://github.com/python/steering-council/issues/364)