From 7372850a1e06a76523c3ea986617cf2521da6b05 Mon Sep 17 00:00:00 2001 From: Evie Gauthier Date: Fri, 20 Mar 2026 10:43:34 -0400 Subject: [PATCH 1/5] docs: pro-AI contribution policy; add AI disclosure level to PR template --- .github/PULL_REQUEST_TEMPLATE.md | 11 ++++++++++- CONTRIBUTING.md | 14 ++++++++------ 2 files changed, 18 insertions(+), 7 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index d481c26ba..1e8cffc2c 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,4 +1,4 @@ - + ### Description @@ -13,6 +13,15 @@ Fixes # - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update +#### AI assistance level + + + +- [ ] **None** — No AI tools were used +- [ ] **Research only** — AI used for research, brainstorming, or understanding existing code; no generated code included +- [ ] **AI-assisted** — AI suggested code or logic that I reviewed, tested, and understand fully; I can explain every change +- [ ] **Primarily AI-generated** — The majority of code was AI-generated; I have thoroughly reviewed it, verified correctness, and made it my own + ### Checklist: - [ ] My code follows the style guidelines of this project diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c417e2071..56466f324 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,17 +47,19 @@ Also, we use [ESLint](https://eslint.org/) for clean and stylistically consisten If your change touches logic with testable behaviour, please include tests. See [docs/TESTING.md](./docs/TESTING.md) for a guide on how to write them. -## Restrictions on Generative AI Usage +## AI-Assisted Development -We expect and appreciate authentic engagement in our community. +We welcome AI-assisted contributions. Tools like GitHub Copilot, Cursor, Claude, ChatGPT, and others are legitimate parts of a modern development workflow, and we don't ask you to hide their use. -Do not post output from Large Language Models or similar generative AI as comments on GitHub, as such comments tend to be formulaic and low content. +That said, **you own everything you submit.** AI is a tool, not a co-author. Before opening a pull request: -If you use generative AI tools as an aid in developing code, ensure that you fully understand the proposed changes and can explain why they are the correct approach. +- **Understand every change.** You must be able to explain why each line is correct and is the right approach for this codebase. If you can't, keep iterating. +- **Review generated code critically.** AI tools make mistakes — logic errors, outdated API usage, subtle security issues. Don't submit code you haven't read carefully. +- **Add genuine value.** Wrapping a prompt in a PR without understanding or verifying the output is not a contribution. Maintainers can tell the difference and will close PRs that don't meet the bar. -Make sure you have added value based on your personal competency to your contributions. Just taking some input, feeding it to an AI and posting the result is not of value to the project. We reserve the right to rigorously reject seemingly AI generated low-value contributions. +When opening a pull request, **disclose your level of AI use** using the checklist in the PR template. This isn't gatekeeping — it's transparency that helps reviewers calibrate their review depth. A heavily AI-generated PR will get more scrutiny; that's expected and fine. -Maintainers may close issues and PRs that are not useful or productive, including those that are fully generated by AI. If a contributor repeatedly opens unproductive issues or PRs, they may be blocked. +GitHub comments and issue discussions should still be your own words. Don't paste LLM output as a comment — it's easy to spot and adds no signal. ## Release notes and versioning (Knope) From 96f9d7ee83b6e5baee0f0a2559a10d541451a4bb Mon Sep 17 00:00:00 2001 From: Evie Gauthier Date: Fri, 20 Mar 2026 10:47:28 -0400 Subject: [PATCH 2/5] chore: add changeset --- .changeset/docs-ai-contribution-policy.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .changeset/docs-ai-contribution-policy.md diff --git a/.changeset/docs-ai-contribution-policy.md b/.changeset/docs-ai-contribution-policy.md new file mode 100644 index 000000000..7b792ccfa --- /dev/null +++ b/.changeset/docs-ai-contribution-policy.md @@ -0,0 +1,5 @@ +--- +default: docs +--- + +Update contribution guidelines with pro-AI development stance and add AI disclosure level to PR template. From c8a368d32c9a864beba3a72995755050b36efb1a Mon Sep 17 00:00:00 2001 From: Evie Gauthier Date: Fri, 20 Mar 2026 11:15:39 -0400 Subject: [PATCH 3/5] Update AI-assisted contribution guidelines Clarified guidelines on AI-assisted contributions, emphasizing transparency in AI usage. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 56466f324..54cd2fcbb 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -49,7 +49,7 @@ If your change touches logic with testable behaviour, please include tests. See ## AI-Assisted Development -We welcome AI-assisted contributions. Tools like GitHub Copilot, Cursor, Claude, ChatGPT, and others are legitimate parts of a modern development workflow, and we don't ask you to hide their use. +We welcome AI-assisted contributions. Tools like GitHub Copilot, Cursor, Claude, ChatGPT, and others are legitimate parts of a modern development workflow. We ask that you do not hide AI usage in your contributions. Doing so is an actionable offence. That said, **you own everything you submit.** AI is a tool, not a co-author. Before opening a pull request: From 50c1935749db85f1d02d786f35c1f3ede8a2ba73 Mon Sep 17 00:00:00 2001 From: Evie Gauthier Date: Fri, 20 Mar 2026 11:55:14 -0400 Subject: [PATCH 4/5] docs: revert to original AI policy wording + add PR template disclosure note --- CONTRIBUTING.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 54cd2fcbb..3da5a3b0c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,19 +47,19 @@ Also, we use [ESLint](https://eslint.org/) for clean and stylistically consisten If your change touches logic with testable behaviour, please include tests. See [docs/TESTING.md](./docs/TESTING.md) for a guide on how to write them. -## AI-Assisted Development +## Generative AI Usage -We welcome AI-assisted contributions. Tools like GitHub Copilot, Cursor, Claude, ChatGPT, and others are legitimate parts of a modern development workflow. We ask that you do not hide AI usage in your contributions. Doing so is an actionable offence. +We expect and appreciate authentic engagement in our community. -That said, **you own everything you submit.** AI is a tool, not a co-author. Before opening a pull request: +Do not post output from Large Language Models or similar generative AI as comments on GitHub, as such comments tend to be formulaic and low content. -- **Understand every change.** You must be able to explain why each line is correct and is the right approach for this codebase. If you can't, keep iterating. -- **Review generated code critically.** AI tools make mistakes — logic errors, outdated API usage, subtle security issues. Don't submit code you haven't read carefully. -- **Add genuine value.** Wrapping a prompt in a PR without understanding or verifying the output is not a contribution. Maintainers can tell the difference and will close PRs that don't meet the bar. +If you use generative AI tools as an aid in developing code, ensure that you fully understand the proposed changes and can explain why they are the correct approach. -When opening a pull request, **disclose your level of AI use** using the checklist in the PR template. This isn't gatekeeping — it's transparency that helps reviewers calibrate their review depth. A heavily AI-generated PR will get more scrutiny; that's expected and fine. +Make sure you have added value based on your personal competency to your contributions. Just taking some input, feeding it to an AI and posting the result is not of value to the project. We reserve the right to rigorously reject seemingly AI generated low-value contributions. -GitHub comments and issue discussions should still be your own words. Don't paste LLM output as a comment — it's easy to spot and adds no signal. +Maintainers may close issues and PRs that are not useful or productive, including those that are fully generated by AI. If a contributor repeatedly opens unproductive issues or PRs, they may be blocked. + +When opening a pull request, disclose your level of AI use using the checklist in the PR template. This isn't gatekeeping — it's transparency that helps reviewers calibrate their review depth. A heavily AI-generated PR will get more scrutiny; that's expected and fine. ## Release notes and versioning (Knope) From 2bb507de583f1db74c0c5e8adeea49e3da727cee Mon Sep 17 00:00:00 2001 From: Evie Gauthier Date: Fri, 20 Mar 2026 13:43:08 -0400 Subject: [PATCH 5/5] Update PR template to include AI disclosure level --- .changeset/docs-ai-contribution-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.changeset/docs-ai-contribution-policy.md b/.changeset/docs-ai-contribution-policy.md index 7b792ccfa..85e1cc88a 100644 --- a/.changeset/docs-ai-contribution-policy.md +++ b/.changeset/docs-ai-contribution-policy.md @@ -2,4 +2,4 @@ default: docs --- -Update contribution guidelines with pro-AI development stance and add AI disclosure level to PR template. +Update PR template to add AI disclosure level.