Re: [python-committers] Proposal for procedures regarding CoC actions

Maybe there should be a published list of moderators (not a mailing list, just a list of people to mail!) where you can send such reports. If a moderator is being rude it's probably time to escalate to the PSF. Thanks for pushing for a definite process on this issue! On Fri, May 5, 2017 at 11:44

Re: [python-committers] Proposal for procedures regarding CoC actions

Thanks everyone for the input. It is still unclear to me how one can report when someone is being rude on GitHub. In the mailing lists we can email the administrators. But what about on GitHub? Do I write to python-committers? What if it was a core developer who was being rude, where can a non

Re: [python-committers] Proposal for procedures regarding CoC actions

On 4 May 2017 at 06:10, Guido van Rossum wrote: > Two ex-board members disagree. I have to side with Brian; the PSF board > should have minimal say in how the developers develop. > > Note, I'm fine with the board being the arbiter when someone disagrees with > their ban though

Re: [python-committers] Proposal for procedures regarding CoC actions

Two ex-board members disagree. I have to side with Brian; the PSF board should have minimal say in how the developers develop. Note, I'm fine with the board being the arbiter when someone disagrees with their ban though -- there's got to be a "higher authority" for appeals. But I don't agree that

Re: [python-committers] Proposal for procedures regarding CoC actions

Since this is a matter outside the realm of committers, the PSF board will have to ultimately decide on any actions taken. The committers can report issues to the board and provide information useful for their decisions, the bad actor also has to be given a chance to respond to allegations and be

Re: [python-committers] Proposal for procedures regarding CoC actions

On Wed, May 3, 2017 at 3:28 PM, Mariatta Wijaya wrote: > Hi, > > First of all, sorry for bringing up an old thread. > I know this is an uncomfortable topic, and I also wish that we can just > avoid it, but ... I think we gotta do something about it. > > I understand

Re: [python-committers] Proposal for procedures regarding CoC actions

Hi, First of all, sorry for bringing up an old thread. I know this is an uncomfortable topic, and I also wish that we can just avoid it, but ... I think we gotta do something about it. I understand why Brett did what he did, and I support his decision. I do agree with Raymond's point, that

Re: [python-committers] Proposal for procedures regarding CoC actions

On 3 April 2017 at 04:08, Brett Cannon wrote: > On Sun, 2 Apr 2017 at 04:34 Paul Moore wrote: >> As a result, the public perception of a "code of conduct violation" is >> that someone has harassed, or otherwise made a community member >> uncomfortable,

Re: [python-committers] Proposal for procedures regarding CoC actions

Thanks, Raymond, this reads like a good proposal, but I'd like to suggest that the three people in question are only intended to discuss whether a CoC event has taken place or not and what the person has to say about this. They should then write up a summary to present to the PSF Board which then

Re: [python-committers] Proposal for procedures regarding CoC actions

Here's a step-by-step guide of how things would be handled with Raymond's proposal -- which seems reasonable to me, BTW -- and can act as an initial draft of what we can put in the devguide: 1. A person is warned that they are violating the CoC by the moderator of the resource being used

Re: [python-committers] Proposal for procedures regarding CoC actions

On 2 April 2017 at 06:59, Nick Coghlan wrote: [...] > And from the point of view of the impact on folks suspended and/or > banned, "I got suspended/banned from due to my inability to > follow explicit directions regarding my communications style" doesn't > seem to me all that

Re: [python-committers] Proposal for procedures regarding CoC actions

On 2 April 2017 at 14:27, Steven D'Aprano wrote: > But he didn't. He labelled Wes a CoC violator, both privately and in > public, for something which is a violation of the CoC only by *really* > stretching the definition. I mean, come on now, insufficiently > respectful of

Re: [python-committers] Proposal for procedures regarding CoC actions

On Sat, Apr 01, 2017 at 09:39:36PM -0400, Alexander Belopolsky wrote: > Luckily, in the Python community, episodes that require repressive actions > are rare enough that they can be dealt on a case by case basis without > causing much distraction. There is no need to over-formalize the process.

Re: [python-committers] Proposal for procedures regarding CoC actions

On Sat, Apr 1, 2017 at 8:43 PM, Raymond Hettinger < raymond.hettin...@gmail.com> wrote: > > * The other is tasked with handling rare one-off situations where the > stated goals are considering the needs of the community, being respectful > as possible to all parties, and doing what they can to

Re: [python-committers] Proposal for procedures regarding CoC actions

> On Apr 1, 2017, at 5:21 PM, Alexander Belopolsky > wrote: > > I propose that when someone thinks there is a problem serious enough to > warrant a Code-of-Conduct action, that it get referred to a group of three > people to make the decision. > > This

Re: [python-committers] Proposal for procedures regarding CoC actions

On Sat, Apr 1, 2017 at 7:07 PM, Raymond Hettinger < raymond.hettin...@gmail.com> wrote: > I propose that when someone thinks there is a problem serious enough to > warrant a Code-of-Conduct action, that it get referred to a group of three > people to make the decision. This reminds me of

[python-committers] Proposal for procedures regarding CoC actions

I would like to make a procedural proposal based on the ideas emerging from the other python-committers discussion regarding the two month suspension of Github project access for a developer who was posting non-productively. It seems that there is general agreement to differentiate commonplace