Yes obviously the code you commit must be yours and you need to make sure it is. That is already a rule, what’s the point of telling people how to work above that?
You cannot tell from the code necessarily anyway so anti-AI policies are hard to enforce. In the end the developer (or AI wielding human) is responsible for the code quality and its license which is what matters. All this discussion feels just like the usual culture war dividing the community. I’m more concerned about the intentions of people adding fuel to the fire.
I used to use audacity for sample editing: Cutting start and end, normalizing, removing noise of a single sample. This is totally the wrong direction for me. Everything shown in this video is done better by one of the multiple already available DAWs (e.g. ardour, bitwig).
You cannot tell from the code necessarily anyway so anti-AI policies are hard to enforce. In the end the developer (or AI wielding human) is responsible for the code quality and its license which is what matters. All this discussion feels just like the usual culture war dividing the community. I’m more concerned about the intentions of people adding fuel to the fire.
I you are ready to make an exception for the Linux kernel you might as well make an exception for the Debian distribution which is the basis of a lot of stuff.
deleted by creator
This is all completely out of your control. You cannot tell people how to work in opensource and projects are completely unable to control if someone uses AI (or which one) to perform tasks, since it is not visible in the result. The easiest thing for you to do, if you don’t want to take part in it, is to put down your phone and go outside.