Moving the PyPA to use the PSF's CoC reporting procedures
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!
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.
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.
+1 On Monday, 6 June 2022 at 16:07:16 BST, 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: vinay_sajip@yahoo.co.uk
+1 Sent from my phone with my typo-happy thumbs. Please excuse my brevity On Mon, Jun 6, 2022, 11:51 Vinay Sajip via PyPA-Committers < pypa-committers@python.org> wrote:
+1
On Monday, 6 June 2022 at 16:07:16 BST, 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: vinay_sajip@yahoo.co.uk _______________________________________________ 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: graffatcolmingov@gmail.com
+1 On 6/6/2022 1:14:02 PM, Ian Stapleton Cordasco <graffatcolmingov@gmail.com> wrote: +1 Sent from my phone with my typo-happy thumbs. Please excuse my brevity On Mon, Jun 6, 2022, 11:51 Vinay Sajip via PyPA-Committers <pypa-committers@python.org [mailto:pypa-committers@python.org]> wrote: +1 On Monday, 6 June 2022 at 16:07:16 BST, Dustin Ingram <di@python.org [mailto: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 [mailto:gaborjbernat@gmail.com]> wrote: Seconded! On Mon, 6 Jun 2022, 16:01 Dustin Ingram, <di@python.org [mailto: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 [mailto:conduct@pypa.io] alias and reports would go right to conduct-wg@python.org [mailto: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 [mailto: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 [mailto: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 [mailto:conduct+unsubscribe@pypa.io]. _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org [mailto:pypa-committers@python.org] To unsubscribe send an email to pypa-committers-leave@python.org [mailto:pypa-committers-leave@python.org] https://mail.python.org/mailman3/lists/pypa-committers.python.org/ [https://mail.python.org/mailman3/lists/pypa-committers.python.org/] Member address: vinay_sajip@yahoo.co.uk [mailto:vinay_sajip@yahoo.co.uk] _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org [mailto:pypa-committers@python.org] To unsubscribe send an email to pypa-committers-leave@python.org [mailto:pypa-committers-leave@python.org] https://mail.python.org/mailman3/lists/pypa-committers.python.org/ [https://mail.python.org/mailman3/lists/pypa-committers.python.org/] Member address: graffatcolmingov@gmail.com [mailto:graffatcolmingov@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: donald@stufft.io [2461186c-67e3-4f12-995b-4b5ae87d909c]
+1 On Mon, Jun 6, 2022 at 09:06 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: nate.prewitt@gmail.com
+1 from me On Mon, 6 Jun 2022 at 16:06, 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: p.f.moore@gmail.com
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
Thanks Pradyun, that's a good find and you're right. I'll follow up with them, let's consider this vote a plan to do this if and only if they support it. On Mon, Jun 6, 2022, 9:02 PM Pradyun Gedam <pradyunsg@gmail.com> wrote:
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
-- 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.
Awesome, thanks for volunteering to do this! On Tue, 7 Jun 2022, 06:37 Dustin Ingram, <di@python.org> wrote:
Thanks Pradyun, that's a good find and you're right. I'll follow up with them, let's consider this vote a plan to do this if and only if they support it.
On Mon, Jun 6, 2022, 9:02 PM Pradyun Gedam <pradyunsg@gmail.com> wrote:
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
-- 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.
+1 Dustin Ingram kirjoitti 6.6.2022 klo 18.06:
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 topypa-committers-leave@python.org https://mail.python.org/mailman3/lists/pypa-committers.python.org/ Member address:alex.gronholm@nextday.fi
+1 On Mon, Jun 6, 2022 at 5:06 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: stephane.bidoul@acsone.eu
+1 -- Matthias On Tue, 7 Jun 2022 at 23:19, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
+1
On Mon, Jun 6, 2022 at 5:06 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, 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: stephane.bidoul@acsone.eu
_______________________________________________ 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: bussonniermatthias@gmail.com
+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 <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
+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 <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
_______________________________________________ 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
(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 <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
_______________________________________________ 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
Here's the response from the Conduct WG: 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.
Given this, we should probably not make the proposed changes here, but I'd very much like to add some additional volunteers to our CoC group. PEP 609 says:
each project that is a part of the PyPA organization must designate at least one PyPA member as available to contact in case of a Code of Conduct incident.
And right now, this definitely isn't the case. On Tue, Jun 14, 2022 at 7:10 AM Dustin Ingram <di@python.org> wrote:
(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 <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
_______________________________________________ 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
+1
On Jun 6, 2022, at 8:01 AM, 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 <mailto:conduct@pypa.io> alias and reports would go right to conduct-wg@python.org <mailto: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 <mailto: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! _______________________________________________ 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: me@cooperlees.com
On Mon, 2022-06-06 at 11:01 -0400, Dustin Ingram 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! _______________________________________________ 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: lains@riseup.net
+1 Cheers, Filipe Laíns
+1 Am 06.06.22 um 17:01 schrieb Dustin Ingram:
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!
_______________________________________________ PyPA-Committers mailing list --pypa-committers@python.org To unsubscribe send an email topypa-committers-leave@python.org https://mail.python.org/mailman3/lists/pypa-committers.python.org/ Member address:opensource@ronnypfannschmidt.de
participants (16)
-
Alex Grönholm -
Bernat Gabor -
Cooper Lees -
Donald Stufft -
Dustin Ingram -
Filipe Laíns -
Ian Stapleton Cordasco -
Matthias Bussonnier -
Nate Prewitt -
Paul Moore -
Pradyun Gedam -
Ronny Pfannschmidt -
Stéphane Bidoul -
Thomas Kluyver -
Vinay Sajip -
Xavier Fernandez