104
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Oct 2025
104 points (97.3% liked)
Open Source
48983 readers
166 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
Which by that point they'd already fixed. They mentioned they also accidentally pushed to the wrong branch.
I dunno, this just looks like someone accidentally made a bad commit and instead of being mature about it and letting them fix it we get statements like "all bridges have been burned" and a split in the community. That's a bit overblown, and if at the first sign of disagreement the decision is to blow up a project you're making it very hard to work with you.
Well, in that case, fair enough.
However, given that a lot of contributors allude to "putting up" with him for years in the comments of the GitHub issue, it seems it wasn't just a bad commit that broke the camel's back
That's fair, I don't know what other things have come before. It just seems really odd that there was such a severe reaction to what happened here.