# Be aware: Python packaging governance discussion

**URL:** <https://forum.djangoproject.com/t/be-aware-python-packaging-governance-discussion/38756>\
**Category:** Django Internals\
**Created:** [February 11, 2025, 7:01am UTC](https://forum.djangoproject.com/t/be-aware-python-packaging-governance-discussion/38756 "2025-02-11T07:01:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ubernostrum](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/ubernostrum/32/54_2.png) [@ubernostrum](https://forum.djangoproject.com/u/ubernostrum)\
**Post date:** [February 11, 2025, 7:01am UTC](https://forum.djangoproject.com/t/be-aware-python-packaging-governance-discussion/38756/1 "2025-02-11T07:01:01Z")

</div>

[PEP 772](https://peps.python.org/pep-0772/) ([Python forum thread](https://discuss.python.org/t/pep-772-packaging-governance-process/79724)) is currently under discussion, and aims to formalize governance of the Python packaging ecosystem. A brief summary is that it proposes creating a “Packaging Council” which will govern Python packaging standards and likely have some delegated authority over packaging PEPs, and the Packaging Council will be elected by a “Packaging Community”.

This is relevant to Django because the “Packaging Community”, in addition to existing members of the Python Packaging Working Group and PyPA, is expected to accept nominations from major entities in the ecosystem, and Django is specifically named as one of the entities which would be asked to nominate members to the “Packaging Community” (see [relevant PEP section](https://peps.python.org/pep-0772/#initial-membership)).

It would probably be a good idea for the Django project to start thinking over who it would like to nominate for that, if this all goes through as expected. Or even who would make the call – would it be the [@steering\_council](https://forum.djangoproject.com/groups/steering_council) ? The Django Releasers? Someone else?

---

<div class="post-metadata">

**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/carltongibson/32/267_2.png) [@carltongibson](https://forum.djangoproject.com/u/carltongibson)\
**Post date:** [February 11, 2025, 7:03am UTC](https://forum.djangoproject.com/t/be-aware-python-packaging-governance-discussion/38756/2 "2025-02-11T07:03:31Z")

</div>

Thanks for sharing this @ubernostrum 👍

---

<div class="post-metadata">

**Author:** ![nanorepublica](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/nanorepublica/32/14211_2.png) [@nanorepublica](https://forum.djangoproject.com/u/nanorepublica)\
**Post date:** [February 11, 2025, 7:43am UTC](https://forum.djangoproject.com/t/be-aware-python-packaging-governance-discussion/38756/3 "2025-02-11T07:43:28Z")

</div>

Going to cross post this PR from the DSF working groups as this would likely contain relevant community members.

> <https://github.com/django/dsf-working-groups/pull/19>
>
> \> This group supports package maintainers in the Django ecosystem.
> 
> Now ready …for public feedback. And we need more group members for this viable, including a Chair and Co-Chair :) If anyone’s interested please review and comment here!
> 
> For anyone reviewing this, here are relevant discussion threads this proposal is based on:
> 
> \- \[We need more roadies in jazzband\](https://github.com/jazzband/help/issues/196)
> \- \[Moving REST framework forward\](https://github.com/encode/django-rest-framework/discussions/9270)
> 
> Additionally this is based on my experience of community-driven package maintenance with \[@wagtail\](https://github.com/wagtail) and \[@wagtail-nest\](https://github.com/wagtail-nest), plans to create a \[Wagtail packaging team\](https://github.com/wagtail/wagtail/wiki/Packaging-Team), and discussions about \[Django Commons\](https://github.com/django-commons) with @tim-schilling. Thank you Tim for the early feedback!