On 01.04.2017 05:44, Raymond Hettinger wrote: > >> On Mar 31, 2017, at 2:40 PM, Brett Cannon <br...@python.org> wrote: >> >> In the (long) discussion of >> https://github.com/python/core-workflow/issues/6, Wes Turner began to do his >> usual posting of lists. People pointed out he was stepping out of line by >> being somewhat off-topic and seemingly lecturing folks. He posted some of >> his lists again and then I warned him that if he did it again I would block >> him for a CoC violation since he did not want to respect anyone's time by >> taking the time to edit what amount to dumping his personal notes on GitHub. >> (This is a long-standing issue, BTW, with Wes where he has been warned in >> other settings like distutils-sig about his posting behaviour.) > > ... > So, if Wes is to be blocked for a while, it should be on the basis of "adding > too much noise to an important communication channel" rather than CoC which > should be sparingly used for only egregious issues. Also, if a real CoC > issue does arise, I think any actions taken need to have multiple assents > from a group of decision makers rather than having one person become a > de-facto CoC czar with the power to banish people.
It's definitely a requirement of any CoC management to have at least two people decide on this, since CoCs in general are always open to interpretation and need to take multiple views into account. Wes's comments are nowhere near a CoC violation, IMO. I agree with Raymond that CoCs are not meant as a tool to silence people with different ideas or communication styles out of convenience. It's the ultimate tool, not the first to consider. If Wes were continuously offensive that would be a reason to start discussing CoC related actions. -- Marc-Andre Lemburg _______________________________________________ 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/
