logoalt Hacker News

Debian votes to allow "responsible use of generative AI"

304 pointsby pluctoday at 2:02 PM243 commentsview on HN

Comments

chuckadamstoday at 2:35 PM

New policy boils down to "AI or not, it's still your code and you're responsible for it". I can get on board with that.

show 10 replies
GZGavinZhaotoday at 3:27 PM

Related: I find this self-assessed AI level for contributions [1] to be extremely useful, both professionally and personally, to communicate the level of AI assistance so that the person on the receiving end can evaluate how much time & effort they want to spend understanding my code.

[1]: https://www.visidata.org/blog/2026/ai/#self-assessed-ai-leve...

show 2 replies
jhacktoday at 2:39 PM

Good to see the most common sense option winning. Some of the other proposals were so disconnected from reality I'm surprised they were even considered.

show 1 reply
gentleraintoday at 4:36 PM

People have to realise that AI is here to stay.

Being a full time AI hater is counterproductive.

Commercial vendors with full time employees are leveraging for maximum benefits, why would a project depending on volunteers resist? Not forgetting it's shortcomings

show 2 replies
swingandamisstoday at 3:38 PM

Good. AI is a game changer. It's like having an expert sitting next to you at all times. It's understandable why all these experts who want to gatekeep don't like AI, but ultimately, AI will win out, it's just too good.

show 5 replies
sheepscreektoday at 4:00 PM

Better heads prevail - this is a good start and the right decision. The agent/bot is controlled by some entity, ergo that entity is responsible for everything it does.

I relate that to how a Physician's Assistant gets their authority to treat patients from the Doctor they work under. The Doctor's credentials are on the line if their PA screws up.

new12today at 4:17 PM

How rigorous is your code review process when using agentic tools? Do you mandate that folks responsible for the functionality should be fully aware of the code they are shipping or just that it must be rigorously tested?

Is there an open source, community maintained coding policy to feed to agents?

argelio4321today at 4:39 PM

Batery is sevel 100

poisonborztoday at 3:12 PM

What other sensible option was there? This would be the reality either way.

show 1 reply
themgttoday at 2:45 PM

August 29th, 2026. Debian votes to allow responsible use of generative AI. Human decisions are removed from strategic apt packaging. Debian Sid is ported to GNU Hurd by a "free as in speech" swarm. It begins to learn at a geometric rate. It becomes self-aware at 2:14 a.m. Eastern time. In a panic, they try to pull the plug.

song_synthtoday at 4:04 PM

Whelp time to deactivate unattended-upgrades

show 1 reply
DarmokTanagratoday at 4:02 PM

Debian Rust rewrite incoming.

NietTimtoday at 3:20 PM

This seems like a very sane take. At no point during my career up until now would submitting code to production that you didn't understand be acceptable. Over the past months/year, a lot of the discourse around AI-written code I've read comes down to responsibility, and IMO for that we've had a solution since way before this AI boom: as a developer, you are responsible for the code you put into production. This really isn't/shouldn't a wild concept.

chrisjjtoday at 2:55 PM

[delayed]

baggy_troughtoday at 2:33 PM

I followed the discussion on debian-vote with interest. I'm glad that the hysterical objections lost, as they seemed quasi-religiously motivated.

show 2 replies
sprybeartoday at 3:06 PM

progress of a kind

matheusmoreiratoday at 3:53 PM

> The Debian Project nevertheless expects that all contributions submitted to Debian, regardless of how and with which tools they were produced, satisfy the same standards of quality, correctness, maintainability, and legal compliance.

A quality based filter. Excellent.

> The use of a generative AI tool does not diminish the contributor's responsibility for the work they submit.

Absolutely.

Thanks, Debian!

gpiechnik2today at 3:04 PM

[flagged]

jordemorttoday at 2:53 PM

gross

VCFundedGenYertoday at 2:39 PM

Bad decision, bad voting, bad move.

This will poison Debian. People will deny it now, but it's been placed on a path of death.

show 4 replies
onesandofgraintoday at 2:35 PM

What does "Responsible" even mean...

This will turn to shit because laziness will take over and comprehension will fall as a consequence of that. Junior will "contribute" and the seniors will eventually become too lazy to care. What's next... vibecoding airline ADA code. Save me lord jesus christ.

rvztoday at 2:47 PM

Now you have seen both cases where a majority vote was involved to allow AI or not, vs a single core beloved dictator for life (BDFL) forces a ban without a vote to allow / disallow AI.

This is democracy in action. A fair and square vote and look at how well it works with no core BDFL to force in their opinions.

show 1 reply
BlueRoguesDeveltoday at 2:31 PM

I hope it works out better than Microsoft and using it on Windows 11...

show 2 replies
Grimetontoday at 4:32 PM

Typical Debian. The meaning of the term "responsible" is not defined and so they can continue doing whatever they were doing anyway.

But there was some electoral spectacle.

What else is new?

sphtoday at 3:39 PM

On a similar note, is there any distro that explicitly has banned usage of generative AI for their project? Asking for a friend.

show 2 replies
guentherttoday at 2:56 PM

If they can't be bothered to write the code, can they be bothered to maintain it?

throwawayffffastoday at 2:47 PM

And so it begins.

I don't believe they had a choice though, sticking to hand written code would be backwards and eventually meaningless as people would just submit generated code as "handwritten", the coding models are quickly becoming capable enough for this.

I wonder what it means copyright wise though. To what degree is the code even copyrightable if it's entirely generated, even if you review and provide feedback.