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

2017-04-01 Thread Nick Coghlan
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 people's time? How Orwel

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

2017-04-01 Thread Steven D'Aprano
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

2017-04-01 Thread Alexander Belopolsky
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 mit

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

2017-04-01 Thread Raymond Hettinger
> 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 reminds me of

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

2017-04-01 Thread Alexander Belopolsky
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

2017-04-01 Thread Raymond Hettinger
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 l

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread R. David Murray
On Sat, 01 Apr 2017 15:08:27 -0400, Alex Gaynor wrote: > I'll be another voice saying that the CoC isn't the right mechanism -- the > CoC is for harassment and abuse (at least, most community's CoCs are, the > Python one is pretty vague). > > That said, I have no problem with the action taken, ba

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Paul Moore
On 1 April 2017 at 19:35, Brett Cannon wrote: > From what people have said in opposition to what I did, I think we need to > have a discussion about two things: > > 1. Is it a CoC violation if someone chooses to ignore repeated warnings that > their communication style is unproductive and thus a w

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Alex Gaynor
I'll be another voice saying that the CoC isn't the right mechanism -- the CoC is for harassment and abuse (at least, most community's CoCs are, the Python one is pretty vague). That said, I have no problem with the action taken, banning people who are extremely unproductive is a necessary step fo

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Brett Cannon
On Sat, 1 Apr 2017 at 09:27 M.-A. Lemburg wrote: > On 01.04.2017 05:44, Raymond Hettinger wrote: > > > >> On Mar 31, 2017, at 2:40 PM, Brett Cannon wrote: > >> > >> In the (long) discussion of > https://github.com/python/core-workflow/issues/6, Wes Turner began to do > his usual posting of lists

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Paul Moore
On 1 April 2017 at 18:59, Nick Coghlan wrote: > In this particular case, we're only at step 2 - self-moderation based > on previously provided guidance has proven inadequate, so an enforced > break specifically from the Python org on GitHub makes sense (mainly > because the tools for dealing with

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Senthil Kumaran
On Sat, Apr 1, 2017 at 9:27 AM, M.-A. Lemburg wrote: > It's the ultimate tool, not the first to consider. I am with this approach too. Defining a process and gradually enforcing CoC through a well-defined process seems to be way to go. Reading Brett's first email, it appears that it was followe

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Nick Coghlan
On 1 April 2017 at 19:16, Paul Moore wrote: > On 1 April 2017 at 09:17, Antoine Pitrou wrote: >> I have sometimes been mildly annoyed by his posting style on MLs, and I >> can imagine how it can become very annoying on a GitHub PR. > > Agreed. I don't feel that Wes' contributions are productive,

[python-committers] Please briefly explain reverts in commit message

2017-04-01 Thread Terry Reedy
I read commit messages to learn from others and understand the CPython development. There have been several recent revert commits with no explanation (that I can see) in the commit message. I would like to see at least something brief. Some possibilities I can think of: Accidentally pushed

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Ethan Furman
On 04/01/2017 02:16 AM, Paul Moore wrote: On 1 April 2017 at 09:17, Antoine Pitrou wrote: But even if that *is* the case, there comes a point where treating all participants equally does mean we're OK to say "sorry, you're being unproductive and that won't change, so we can't work with you" re

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread M.-A. Lemburg
On 01.04.2017 05:44, Raymond Hettinger wrote: > >> On Mar 31, 2017, at 2:40 PM, Brett Cannon wrote: >> >> In the (long) discussion of >> https://github.com/python/core-workflow/issues/6, Wes Turner began to do his >> usual posting of lists. People pointed out he was stepping out of line by >>

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Paul Moore
On 1 April 2017 at 09:17, Antoine Pitrou wrote: > I have sometimes been mildly annoyed by his posting style on MLs, and I > can imagine how it can become very annoying on a GitHub PR. Agreed. I don't feel that Wes' contributions are productive, and I generally ignore them. I support banning him i

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

2017-04-01 Thread Antoine Pitrou
Le 01/04/2017 à 05:44, Raymond Hettinger a écrit : > > FWIW, this may just be his communication style that reflects his tooling (probably emacs org-mode or some such) and his way of thinking about problems. It is most probably his communication style, as I have seen him act this way on other mai