So uh, now that #Debian did the thing, what's everybody going to use from now on?
@argv_minus_one Maybe #debian will choose to isolate AI-derived software in its own repository, making it opt-in. That would be very helpful.
I suppose vim would have to go in there. And it wouldn't solve the kernel issue.
@Steve @argv_minus_one this could be a first step towards that. I hope AI labeling could be something AI skeptical folks can push cross-distro, to raise the bar
@michel_slm @argv_minus_one Makes perfect sense to me. This is a sensible way to prevent or clean up a mess, depending on one's choices.
But how does one convince them to do such a thing? The option they just voted for specifically requires no labeling, and unless I'm mistaken it was the only available option that doesn't require labeling.
@argv_minus_one @michel_slm I don't really know. If it were in my power, I'd have a repository for software where the developers proactively report that they did not use AI, a repository for ones that report that they did, and one for those who don't specify.
But, that might get out of hand.
Maybe just make it a requirement that developers affirm that they did not use AI to be in the "free" repository, and lump everything else in "non-free."
@Steve @argv_minus_one that might be too hard, since per the GR, Debian itself is likely in the non-free bucket by that definition
The voting software, Devotee got an AI written patch just before voting opened!
@michel_slm @argv_minus_one Then I guess we're back to the fork idea.