You're right KR, it is pretty hard to enforce. However, having this field will at least let our good-faith contributors know what is expected for their commit message formatting so that we can begin to track generative-tooling use in the kernel to see how our developers are using it and possibly integrate it into the SBOM workflow if that evolves to be a requirement from the ASF.
It seems like there are a few options for this field. It would be nice to hook "Co-authored by:" into the GitHub interface. However, like Alin mentioned, I don't think we can consider generative-tools as co-authors under the ASF guidelines. I also think it might still be better to align the field name with what other major projects use, as Alin suggested. Best, Matteo On Fri, Jul 3, 2026 at 11:26 AM <[email protected]> wrote: > On 2026-07-03 17:07, Alin Jerpelea wrote: > > from my understanding: > > - a tool can not co-author code > > The issue is that unless the person writing the code agrees with this > position, it is nigh impossible to enforce this rule. (Unless the code > is an obvious AI slop.) Incidentally, I recently got a good example for > this but I don't think a wall of text would be appropriate for a vote > thread. >
