The proposal came from the PSF, regarding PSF business; and despite the contention the measure passed easily (just not as easily as the other measures). The SC acted on a recommendation from the PSF's "Code of Conduct Work Group" (an unelected body). The ban was announced on behalf of the SC by Thomas Wouters (one of the SC members) - see the OP of the thread I linked - who describes the separation of concerns here: https://discuss.python.org/t/why-im-leaving-discuss-python-o...
That said, Wouters seems very sympathetic to the Work Group's reasoning on a personal level, in general, based on other interactions I've had. On the other hand, I can vouch that Barry Warsaw has always been much more level-headed. The others I don't know so much about.
The reasoning may or may not be correct. However, the timing of application was extremely poor irrespective of that.
If an individual is exhibiting problematic behavior, then it was problematic before and will be problematic after. There will be plenty of other opportunities to throw the ban hammer in defense of someone who isn't part of the leadership group.
Applying a punishment that looks like abuse of authority in response to someone challenging a measure which increases your scope of authority is an extraordinarily poor choice of timing. Instead of looking like punishment for wrongdoing it looks like harassment and intimidation because someone had the temerity to publicly call you out.
The current problem is that punishments do not have negative consequences to their use. If something is important enough to punish someone else, it should also be important enough for you to take a penalty (stepping down, being unable to run for reelection, being unable to be a moderator, etc.).
If this kind of behavior occurred inside a corporate political structure, for example, there would be all manner of people decrying the abuse of power, and the approbation would be nearly unanimous.
Funny how quickly people get thin skinned when they're delivering the pointy end of the stick rather than receiving it.
>The reasoning may or may not be correct. However, the timing of application was extremely poor irrespective of that.
I agree. I just wanted to highlight that it was not the SC's original proposal, nor their unilateral action; and that the Code of Conduct Work Group appears to be pulling the strings behind the scenes in many ways (while enjoying a relative lack of accountability).
> That is a bad look no matter what you think of Tim's actions.
The thing that leaves a very bad taste in my mouth is the public announcements of the suspension. It's like a company announcing they fired someone, or that they put them on a PEP. Maybe they were 100% justified in the firing, but you know, live and learn, new chances, etc.
Making a big deal out of it on the internet ("the internet never forgets") is not treating the person with kindness or dignity, and is not respecting their privacy. And yes, people deserve those things even if they did something wrong.
My comment is that the SC needs to go even if I concede their point that Tim is wrong. It doesn't actually matter whether Tim is right or wrong simply because what the SC did absolutely looks like intimidation and harassment regardless.
At this point, I'm thinking that CoC's all need to be updated with "Leadership gets to use the banhammer, but it costs them their seats for some number of election cycles."
There are a whole set of problems, IMHO. The code-of-conduct working-group (CoC WG) members are self selected. There is no effective oversight mechanism. No matter if you think they are currently doing a good job or not, it's not a proper way to organize such a group. The steering council (SC) did a poor job in communicating and their tendency towards secretiveness does not inspire confidence that the machinery regarding these things is working correctly. Part of the justification for secrecy is that they are protecting the banned person. That is hard to believe since it's trivial to figure out who they are talking about given their initial ban announce posting (X number of posts in a certain topic points to exactly one person). So it looks more like the secrecy is to avoid answering uncomfortable questions about the decision making and the process and not about actually protecting the accused.
Someone made a great analogy about what is happening here. You have a machine that is supposed to make toy dolls. One day you notice the dolls coming out the machine are deformed and weird looking. So, you say to the doll factory manager:
> I think something is wrong with the doll making machine.
They say
> No, this is a very high quality doll making machine, look at the specifications on the great looking dolls it will make. Don't you trust that this machine will make proper dolls? The manufacturer and people running the machine are all very trustworthy
You say:
> That might be true but I see the dolls coming out are deformed, something must be wrong.
Tim does not get a free pass to behave badly just because he is a long-time Python contributor. However, given his literal decades of civil behavior in many public forums, it is hard to believe he did something that was justifying a ban. Based on looking at what the CoC WG shared and what Tim shared, I don't see anything that justifies it. So, I don't think the "machine" is working correctly.
It took me a while to realize that the SC people were talking about in this thread was the Python Steering Committee. I thought it stood for Star Chamber.
The Python SC was floating a contentious proposal without justification, and Tim Peters forcefully called them out on it. Repeatedly.
And, in return, it feels like the SC went hunting for justifcation to throw a ban at him.
That is a bad look no matter what you think of Tim's actions.
This SC needs to go even if they are right, and Tim is wrong. Period.