this post was submitted on 17 Oct 2025
120 points (98.4% liked)
Open Source
41503 readers
349 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 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem is here is not AI, the problem here is pushing code that didn't even compile straight to main. It's a huge collaborative project, running it as a one man show just doesn't work anymore.
Had he made a PR/Draft, none of this would have happened. Hell, even his commit message says "needs to be reviewed before being deployed"
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.
Gotcha