# Notes from Python Packaging Council's first meeting

**URL:** https://discuss.python.org/t/notes-from-python-packaging-councils-first-meeting/109203
**Category:** Packaging
**Created:** [September 23, 2026, 11:38pm UTC](https://discuss.python.org/t/notes-from-python-packaging-councils-first-meeting/109203 "2026-09-23T23:38:09Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![barry](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/barry/32/42_2.png) [@barry](https://discuss.python.org/u/barry)
#### Post date: [September 24, 2026, 6:46pm UTC](https://discuss.python.org/t/notes-from-python-packaging-councils-first-meeting/109203/9 "2026-09-24T18:46:58Z")

</div>

> [@Jelle](#):
>
> But there’s no corresponding provision for the Packaging Council. Conversely, we haven’t actually given Typing Council members commit access to the peps repo. It looks like one PEP was sponsored by a non-core dev Typing Council member (PEP 764, by Eric Traut), but I was added as a code owner instead.
> 
> It seems reasonable to me to give the members of the Packaging Council commit access to the peps repo; I’m comfortable making that call as a PEP editor. Changing PEP 1 to pre-approve Packaging Council members as sponsors also seems reasonable but needs Steering Council approval.

I agree about pre-approving PPC members as sponsors, and I’ve put that question on the SC’s agenda.

What’s holding up giving PTC members commit to the peps repo?

---

_[View the full topic](https://discuss.python.org/t/notes-from-python-packaging-councils-first-meeting/109203)._