You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Organizations on PyPI are self-managed teams, with their own exclusive branded web addresses. Our goal is to make PyPI easier to use for large community projects, organizations, or companies who manage multiple sub-teams and multiple packages. We’re making organizations available to community projects for free, forever, and to corporate projects for a small fee.
This should make things easier for us to maintain, improve bus factor, in addition to giving us the umbrella /org/python/ URL.
Greg said:
We should do this, but we need to not blindly put things in it on a whim because they exist elsewhere under that label. Our github organization has things in it that don’t belong there and only live there for historical reasons. We should be as narrow as our latest steering council decided policy or even narrower when adding things to a PyPI org.
Dear Steering Council,
Please could you come up with a policy for a https://pypi.org/org/python/ organisation on PyPI?
At PyCon US, PyPI announced their new organisation accounts:
Docs: https://docs.pypi.org/organization-accounts/
I suggested on Discourse that we ask for the (currently unassigned) https://pypi.org/org/python/ organisation, to use for packages maintained under the https://github.com/python GitHub organisation.
This should make things easier for us to maintain, improve bus factor, in addition to giving us the umbrella
/org/python/
URL.Greg said:
Sounds good; similar to the GitHub Organization Repository Policy, please could the Steering Council come up with a policy for the PyPI org?
The text was updated successfully, but these errors were encountered: