[python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
Brett Cannon
brett at python.org
Wed Jul 15 19:59:46 CEST 2015
More information about the python-committers mailing list
Wed Jul 15 19:59:46 CEST 2015
- Previous message (by thread): [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
- Next message (by thread): [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Jul 15, 2015 at 6:38 AM Barry Warsaw <barry at python.org> wrote: > On Jul 15, 2015, at 12:29 PM, Nick Coghlan wrote: > > >The FreeBSD community recently posted their Code of Conduct guidelines > >for technical discussions at > >https://www.freebsd.org/internal/code-of-conduct.html > > I wouldn't mind something shorter, perhaps a happy middle ground between > that > and the PSF CoC? In any case, +1 though... > > >Would folks mind if I drafted a CPython Code of Conduct inspired by > >their example, and proposed it for inclusion in the Developer's Guide? > > Why not put it in a low-numbered informational PEP? > > +1 on the idea and on making it a PEP that the devguide can reference since it will essentially be a procedural doc. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20150715/934858b0/attachment.html>
- Previous message (by thread): [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
- Next message (by thread): [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list