[python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
Antoine Pitrou
antoine at python.org
Sat Jul 18 01:57:27 CEST 2015
More information about the python-committers mailing list
Sat Jul 18 01:57:27 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] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Nick, Given the amount of ludicrous babble that goes on on python-dev and the like, I've unsubscribed from those lists, so I don't have much interest in this discussion anymore. I hope you can make them a better place anyway. Regards Antoine. Le 15/07/2015 04:29, Nick Coghlan a écrit : > Hi folks, > > The FreeBSD community recently posted their Code of Conduct guidelines > for technical discussions at > https://www.freebsd.org/internal/code-of-conduct.html > > I think their guidelines align pretty well with the way we try to run > the CPython issue tracker and the core mailing lists, but we don't > currently spell out those expectations for newcomers (or potential > newcomers) as clearly as they have. > > 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? > > Regards, > Nick. >
- Previous message (by thread): [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
- Next message (by thread): [python-committers] 2.7 compilation problem on Mac 10.10.4 - Failure with mac specific modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list