The TYPO3 Association Board statement on GPL licensing and AI-generated
code [1] says license compatibility depends on provenance, not on the
tool used, and that responsibility rests with the contributor. It
leaves the Core to put this into practice through its own process.
This is how the Core Mergers do that.
1. Responsibility and sign-off
Whoever submits a change is responsible for it, however it was
produced. A Signed-off-by: line certifies the Developer Certificate of
Origin (DCO) [2]: the person has the right to submit the change under
the project's license. For Core Mergers, it is the signal that a
person takes ownership of and responsibility for the work.
The Board recommends evaluating a DCO sign-off but does not make it a
precondition. We follow that: humans SHOULD sign off their commits. We
may require a human sign-off in the future.
A new patch set does not require an additional Signed-off-by: line.
Anyone uploading one MAY add their own.
2. AI tools and committing
The sign-off is a personal statement about provenance. Only a human
can make it and be accountable for it, so AI tools MUST NOT add a
Signed-off-by: line. The Linux kernel follows the same rule.
We recommend that the human makes the actual commit rather than
letting an AI tool commit. That way, they review exactly what they put
their name to.
3. AI attribution
Anyone MAY credit AI tools with Co-authored-by:, Assisted-by: or
similar lines. The Board mentions a lightweight disclosure convention
as one possible instrument. The Core Mergers recommend leaving such
lines out:
- No distinction in the workflow. The TYPO3 Core workflow does not
distinguish whether AI wrote the changelog, the commit message, all
of the code, or only helped with research before any code was
written. One trailer covers all of these alike.
- Reviews have no equivalent. Gerrit comments and reviews can be
AI-assisted or fully AI-driven, with no mechanism to mark it.
Labeling only commits records one part of the process.
- It has become noise. Most contributors use some AI tool somewhere in
their work. A label on nearly every commit says nothing about
provenance, which is where the licensing risk lies.
We have never used Co-authored-by: for human collaborators improving
patches either.
[1] https://news.typo3.com/article/typo3-association-board-meeting-protocol-8-july-2026/board-statement-on-gpl-and-ai-code
[2] https://developercertificate.org/