[python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
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. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
On 07/14/2015 07:29 PM, Nick Coghlan wrote: 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? Sounds good to me. -- ~Ethan~ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?
On Tue, Jul 14, 2015 at 10:29 PM, Nick Coghlan wrote: > 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? > The language of the FreeBSD Code of Conduct is a pretty heavy CYA-style corporate legalese, but the overall message sounds right. +1 ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
