+1
In PEP 609, we moved the PyPA to use the PSF's Code of Conduct, but we left in place a PyPA-specific CoC team.
I'd like to propose moving our reporting procedure to use the same procedure as the rest of the PSF. Practically this means that we'd dreprecate the conduct@pypa.io alias and reports would go right to conduct-wg@python.org instead.
A few advantages:
- The PyPA is not a 'special case' for PSF projects when it comes to CoCs
- The CoC team would include unbiased members that aren't part of the PyPA
- Better response time, and more experience around response procedure, etc.
Given that PEP 609 doesn't actually talk about the conduct@pypa.io intermediary, this might not be considered an "Update to the Governance/Specification Processes", but I'd like to propose a vote on this anyway.
Reminder that a PyPA committer vote is triggered when a PyPA committer (not the proposer) seconds the proposal.
Thanks!
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3/lists/pypa-committers.python.org/ Member address: opensource@ronnypfannschmidt.de