Package: debian-policy Severity: wishlist X-Debbugs-Cc: [email protected] Given Debian's decision on AI and LLM usage, perhaps something like:
[X-]AI-Usage: none | optional | required [X-]AI-Dependency: none | local | external [X-]AI-Assisted: none | packaging | source | documentation | ... in the control file would be a go'er? Would at least encourage transparency and choice for those of us that care. I wonder if that would be consistent with the resolution as voted for? Note. I'm not tied to any specific fieldnames or direction on how they are used - there are many excellent DD who might be able to solve that. However, I'm proposing X variants in the hope that even without a policy change, those that care can start the process towards transparency now. -- System Information: Debian Release: 13.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.101+deb13-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled debian-policy depends on no packages. Versions of packages debian-policy recommends: ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 ii libjs-sphinxdoc 8.1.3-5 pn sphinx-rtd-theme-common <none> Versions of packages debian-policy suggests: pn doc-base <none>
