mirror of
https://github.com/docker/compose.git
synced 2026-11-19 14:40:08 +00:00
docs(ai-policy): tighten policy per PR #13550 review feedback
thaJeztah, vvoland, and crazy-max raised several gaps during review: AI co-author trailers don't belong in commits (disclosure belongs in the PR description), unreviewed AI replies and wall-of-text issues waste maintainer time, and unrelated-code scope creep and contribution farming weren't called out anywhere. Addresses review comments on docker/compose#13550. Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
This commit is contained in:
parent
f3d5954c38
commit
a9df37eb5e
3 changed files with 43 additions and 5 deletions
|
|
@ -45,6 +45,9 @@ All agents must conform to [AI_POLICY.md](AI_POLICY.md).
|
|||
|
||||
## Issue and PR Guidelines
|
||||
|
||||
- Keep changes scoped to the task. If you're fixing a bug, fix the bug -
|
||||
don't refactor unrelated code, fix unrelated typos, or reformat files you
|
||||
didn't need to touch. Put unrelated improvements in a separate PR.
|
||||
- Never create an issue or pull request without the user's explicit instruction.
|
||||
- If a user asks you to create a pull request on their behalf, add a file named
|
||||
`AI_AGENT_DISCLOSURE.md` to the change containing the text below followed by
|
||||
|
|
|
|||
21
AI_POLICY.md
21
AI_POLICY.md
|
|
@ -34,11 +34,22 @@ Docker Compose has clear rules for AI-assisted contributions:
|
|||
`make fmt` before submitting.
|
||||
|
||||
- **Issues and discussions can use AI assistance but must have a full
|
||||
human-in-the-loop.** This means that any content generated with AI
|
||||
must have been reviewed _and edited_ by a human before submission.
|
||||
AI is very good at being overly verbose and including noise that
|
||||
distracts from the main point. Humans must do their research and
|
||||
trim this down.
|
||||
human-in-the-loop.** Any content generated with AI must be reviewed
|
||||
_and edited_ by a human before submission - never post a raw agent
|
||||
reply ("Excellent observation, thank you...") without reading and
|
||||
rewriting it yourself. AI is very good at being overly verbose and
|
||||
including noise that distracts from the main point; if there's
|
||||
genuinely useful detail worth keeping, lead with a short summary and
|
||||
put the rest in a collapsible `<details>` section instead of making
|
||||
maintainers read a wall of text to figure out if something is
|
||||
actionable.
|
||||
|
||||
- **Don't add AI attribution to commit messages.** A
|
||||
`Co-Authored-By: <AI tool>` trailer belongs on the commit only if a
|
||||
human co-authored it; the tool you used to write the code isn't a
|
||||
co-author. Disclose the AI tool and how it was used in the PR
|
||||
description instead (see above) - the person opening the PR signs
|
||||
off on and owns the commit regardless of what wrote it.
|
||||
|
||||
- **A merged contribution is not a one-shot event.** If your change surfaces
|
||||
a regression, a follow-up review comment, or a question after merge, we
|
||||
|
|
|
|||
|
|
@ -17,6 +17,7 @@ start participating.
|
|||
- [Reporting other issues](#reporting-other-issues)
|
||||
- [Quick contribution tips and guidelines](#quick-contribution-tips-and-guidelines)
|
||||
- [AI-assisted contributions](#ai-assisted-contributions)
|
||||
- [No contribution farming](#no-contribution-farming)
|
||||
- [Pull requests are always welcome](#pull-requests-are-always-welcome)
|
||||
- [Talking to other Docker users and contributors](#talking-to-other-docker-users-and-contributors)
|
||||
- [Conventions](#conventions)
|
||||
|
|
@ -95,6 +96,29 @@ ignore this policy may be banned from the repository.
|
|||
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.
|
||||
|
||||
### 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.
|
||||
|
||||
### Pull requests are always welcome
|
||||
|
||||
Not sure if that typo is worth a pull request? Found a bug and know how to fix
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue