Skip to content

Proposal: Add AI contribution policy#1233

Open
vdemeester wants to merge 2 commits intotektoncd:mainfrom
vdemeester:propose-ai-contribution-policy
Open

Proposal: Add AI contribution policy#1233
vdemeester wants to merge 2 commits intotektoncd:mainfrom
vdemeester:propose-ai-contribution-policy

Conversation

@vdemeester
Copy link
Member

@vdemeester vdemeester commented Nov 20, 2025

  • Establish clear guidelines for responsible AI tool usage
  • Ensure transparency through disclosure requirements
  • Maintain quality and security standards for AI-assisted work

This is modeled from Fedora's AI contribution policy: https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/

/cc @tektoncd/governing-board

- Establish clear guidelines for responsible AI tool usage
- Ensure transparency through disclosure requirements
- Maintain quality and security standards for AI-assisted work

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester added the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Nov 20, 2025
@tekton-robot
Copy link
Contributor

@vdemeester: GitHub didn't allow me to request PR reviews from the following users: tektoncd/governing-board.

Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

  • Establish clear guidelines for responsible AI tool usage
  • Ensure transparency through disclosure requirements
  • Maintain quality and security standards for AI-assisted work

/cc @tektoncd/governing-board

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 20, 2025
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good, thanks!

@afrittoli afrittoli added kind/documentation Categorizes issue or PR as related to documentation. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Nov 20, 2025
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 20, 2025
@waveywaves
Copy link
Member

+1
/lgtm

@tekton-robot
Copy link
Contributor

@waveywaves: changing LGTM is restricted to collaborators

Details

In response to this:

+1
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@waveywaves
Copy link
Member

/approve

Copy link
Member

@twoGiants twoGiants left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it 😸 👍 but I think it's not strict enough and to long. I think the ghostty AI Policy is pretty good.

It states the most important thing at the beginning and in the second paragraph states that maintainer can close PRs if he suspects undisclosed AI use => If AI isn't disclosed but a maintainer suspects its use, the PR will be closed [1].

Of course I would remain professional and leave out such things => Bad AI drivers will be banned and ridiculed in public. You've been warned. => 🤣 But I understand the sentiment. I have reviewed to much AI slop in last 6 months.

I propose to use the Ghostty AI policy and adapt it a bit:

Of course it's up for discussion and the policy here is already great! If we decide to keep it I would at least change it a bit and say that ALL AI usage must be disclosed and that maintainers can close PRs / Issues if they suspect undisclosed AI usage and that maintainers are exempt from those rules.

But let me know what you think.

@tekton-robot tekton-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 2, 2026
Simplify and strengthen the policy:
- Move core disclosure requirement to the top
- Add maintainer enforcement clause for suspected undisclosed AI use
- Add Ghostty AI policy to references

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester force-pushed the propose-ai-contribution-policy branch from 97b4c69 to ab96c64 Compare February 2, 2026 15:27
@vdemeester
Copy link
Member Author

Updated in a new commit @twoGiants

Copy link
Member

@twoGiants twoGiants left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the change! I like this version. It's concise and very clear. 😸 👍

/approve
/lgtm
/hold for other reviewers

@tekton-robot
Copy link
Contributor

@twoGiants: changing LGTM is restricted to collaborators

Details

In response to this:

Thank you for the change! I like this version. It's concise and very clear. 😸 👍

/approve
/lgtm
/hold for other reviewers

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2026
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, dibyom, twoGiants, waveywaves

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/documentation Categorizes issue or PR as related to documentation. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants