[python-committers] Making the PSF CoC apply to core developers
mal at egenix.com
Sun Mar 6 13:13:46 EST 2016
On 05.03.2016 00:40, Brett Cannon wrote:
> On Fri, 4 Mar 2016 at 14:04 M.-A. Lemburg <mal at egenix.com> wrote:
>> I don't think that spamming all MLs, Github accounts, etc.
>> with CoC notices will help anyone.
> Which is not what I'm suggesting nor would I want to do unless it's a
> stated change in policy so people feel properly notified.
I was referring to adding CoC links to all ML footers (causing it
to appeary on each and every ML message), all Github repos, etc.
I think this is not helpful. It's better to have a single page
on the python.org where we state how we use the CoC and perhaps
a footer link on python.org pointing to it.
Perhaps we don't even need a new page and simply use the
existing CoC page for this, by adding some more text to it
and perhaps a FAQ section.
>> You may not be aware, but all PSF infrastructure is covered by
>> the PSF CoC already, and has been for quite a while:
>> RESOLVED, that the Python Software Foundation shall manage and curate
>> the Foundation's public
>> and member-accessible web properties to remove spam, serve the membership,
>> and conform to the the
>> Python Community Code of Conduct.
>> Approved 9-0-0 by IRC vote, 3 January, 2014.
> That's great, but how are people to know this if they don't read the
> minutes of the board? Is it considered too much if I link to the minutes in
> the devguide so people know about this (
If needed at all, it's better to link to above yet-to-be-written page.
>> All PSF members have acknowledged this and adding yet another
>> notice to each and every point of interaction will not make
>> things better.
> I'm not worried about PSF members, it's all the new folk who are just
> "walking off the street" and are looking to contribute.
>> If there are issues, point people to the CoC. Otherwise, let's
>> not get all tangled up in CoC links everywhere :-)
> Fair enough, but I would like at least one canonical location to link to
> that bit of the minutes so that it's somewhere a bit more public. Is a link
> in the devguide considered acceptable?
>> We can get the 16 ton weight out when needed...
>> and optionally even send the tiger.
>> Marc-Andre Lemburg
>> On 04.03.2016 22:31, Brett Cannon wrote:
>>> The discussion about the Code of Conduct has sputtered out, so I'm going
>>> assume those who care to speak up have at this point. It seems to me that
>>> the general agreement is that putting python-dev and bugs.python.org
>>> the CoC might not solve any real issues we currently have, but it won't
>>> hurt anything either (and both python-committers and python-ideas are
>>> already covered). And since the CoC might make some people feel more
>>> comfortable in participating, that means going ahead and flipping on the
>>> CoC where we reasonably can.
>>> So what I will do is try to convince the managers of python-dev to put it
>>> under the CoC and get the CoC mentioned in the footer of
>>> I will update the devguide to say that the various mailing lists and
>>> tracker are under the CoC so people are aware, but I won't go as far as I
>>> was originally proposing about covering all public, Python-related
>>> interactions. Once we move to GitHub we will most likely have a
>>> CONTRIBUTING file that links to the devguide and that file will mention
>>> that interactions involving the repo are under the CoC (or some other
>>> wording that says pull requests fall under the Code of Conduct).
>>> On Fri, 26 Feb 2016 at 11:29 Brett Cannon <brett at python.org> wrote:
>>>> I noticed that the devguide didn't explicitly mention that core
>>>> were expected to follow the PSF CoC (
>>>> https://docs.python.org/devguide/coredev.html and
>>>> https://www.python.org/psf/codeofconduct/, respectively). I have opened
>>>> http://bugs.python.org/issue26446 to make sure it gets documented.
>>>> Since this is technically a modification of the requirements of getting
>>>> commit privileges I wanted to mention it here before I (or anyone else)
>>>> made the change.
>>> python-committers mailing list
>>> python-committers at python.org
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> Marc-Andre Lemburg
>> Professional Python Services directly from the Experts (#1, Mar 04 2016)
>>>>> Python Projects, Coaching and Consulting ... http://www.egenix.com/
>>>>> Python Database Interfaces ... http://products.egenix.com/
>>>>> Plone/Zope Database Interfaces ... http://zope.egenix.com/
>> 2016-02-19: Released eGenix PyRun 2.1.2 ... http://egenix.com/go88
>> ::: We implement business ideas - efficiently in both time and costs :::
>> eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
>> D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
>> Registered at Amtsgericht Duesseldorf: HRB 46611
> python-committers mailing list
> python-committers at python.org
> Code of Conduct: https://www.python.org/psf/codeofconduct/
Professional Python Services directly from the Experts (#1, Mar 06 2016)
>>> Python Projects, Coaching and Consulting ... http://www.egenix.com/
>>> Python Database Interfaces ... http://products.egenix.com/
>>> Plone/Zope Database Interfaces ... http://zope.egenix.com/
2016-02-19: Released eGenix PyRun 2.1.2 ... http://egenix.com/go88
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the python-committers