Brett Cannon <brett <at> python.org> writes: > 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.
When I started here, the PSF and python-dev were considered disjoint entities (quoting MvL from memory). Looking at https://www.python.org/psf/records/board/history/ , half of the current directors have never appeared anywhere on the python-dev infrastructure, most notably on python-checkins. Contrast this with e.g. the period of 2003-2004, where I still know all of the directors even though I did not know Python at that time! Some very prolific contributors do not appear in the list of PSF members at all. This particular CoC specifically addresses conference misbehavior, which is fine. No CoC short of an 800 page volume can address the many forms of human shortcomings in more complex situations. I'm not going to go into detail here, but "suaviter in modo, fortiter in re", even though usually depicted as desirable behavior, can easily lead to more stagnation and friction than occasional superficial impoliteness. I think python-dev should remain an entity where interested people can just come and "hack on something" instead of being overburdened by regulations. As for the devguide, briefly mentioning the categorical imperative should suffice. ;) Stefan Krah _______________________________________________ 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/
