@gregkh I think a kernel community joint statement of this (like we have for the research shenanigans due to a big fail a while ago) would be really good. currently the AI patches are at the "mostly just entertaining, obvious nonsense" stage still, but I guess this could change quickly
maybe wrap it up together with the guidelines for dual-licensed code, since that's another topic I've seen pop up in a few places in public and private ...
@gregkh
I don't think there's any way to enforce that, is there?
@gregkh how confident are you that you can detect violations of this policy?
@craftyguy @gregkh I'm not sure if the maintainers should be in the role of actively policing. They are overloaded enough as-is already.
IMHO as abuses are brought to light - via research done by individuals, groups or otherwise - the work can be pulled out. Just like the unfortunate events 1-2 years ago.
@gregkh Even if that provenance were proven, the output from an LLM can't be copyrighted itself, as far as I understand. So I'm not sure what that'd do to the kernel if it was a non-trivial contribution.
@gregkh maybe the idea of „copyright“ wasn’t so good after all.