On Fri, 4 Mar 2016 at 14:04 M.-A. Lemburg <m...@egenix.com> wrote: > Brett, > > 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. > > 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 ( https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties )? > > 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? -Brett > > We can get the 16 ton weight out when needed... > > https://www.youtube.com/watch?v=U90dnUbZMmM > > and optionally even send the tiger. > > Cheers, > -- > 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 > to > > 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 > under > > 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 > bugs.python.org. > > I will update the devguide to say that the various mailing lists and > issue > > 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 <br...@python.org> wrote: > > > >> I noticed that the devguide didn't explicitly mention that core > developers > >> 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@python.org > > https://mail.python.org/mailman/listinfo/python-committers > > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > > > -- > Marc-Andre Lemburg > eGenix.com > > 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 > http://www.egenix.com/company/contact/ > http://www.malemburg.com/ > >
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/