# Request "python" organisation on PyPI

**URL:** <https://discuss.python.org/t/request-python-organisation-on-pypi/26545>\
**Category:** Core Workflow\
**Tags:** PyPI\
**Created:** [May 5, 2023, 5:52pm UTC](https://discuss.python.org/t/request-python-organisation-on-pypi/26545 "2023-05-05T17:52:31Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [November 5, 2024, 7:39pm UTC](https://discuss.python.org/t/request-python-organisation-on-pypi/26545/10 "2024-11-05T19:39:49Z")

</div>

We now have the [pypi.org/org/cpython/](https://pypi.org/org/cpython/) and [pypi.org/org/python/](https://pypi.org/org/python/) organisations 🎉

As PyPI organisations are very new to us, let’s start small so we can gain experience as we go along, especially around the various roles; see the [matrix in the docs](https://docs.pypi.org/organization-accounts/roles-entities/). Ideas welcome on this.

Right now, Ee and I have the owner role for both orgs. Perhaps we can create a team for each project and add interested core team members as maintainers or owners. Although we’re already using Trusted Publishers which takes care of uploading for us.

I suggest starting with moving one of `blurb`, `cherry-picker` or `python-docs-theme` into the `cpython` org. I’ll open an issue in the relevant repo.

---

_[View the full topic](https://discuss.python.org/t/request-python-organisation-on-pypi/26545)._