I think moderation and CoCs are needed, but this example looks to be an example of their misuse.
I'm glad as An American tax payer that we're not funding an organization with such petty politics and discriminatory behaviors.
Tim sounds similar to John Carmack recent she post about Meta:
> I wish I could drop (so many of) my old internal posts publicly, since I don’t really have the incentive to relitigate the arguments today – they were carefully considered and prescient. They also got me reported to HR by the manager of the XROS effort for supposedly making his team members feel bad
Once you have such a committee or COC, game over.
Or is it just a equlibra of just that they might be the best thing we have got currently or something similar?
Within perl we treated conference abuse privately in a seperate nonpublic group, but never mailinglist outbursts. This group had no power over anyone else. Esp. over devs with different opinions, who critized core devs over their work.
1. As the first person on the project, assume BDFL status and prepare to act that way as soon as you consider accepting a PR.
2. As a person, make sure you strongly understand what your moral values are, and why you hold them.
3. Proactively write your own Code of Conduct from scratch. It's important to have one so that you will not be pressured to use someone else's. It's important to ensure that it reflects your own values, not those of some activist organization (or another project that has been co-opted). Make it simple, but feel free to refer to additional documents. https://compass.naivete.me/ can be considered an example (this is not an endorsement, and again my recommendation is to write it yourself from scratch).
4. Do not have an "Enforcement Procedures" document, and actively reject any such proposal. The interpretation of your code of conduct should be apparent from the text itself, given a reasonable-person standard; you do not need to try to formalize the notion of a reasonable person.
5. If people think you are being unreasonable in your project governance, take that discussion somewhere else.
6. Remember at all times that everyone is free to fork your project. If people wish to do this over a governance dispute, it would be better for it to happen now than later. Do not try to prevent this from happening: do not attack the efforts of others (as has happened to XLibre), and also do not negotiate with others out of fear that they might start a fork. If they start a fork it is of no concern to you.
7. Only dictatorships and democracies are stable. While you are in charge, power rests only in those you directly appoint, and you may revoke this if necessary. When you are ready to leave, unless you have in mind a 100% trusted successor, ensure that your replacement is elected and that the project has a charter such that power can only rest with elected individuals.
A failure mode with a lot of community management systems is that they're adopted because they have a general vibe of keeping the bad people out. And that vibe will see any criticism of the community management document/team/actions as a way to sneak the bad people in.
Imagine I told you I found a rando discord server dedicated to a tabletop RPG I love, but complained that the moderation team was a clique. I claimed that I feel forced to fit in by pandering to their sensibilities and biting my tongue on other topics even if they're just flat out provably wrong. Nobody would assume I'm just salty because I secretly want to post porn, cuss and be racist in #general. Because we all know discord mods are notoriously petty tyrants.
Now give that discord community a github page and copy-paste in an HR document. The way expectations snap into treating them like levelheaded professionals with unassailable intentions and righteous goals is the reason this topic always goes nowhere.
The reality is that you may be confusing a victim with your political enemies.
But, the employees at the foundation, who are responsible for keeping the community healthy, and for enforcing policies, would absolutely take complaints, then use personal accounts, email list history, chat history, and such. It's effectively like how HR works.
> The only thing I've heard
Right, because you're talking to the wrong people, and you're ignoring the fact that he has had folks complain about his behavior, and you're also ignoring his email list and chat history, which you could go look at.
You're acting like this is some kind of witch hunt, when it's simply "HR" enforcing "employment handbook" standards. It just happens to be that this is a set of volunteers, rather than employees.
I'm not the person you replied to but I've just spent a bunch of time looking at (what seem to be) the relevant posts on https://discuss.python.org/, along with a couple of external posts about the ban, and I've yet to find anything that looks like a pattern of shitty behaviour on the part of Tim Peters. I wasn't previously aware of him and I obviously may have missed something important, so I ask this in good faith: can you point to some of the specific emails/chats you had in mind? (I'm happy not to argue the point if you'd prefer not to; I'd just like to see the strongest anti-Peters evidence.)
The threads you've waved at do not show Tim to be the "racist, sexist or creep" that you've insinuated. Rather, they show a committee that can't handle questions, abuses its own rules, and hides behind HR & secret "complaints".
Of course, that's just my opinion from skimming. It'd be better to have someone credible give honest evidence, instead of someone defaming & blaming while projecting their bigotry onto others.
Can you provide any concrete evidence of wrongdoing whatsoever?
For example, Mr. Peters has published comments of his that were removed from the pertinent discussions, and I can vouch for their accuracy from my own recollection. (Since the Discourse forum can also be used via mailing list, and emails cannot be un-sent, presumably many other people can corroborate via their own local backups, too.) Can you find anything in them to suggest wrongdoing?
The fact that there is no official concrete list of bannable posts suggests there are no standalone posts to look at and be like "wow, how come he's not banned yet". On the other hand I know people who walk a very tight line and find loopholes in every rule, and mods have a very hard time "officially" banning those types (even for a short time to help them reflect on their behaviour). Maybe it was like a town where the main bully met unfortunate circumstances and all twenty witnesses haven't actually seen anything for some reason.
Okay, but can you provide any concrete examples of anything objectionable whatsoever?
> The fact that there is no official concrete list of bannable posts suggests
No; it suggests that he did nothing wrong. Which he didn't.
> On the other hand I know people who walk a very tight line and find loopholes in every rule, and mods have a very hard time "officially" banning those types
I observed him throughout the entire exchange. He did nothing wrong.
ryan_lane claims to know things here, but refuses to cite anything. Because, I contend, there is nothing to cite.
Yes, Mr. Peters apparently has a personality that rubs certain people the wrong way, and over time they get the impression of wrongdoing. I find this impression to be completely unreasonable. But more importantly, the Python Code of Conduct explicitly to "be respectful of differing viewpoints and experiences" and "show empathy towards other community members"; and the way that people find fault with Mr. Peters demonstrates nothing of the sort. It is rather about seeking uncharitable interpretation, which goes so far as to state overt falsehoods.
Also: speaking from personal experience as a moderator, "skill issue tbh". At any rate, despite its length, the Python Code of Conduct is not a bunch of legalese in which people might be able to find "loopholes". The judgment of whether someone is playing along is appropriately subjective, as it needs to be for such matters.
The problem is that it isn't being applied fairly. Not even remotely.
> Maybe it was like a town where the main bully met unfortunate circumstances and all twenty witnesses haven't actually seen anything for some reason.
The PSF goes out of its way to avoid this circumstance with its reporting and incident-handling procedures. It goes so far (which is part of the problem) that they explicitly use it to justify a refusal to show any kind of evidence, even in cases where nobody in the discussion can imagine a way that the evidence could identify a reporter.
I use their bias sometimes for detection. For example, the GP here advances a melodramatic allegation, which someone from their Wikipedian tribe would certainly have documented-- if the evidence aligned with their bias.
All evidence I have seen points to the contrary.
> citing the rules he violated
I wish I could have the graciousness of Tim Peters. Those accusations were not made in good faith.
You can dig up any number of posts on anyone, as Richelieu has pointed out pre-Internet.
No, he does not. He has been a pillar of the community since the beginning, and well loved by many. He has also been trusted with various forms of moderation authority in the past, and his decisions were respected at the time.
> and they used the CoC to enforce a (temporary!) ban, citing the rules he violated.
Please read https://discuss.python.org/t/three-month-suspension-for-a-co..., and then https://tim-one.github.io/psf/crimes.html . Mr. Peters is, if anything, overly self-critical here. He quite frankly did nothing wrong. The supposed "rule violations" include things that no reasonable person could actually object to, as well as complete mischaracterizations of the observable facts. In some places, multiple points appear to refer to the same action. In some places it's unclear what is referred to and there has never been any official explanation. In no case is any evidence provided.
> If the CoC didn't exist, you'd be screaming "he didn't do anything wrong"
I am saying it (your use of the word "screaming" here is demeaning, substance-less rhetoric) because it is in fact the case. Many of the cited "violations" don't actually go against the Code of Conduct (https://policies.python.org/python.org/code-of-conduct/), even if they were true and accurate.
> but obviously, according to the well posted rules, he did
It is not obvious, because it is incorrect.
> and they enforced those rules for the good of the community.
No useful purpose was served by this suspension.
> The reality of the situation is that yall don't want to be excluded from communities for being racist, misogynistic, or creepy.
This accusation is baseless, incorrect, and offensive.
These are not mutually exclusive states. If anything, it has improved my esteem of PSL that they were willing to hold one of their "inner circle" up to scrutiny.
Even Linus Torvalds came around to the idea that he was a great software engineer and a mean individual to interact with. There's room for improvement in most if not all of us. I'm impressed at both Tim and the PSL for being able to disagree, go through a suspension, and come to terms. It's the kind of potential for growth that makes it a comfortable ecosystem to work in.
> The supposed "rule violations" include things that no reasonable person could actually object to
The problem with the "reasonable person" standard is that it's subjectivity masked in objectivity; we don't poll ten thousand people to decide what "reasonable" looks like. It's another term for "common sense," and... Common sense moves. Common sense said slavery was fine three hundred years ago. Common sense said homosexuality was an abomination sixty years ago. Common sense said you could be as awful to interact with as you wanted as long as you were making software people craved thirty years ago. We grow and change.
Their scrutiny is utter nonsense, as demonstrated by even a superficial examination of the facts.
He was (and still is) well loved by many (including myself, despite our political disagreements) specifically because of his demeanor.
> The problem with the "reasonable person" standard
And yet it's good enough to appear all over the law. None of the examples you describe bear any resemblance to the current situation.
Again: Tim Peters did not do anything wrong. We know what actions the list in https://discuss.python.org/t/three-month-suspension-for-a-co... refers to; most have been characterized unfairly or are even flat-out false. For the rest, if you have an argument as to how the action taken was actually in violation of what is described in https://policies.python.org/python.org/code-of-conduct/, you are welcome to present it.
The reality of the situation is that yall don't want to be excluded from communities for being racist, misogynistic, or creepy.