2 ms·
Not meaning to support him, but for Kent’s perspective: https://www.patreon.com/posts/trouble-in-116412665 https://www.patreon.com/posts/trouble-in-116412665
by alwayslikethis 2y ago
Not meaning to support him, but for Kent’s perspective:
https://www.patreon.com/posts/trouble-in-116412665 https://www.patreon.com/posts/trouble-in-116412665
I don't think what Kent did was right, but I'm also not sure this kind of heavy-handed approach by the CoC team is good, either. The forced public apology sounds a bit like a kindergarten teacher forcing two kids to shake hands after a fight.
On my part, I just hope that Linux will get a real competitor to ZFS.
- senectus1 2y agoI dont think so, It requires an acknowledgement of a back-down... a de-escalation. Without it your only two choices are to boot him out or let him stay and try to ignore him. One is overly heavy handed the other just formulates escalating toxicity.
- gomijacogeo 2y agoHis well over 6,000 word perspective. And I think that's one of the reasons Kent got the pointy, if maladroit, end of the CoC's attention. Every time he wants to break/rearchitect an internal API, or every time he makes a submission that flagrantly goes against kernel convention, you have to navigate a dozen walls of text where Kent vents and re-re-relitigates every transgression he's endured, every minute detail of his thought process as to why he needs to break the rules because his case is special, his list of ailments and anxieties that all the pushback is causing him, etc, etc, etc. His language is frequently escalatory and he seems unable to contemplate alternatives until at the brink of someone's (frequently Linus') patience and threats of bans or having bcachefs yanked from the kernel. It's brinksmanship and he overstepped. In short, he is the "that guy" on the list.
- anonfordays 2y agoDo you contribute to Nix or NixOS by any chance?