We should get a confirmation from the Conduct WG that they're fine with the intermediate group being gotten rid of? If I'm remembering correctly, the conduct@pypa.io was set up since the PSF's Conduct WG wanted an intermediate group that served as the point of contact for reporting incidents -- a quick search on discuss.python.org brings up https://discuss.python.org/t/move-to-the-psf-code-of-conduct/3876/19 which indicates similarly. I'd like to avoid getting into a situation where we vote "yes" and the Conduct WG says "wait, no, that doesn't work for us". I'm not sure how many reports they deal with and how many reports the PyPA CoC responders have received but they might just say "OK, we'll handle those directly" -- but let's make sure. :) On Mon, Jun 6, 2022 at 8:36 PM Dustin Ingram <di@python.org> wrote:
The proposal will be put to a vote on the PyPA-Committers mailing list, over a 7-day period. Each PyPA committer can vote once, and can choose one of +1 and -1. If at least two thirds of recorded votes are +1, then the vote succeeds.
This vote will close on Monday, June 13 at 11AM ET.
On Mon, Jun 6, 2022 at 11:03 AM Bernat Gabor <gaborjbernat@gmail.com> wrote:
Seconded!
On Mon, 6 Jun 2022, 16:01 Dustin Ingram, <di@python.org> wrote:
In PEP 609 <https://peps.python.org/pep-0609/>, we moved the PyPA to use the PSF's Code of Conduct, but we left in place a PyPA-specific CoC team <https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md>.
I'd like to propose moving our reporting procedure to use the same procedure as the rest of the PSF <https://www.python.org/psf/conduct/>. 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" <https://peps.python.org/pep-0609/#updates-to-the-governance-specification-pr...>, 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!
-- You received this message because you are subscribed to the Google Groups "PyPA Code of Conduct Report" group. To unsubscribe from this group and stop receiving emails from it, send an email to conduct+unsubscribe@pypa.io.
-- You received this message because you are subscribed to the Google Groups "PyPA Code of Conduct Report" group. To unsubscribe from this group and stop receiving emails from it, send an email to conduct+unsubscribe@pypa.io.
_______________________________________________ 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: pradyunsg@gmail.com