22 Dec 2018 22 Dec '18
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 email@example.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 firstname.lastname@example.org wrote: >>> >>> Hi folks, >>> >>> It was recently pointed out to me that the distutils-sig list description is missing a CoC reference (see ), 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. >>> >>>  https://github.com/pypa/pypa.io/issues/33 >>> >>> -- >>> Nick Coghlan | email@example.com | Brisbane, Australia >>> _______________________________________________ >>> PyPA-Committers mailing list -- firstname.lastname@example.org >>> To unsubscribe send an email to email@example.com >>> https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/ > _______________________________________________ > PyPA-Committers mailing list -- firstname.lastname@example.org > To unsubscribe send an email to email@example.com > https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/ >