From 88336f549ba23defefdb8adc1f4c8a56d5d93e5e Mon Sep 17 00:00:00 2001
From: Adrian Edwards <adredwar@redhat.com>
Date: Mon, 8 Jun 2026 14:56:56 -0400
Subject: [PATCH 1/4] Copy GenAI disclosure template from 8Knot

Signed-off-by: Adrian Edwards <adredwar@redhat.com>
---
 .github/pull_request_template.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 437997d1d..3641b4b37 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -8,6 +8,21 @@ This PR fixes #
 **Signed commits**
 - [ ] Yes, I signed my commits.
 
+
+**Generative AI disclosure**
+<!-- To learn more about our Generative AI policy and required disclosures, see the `CONTRIBUTING.md` file -->
+
+Please select one option:
+
+- [ ] This contribution was NOT assisted or created by Generative AI tools.
+- [ ] This contribution was assisted or created by Generative AI tools.
+
+
+If AI tools were used, please provide details below:
+    - What tools were used? <!-- gemini / chatgpt / claude .etc -->
+    - How were these tools used? <!-- initial draft of the code / code review / writing tests .etc -->
+    - Did you review these outputs before submitting this PR? <!-- No / Yes and I made these fixes... -->
+
 <!--
 Thank you for contributing to CHAOSS projects! 
 

From 908f33c3c1a1967869fde62b1b5de9ab77e63f1b Mon Sep 17 00:00:00 2001
From: Adrian Edwards <adredwar@redhat.com>
Date: Mon, 8 Jun 2026 14:57:02 -0400
Subject: [PATCH 2/4] remove redundant PR template

Signed-off-by: Adrian Edwards <adredwar@redhat.com>
---
 .../PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md  | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 .github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 864f4af87..000000000
--- a/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-name: Pull Request
-about: Open a pull request. Please check your branch!
-
----
-## Changeset
-- This is a bulleted list of the changes you are suggesting. These should be high-level; think commit message  
-
-## Notes
-Add any notes about why you made these changes, note-worthy technical details or caveats for your implementation, next steps, etc. Be as descriptive as you can. 
-
-## Related issues/PRs
-- This is a bulleted list of any related issues/PRs; leave blank if there are none
\ No newline at end of file

From 76e3a6baa8c7debbc08941adf4b5a3e89ff0ee9b Mon Sep 17 00:00:00 2001
From: Adrian Edwards <adredwar@redhat.com>
Date: Mon, 8 Jun 2026 16:04:38 -0400
Subject: [PATCH 3/4] first pass at documenting the contribution standards

Signed-off-by: Adrian Edwards <adredwar@redhat.com>
---
 CONTRIBUTING.md | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ad19e84e3..f7651645c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -19,8 +19,22 @@ If you are new to opening issues, we recommend [opensource.guide](https://openso
 > [!TIP]
 > Filling our our issue templates will help us gather all the necessary information to troubleshoot your issue efficiently. Issues that are missing details may take longer to be fixed.
 
+## Contribution Standards
 
-## Contributing to the source code
+In order to maintain a high level of code quality, we have certain standards of behavior and contribution quality we expect from all contributors and contributions (regardless of whether those changes were made by hand or with tools).
+
+- **Discuss first, then code.** Open an issue, leave a comment, or reach out on Slack before submitting a PR (especially if its your first time). This creates an opportunity to get early feedback on your plan from the maintainers and allows you to check if the task has been claimed by someone else, avoiding wasted effort on both sides.
+- **Maintain situational awareness of your code and take responsibility.** The power to make changes to code that other people use requires taking responsibility. As a rule of thumb, if you can't explain why your change works or aren't prepared to answer follow-up questions from maintainers during review, consider picking a different issue to solve or asking maintainers for resources to help you learn the relevant concepts or details about the codebase.
+- **Be honest and upfront.** Honesty, integrity, and trust are an important part of how we maintain the quality of our codebase. We require that the sources be cited when they are not written by the author of the PR. This includes, but is not limited to: citing Stack Overflow when you copy and paste code, correctly attributing co-authorship on commits that are made collaboratively, and completing the AI disclosure and DCO portions of the PR template truthfully.
+- **Respect others time.** Project maintainers and other contributors may be volunteering their time to review your work, please be courteous and respect their time. If you can't respond to something for a few days, just say so! If your proposed changes (or any comments about them) are too long for you to proofread, they're likely too long for maintainers to read and should be reorganized or made smaller if possible.
+- **Remember the human.** Remember that the humans who are helping build this project are on the other side of your issues, commments, and Slack messages. Your words and actions should remain respectful, even if you disagree. Using inflammatory or hateful language is not acceptable. Simply outsourcing your workload to an LLM and relaying the output back doesn't help anyone grow and doesn't sustain our community.
+
+
+Following these standards when you contribute will help your contributions get merged faster. If a maintainer determines your change to be in violation of one of these standards, you will be informed and given an opportunity to correct your PR.
+
+Repeat violations of these standards may result in the closure of your PRs, a ban from the project, referral for CHAOSS Code of Conduct violations, or other remedies deemed by the maintainers to be in the best interests of the overall health of the project. 
+
+## How to contribute to the source code
 We welcome pull requests from anyone!
 
 We follow the same GitHub workflow that most other projects on GitHub follow: Fork -> create a branch -> make a pull request -> repeat.

From 666643432e61a5cbaf20253248bb1b3c192d601d Mon Sep 17 00:00:00 2001
From: Adrian Edwards <adredwar@redhat.com>
Date: Mon, 8 Jun 2026 16:05:57 -0400
Subject: [PATCH 4/4] fix typo

Signed-off-by: Adrian Edwards <adredwar@redhat.com>
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f7651645c..ad0ebd17d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -27,7 +27,7 @@ In order to maintain a high level of code quality, we have certain standards of
 - **Maintain situational awareness of your code and take responsibility.** The power to make changes to code that other people use requires taking responsibility. As a rule of thumb, if you can't explain why your change works or aren't prepared to answer follow-up questions from maintainers during review, consider picking a different issue to solve or asking maintainers for resources to help you learn the relevant concepts or details about the codebase.
 - **Be honest and upfront.** Honesty, integrity, and trust are an important part of how we maintain the quality of our codebase. We require that the sources be cited when they are not written by the author of the PR. This includes, but is not limited to: citing Stack Overflow when you copy and paste code, correctly attributing co-authorship on commits that are made collaboratively, and completing the AI disclosure and DCO portions of the PR template truthfully.
 - **Respect others time.** Project maintainers and other contributors may be volunteering their time to review your work, please be courteous and respect their time. If you can't respond to something for a few days, just say so! If your proposed changes (or any comments about them) are too long for you to proofread, they're likely too long for maintainers to read and should be reorganized or made smaller if possible.
-- **Remember the human.** Remember that the humans who are helping build this project are on the other side of your issues, commments, and Slack messages. Your words and actions should remain respectful, even if you disagree. Using inflammatory or hateful language is not acceptable. Simply outsourcing your workload to an LLM and relaying the output back doesn't help anyone grow and doesn't sustain our community.
+- **Remember the human.** Remember that the humans who are helping build this project are on the other side of your issues, comments, and Slack messages. Your words and actions should remain respectful, even if you disagree. Using inflammatory or hateful language is not acceptable. Simply outsourcing your workload to an LLM and relaying the output back doesn't help anyone grow and doesn't sustain our community.
 
 
 Following these standards when you contribute will help your contributions get merged faster. If a maintainer determines your change to be in violation of one of these standards, you will be informed and given an opportunity to correct your PR.