Adding CoC link to the list description
Hi folks, It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see [1]), and it occurred to me that the description for this list should also link to the PyPA CoC: https://www.pypa.io/en/latest/code-of-conduct/ Cheers, Nick. [1] https://github.com/pypa/pypa.io/issues/33 -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Adding a CoC for both the mailing-lists is a good idea IMO. I think distutils-sig will likely need to be under the PSF CoC, since the PyPA CoC is aimed at projects. Pradyun On Wed, Jun 13, 2018 at 5:25 PM Nick Coghlan <ncoghlan@gmail.com> wrote:
Hi folks,
It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see [1]), and it occurred to me that the description for this list should also link to the PyPA CoC: https://www.pypa.io/en/latest/code-of-conduct/
Cheers, Nick.
[1] https://github.com/pypa/pypa.io/issues/33
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/
And, immediately after sending that mail, I notice you've made similar comments on the tracker issue you've linked to. :) Cheers, Pradyun On Wed, Jun 13, 2018 at 7:36 PM Pradyun Gedam <pradyunsg@gmail.com> wrote:
Adding a CoC for both the mailing-lists is a good idea IMO.
I think distutils-sig will likely need to be under the PSF CoC, since the PyPA CoC is aimed at projects.
Pradyun
On Wed, Jun 13, 2018 at 5:25 PM Nick Coghlan <ncoghlan@gmail.com> wrote:
Hi folks,
It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see [1]), and it occurred to me that the description for this list should also link to the PyPA CoC: https://www.pypa.io/en/latest/code-of-conduct/
Cheers, Nick.
[1] https://github.com/pypa/pypa.io/issues/33
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/
In keeping with this, I've updated the welcome message for pypa-dev https://groups.google.com/forum/#!forum/pypa-dev to refer to the PyPA CoC. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc On 6/13/18 10:07 AM, Pradyun Gedam wrote:
And, immediately after sending that mail, I notice you've made similar comments on the tracker issue you've linked to. :)
Cheers, Pradyun
On Wed, Jun 13, 2018 at 7:36 PM Pradyun Gedam <pradyunsg@gmail.com> wrote:
Adding a CoC for both the mailing-lists is a good idea IMO.
I think distutils-sig will likely need to be under the PSF CoC, since the PyPA CoC is aimed at projects.
Pradyun
On Wed, Jun 13, 2018 at 5:25 PM Nick Coghlan <ncoghlan@gmail.com> wrote:
Hi folks,
It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see [1]), and it occurred to me that the description for this list should also link to the PyPA CoC: https://www.pypa.io/en/latest/code-of-conduct/
Cheers, Nick.
[1] https://github.com/pypa/pypa.io/issues/33
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/
participants (3)
-
Nick Coghlan -
Pradyun Gedam -
Sumana Harihareswara