Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?

2015-07-16 Thread Meador Inge
On Thu, Jul 16, 2015 at 10:08 AM, Nick Coghlan wrote: > That last one is actually an area where I *dis*agree with the FreeBSD > guidelines - I see asking for someone to revert a change as a big > deal, as it means we're laying claim to a non-trivial amount of their > time. A non-urgent request fo

Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?

2015-07-16 Thread Nick Coghlan
On 16 July 2015 at 14:16, Steven D'Aprano wrote: > On Wed, Jul 15, 2015 at 12:29:52PM +1000, Nick Coghlan wrote: > [...] >> 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 expec

Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?

2015-07-16 Thread Antoine Pitrou
Le 16/07/2015 07:34, Brett Cannon a écrit : > > I have met people at PyCon > numerous times who have viewed at least python-dev as at minimum cold > and possibly hostile to people, and that's simply not the kind of > environment I would like to foster. For the record, the last time someone said

Re: [python-committers] More explicit Code of Conduct for the issue tracker & core mailing lists?

2015-07-16 Thread Antoine Pitrou
Le 16/07/2015 07:34, Brett Cannon a écrit : > And three, we need a CoC. Not to explicitly call anyone out, but in the > past week or so I have heard peoples' ideas called "ridiculous" and been > told to "shut up" on various mailing lists. Which mailing-lists? AFAIK, the CoC would be for python-de