We do recommend sub-groups and fiscal sponsorees maintain their own CoC intermediary. We recommend continuing to maintain a PyPA-specific CoC team and using us as an advisory body.
Our group does not take any actions on our own but instead makes recommendations primarily to the PSF Board and the Python Steering Council.
If you have reports that you would like us to be aware of, please let us know and we’ll log it.
Also please feel free to use us as an advisory group: we don’t have the insight into your community that you do but it can be helpful to seek a second opinion from an outside observer.
(The vote closed on Monday, June 13 at 11AM ET. I'm still waiting to hear back from the Conduct WG about this.)On Tue, Jun 14, 2022, 6:22 AM Xavier Fernandez <xav.fernandez@gmail.com> wrote:+1_______________________________________________On Wed, 8 Jun 2022 at 11:23, Pradyun Gedam <pradyunsg@gmail.com> wrote:+1_______________________________________________On Mon, 6 Jun 2022, 20:36 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, 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!
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
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: xav.fernandez@gmail.com
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: di@python.org