It feels like there’s a meta-discussion to be had about AI disclosure and AI use in a lot of these projects and it’s starting to boil over.
I would suggest that maintainers should:
- Add an AI disclosure in their readme, which is what I do on my projects. If you don’t like AI then it’s on the tin and you can avoid it – explicit is always better than implicit.
- Provide guidelines on AI contributions to their project. Every project needs an AI contribution policy now because we live in a world where most devs do use AI code gen. If you accept a patch from a community user it’s probably been touched by AI.
- Detail their AI workflow, but specifically how they review this code. I can only really work and review at a file-at-a-time pace so that 100% of AI code is reviewed by me, in detail, and it’s up to my standards.
When it comes to existing projects that start adding AI contributions it’s always going to be difficult. It’s not something projects started with even the option of, there’s no way to get consent from your users (nor whether you should you get their consent), and there have been varying levels of AI code gen for years now from simple completions to now agentic vibe coding.
I’ll be honest, most of my own projects use AI generated code, and I use it for work. It’s never code I couldn’t have written myself – because if it were how could I review it? But the fact is, in the year 2026 AI code generation is both fast, usable, and it’s near ubiquitous. There are tasks I could work on for weeks that I can build plus review in a couple of hours with AI. It’s very hard to argue with that, and I’m a very picky coder+reviewer.
And lastly, for the community we all need to be mindful of open source maintainers.
They work hard, for free, and get treated like shit by users, the law, and big corporations. There’s a new generation of people who sign up for code hosting services just to request features or complain in your git issues, they’re opening up slop PRs and emailing you. Plus, internet users love to pile on and harass people.
Please remember there’s (usually) a human made of meat at the end of the intertubes, and when 100s of people write mean/abrasive things it adds up. Nobody is perfect, open source devs are just trying to share and help.
PS for mods: I saw there was another thread on another app using AI that was locked as off topic, I am trying to be constructive in this comment, but if it’s off topic/too divisive I understand.
eodur@piefed.social 3 days ago
The BookLore thing is really disappointing. I hope we see a quality fork in the near future.
KairuByte@lemmy.dbzer0.com 3 days ago
Just read through some of the BookLore stuff and that was a wild ride.
bobslaede@feddit.dk 3 days ago
Yeah… I will not be updating my instance for a while. Will probably start looking for something else.
Wild ride…
red_bull_of_juarez@lemmy.dbzer0.com 3 days ago
After reading both the accusations and the dev response I don’t know who to believe. I love BookLore and have not encountered any issues, so I guess I’ll stick with it for now.
irmadlad@lemmy.world 3 days ago
I have seriously considered spinning up Booklore. Great looking UI. Oh well.
EarMaster@lemmy.world 3 days ago
I’d rather have a happy and productive maintainer than a burnout and an orphaned project. Either way forks can be made at any point - so if you don’t like the use of AI just fork it or don’t update any more and stay happy. No need for either of you to get mad at each other.
iamthetot@piefed.ca 3 days ago
They said they were disappointed, not mad.
tofu@lemmy.nocturnal.garden 3 days ago
I’m not sure a fork makes sense given the dev merged way too much nonsense already. Maybe from a point in time before it started?
I’ve been looking to check out Booklore over some annoyances I have with CWA but IDK anymore.
panda_abyss@lemmy.ca 2 days ago
Don’t let perfect stop you from achieving good.
It’s not radioactive waste, it’s code. You can read it, write it, change it. Just like any legacy codebase it’s full of shit, and maintaining means addressing the specific issues.