What Happened
The darktable community, developers behind the popular open-source photo editing application, is having a pointed discussion about whether to accept code modules generated by LLMs. The debate surfaced on the Pixls.us forum and hit Hacker News on March 7, 2026.
The core problem: contributors are submitting AI-generated modules that they don't fully understand. When maintainers request changes during code review, these contributors can't address the feedback because they didn't write the code themselves. They just prompted it.
This comes at a particularly bad time for darktable. The project is facing a GTK 4 migration estimated at 18 to 24 months of work requiring 3 to 4 developers. Maintainers are already stretched thin. Reviewing a flood of AI-generated module submissions pulls resources away from critical infrastructure work.
Some community members are pushing back, arguing that code should be evaluated on quality regardless of who or what produced it. Others have proposed solutions including a plugin framework to separate experimental modules from the core distribution, mandatory automated testing, and a temporary moratorium on new features during the GTK 4 migration.
Why It Matters
Darktable is a canary in the coal mine. Every open-source project is about to face this exact debate, if they haven't already.
AI coding tools like Cursor, Claude Code, Cody, and Aider have made it trivially easy to generate functional-looking code. The barrier to contributing has dropped to nearly zero. That sounds good in theory. In practice, it means maintainers now receive pull requests from people who cannot maintain what they submitted.
This creates a new category of technical debt: code that works today but has no human champion who understands it well enough to fix it tomorrow. For projects that run on volunteer time, that's a sustainability threat.
The licensing question adds another layer. When an LLM generates code trained on millions of repositories, the copyright provenance is murky at best. Open-source projects with strict licensing requirements have legitimate reasons to be cautious.
Our Take
The darktable community is asking the right questions, but the answer isn't "ban AI-generated code." It's "raise the bar for all contributions equally."
The real issue isn't whether code was written by a human or an LLM. It's whether the submitter can maintain it. A contributor who used Cursor to write a module but genuinely understands the output and can respond to review feedback should be welcomed. A contributor who pasted a prompt into ChatGPT and submitted the result without reading it should not.
The proposed plugin framework is the smartest solution on the table. Separating experimental modules from the core distribution lets the community benefit from rapid development without burdening the core maintainer team. This is the same pattern that's worked for VS Code extensions, WordPress plugins, and browser add-ons for years.
For anyone using AI coding tools professionally, this debate is a reminder: the tool writes the first draft, but you own the result. If you can't explain it, debug it, and maintain it, you haven't actually contributed anything. You've just created a future problem for someone else.