Debian votes to allow 'responsible use of generative AI'

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...

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.

I don't understand enough about coding to speak on Debian as anything but a longtime user.

I find AI useful for small shell scripts that you can visually inspect.

I want to make a GIF later, so I'll probably ask Duck.AI how to write the command if the file path to the MKV is X and the timestamps are Y and Z.

Then, I can create my own little tool without downloading some shady binary that slaps a UI on Imagemagik(sp?) or whatever.

I've only played with AI a little bit, with a focus on local LLMs, but even simple things like an anonymous FTP scanner I wrote took a lot longer than someone slightly more skilled than me could have done them in.

Anyways, I always respected how Debian gatekeeps access to the code -- some kinds of gatekeeping are cool and good, and a lot of young folks fight with devs trying to show how smart they are -- I've been guilty of that myself in my youth.

Joey Hess is unimpressed. See https://joeyh.name/blog/entry/Debian_and_the_sirens/

A good heuristic is to understand the generated code you submit as if you typed every character yourself. A "I'm not sure, AI wrote it" type circumstance is a critical failure.

Good outcome, mostly.

Option E beat literally every other option, so it is an unambiguous Condorcet winner.

Bradley–Davidson analysis: https://gist.github.com/tulior/74479b28ddd1e191e5b2d89b8b68c...

The Bradley-Davidson model gives Option 5 a 99.9993% posterior probability of ranking first.

Options 2 and 6 are effectively tied for second.

Option 5 also beat every alternative head-to-head. Its closest matchup was against Option 2, at 57.8% to 42.2%, so the result was decisive overall even though the closest pairwise contest was not a blowout.

How much does open source rely on copyright for enforcement?

Do court decisions that limit copyright protection of AI generated content cause problems for open source? Isn't there a requirement for a "Mental Conception" of the code output when using such a tool? Even copypasta requires you to somewhat know what you need to do, where "automated bug finding", does not seem to.

Is anyone tracking how the different distros are coming down on the question?

I was curious how Fedora is moving on this question, but I don't know where to look. And if one wants to hop distro either towards or away from AI, it would be nice to have a place to see the relative adoption.

Linux distros are the perfect place to have a wide marketplace of options to suit every person, from completely anti-AI to completely YOLO vibe-code.

The voting seems to have been pretty much linear to how pro-LLM they were. So it's interesting that all of the proposals were essentially anti-LLM and the chosen one was the mostly neutral, only slightly anti-LLM one. The absence of any pro-LLM proposal indicated that proposal writers are not in sync with the voters