Implementing PEP 609: PyPA Governance

Hurray! We have formalized the governance of the PyPA. :tada:

I think our next steps would be to actually implement the changes the PEP outlines:

  1. Adopt PSF CoC on all the PyPA projects (and drop the PyPA CoC), using the files that GitHub recognises.
  2. Get the pypa-committers mailing list up-to-date (and a way to maintain this?)
  3. Work with the SC on the PEP process-related changes
    • Determine a list of “who from PyPA can be a PEP sponsor” – this needs a dedicated discussion, and a committer vote IMO (so blocked on 2. above)
    • Get clarity on the process for changing PEP 0 for namespacing.
    • Get clarity on how to provide list of “PyPA sponsors” to the SC / PEP editors.

@EWDurbin any thoughts on how to make 2. happen?

3 Likes

This can be done by putting (for example) CODE_OF_CONDUCT.md in an organisation-wide https://github.com/pypa/.github repo, so it doesn’t need to be added individually to all project repos.

2 Likes

I created https://github.com/pypa/.github/ as well as https://github.com/pypa/.github/pull/1/ to add the PSF CoC.

1 Like

For #1, I’ve merged https://github.com/pypa/.github/pull/1, I think next steps would be removing the PyPA CoC from http://github.com/pypa/ repos – @hugovk perhaps you’d be interested in doing that?

For #2, I’ll work on setting up this list.

Sure, something like https://github.com/pypa/get-pip/pull/70/?

The existing link is to https://www.pypa.io/en/latest/code-of-conduct/, which says:

All PyPA contributors and maintainers are expected to follow the PSF Code of Conduct. Please see PyPA-specific details.

(PyPA previously had its own code of conduct separate from PSF’s; PEP 609 switched PyPA to PSF’s Code of Conduct.)

Is that existing link okay, or would it better going direct to https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md or elsewhere?

On that PR, @pradyunsg suggested linking directly to https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md because it skips needing to click through an extra link to get to the relevant reporting details, so I’ll go for that one. :+1:

Edit: There we go! That should be the lot:

  1. https://github.com/pypa/get-pip/pull/68
  2. https://github.com/pypa/virtualenv/pull/1911
  3. https://github.com/pypa/pip/pull/8651
  4. https://github.com/pypa/pypa.io/pull/59
  5. https://github.com/pypa/warehouse/pull/8338
  6. https://github.com/pypa/manylinux/pull/690
  7. https://github.com/pypa/packaging.python.org/pull/760
  8. https://github.com/pypa/setuptools/pull/2291
  9. https://github.com/pypa/twine/pull/680
  10. https://github.com/pypa/auditwheel/pull/256
  11. https://github.com/pypa/pipenv/pull/4405
  12. https://github.com/pypa/packaging/pull/326
  13. https://github.com/pypa/pipfile/pull/129
  14. https://github.com/pypa/pypi-support/pull/519
  15. https://github.com/pypa/wheel/pull/361
  16. https://github.com/pypa/setuptools_scm/pull/466
  17. https://github.com/pypa/python-manylinux-demo/pull/27
  18. https://github.com/pypa/readme_renderer/pull/171
  19. https://github.com/pypa/linehaul/pull/53
  20. https://github.com/pypa/interoperability-peps/pull/73
  21. https://github.com/pypa/forklift/pull/2
  22. https://github.com/pypa/wheel-builders/pull/4
1 Like

Hurray! Thanks a lot for doing this @hugovk! ^.^

1 Like

Because Discourse is nice, I’ve added a checklist to the first-post here, and checked off the first box. :slight_smile:

1 Like