add AI Policy - #13550
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
suggestion: contributors should not propose PRs on issues which are not approved by maintainer (status/0-triage -> status/approved) |
Done @ndeloof |
| @@ -0,0 +1,74 @@ | |||
| # AI Usage Policy | |||
There was a problem hiding this comment.
Wonder if we should have a central location for this, so that we can link to it from other repositories. Possibly we could put it in https://github.com/docker/.github (which I THINK is meant for things like this).
There was a problem hiding this comment.
Possibly we could put it in https://github.com/docker/.github (which I THINK is meant for things like this).
Yes agreed
|
This issue has been automatically marked as not stale anymore due to the recent activity. |
Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
🟢 No issues found — LGTM! View logs.
|
|
||
| This is not an anti-AI stance - we use AI ourselves. This policy exists to maintain | ||
| code quality and protect maintainer time. See [AI_POLICY.md](AI_POLICY.md) for details. | ||
|
|
There was a problem hiding this comment.
Should we also explicitly call out contribution farming?
| ### No contribution farming | |
| Contribution farming is forbidden. Do not submit pull requests in an attempt to inflate contribution counts, build a public portfolio or gain repository activity rather than to improve the project. | |
| Examples include: | |
| - opening pull requests without verifying the problem or testing the proposed solution; | |
| - submitting unsolicited changes for problems that have not been reported; | |
| - splitting one logical change into multiple trivial pull requests without a clear motivation; | |
| - submitting mechanical, cosmetic, generated, or speculative changes without a concrete user or maintenance benefit. | |
| Maintainers may choose to close such submissions without detailed review or even ban contributors who repeatedly engage in this behavior. | |
| This rule is based on submission quality and behavior, not contributor experience or tool choice. First-time contributors and appropriately scoped small fixes are welcome when they address a real, verified problem or need. |
6 participants
What I did
Add AI policies to give clear notices about AI usage within Compose development
Inspired by Ghostty AI Policy
Related issue
N/A
(not mandatory) A picture of a cute animal, if possible in relation to what you did
