
On 15.07.2015 04:29, Nick Coghlan wrote:
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
Looks like a good start, but as others have mentioned, I think we ought to simplify this a lot and use it as extension to the CoC we already have rather than as replacement.
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?
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source
Python Projects, Coaching and Consulting ... http://www.egenix.com/ mxODBC Plone/Zope Database Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/