From 5397418dd6fc698cc973ee6d374b5633ac412cff Mon Sep 17 00:00:00 2001 From: Gerrit Date: Thu, 19 Feb 2026 09:34:28 +0100 Subject: [PATCH 1/2] Add AI tools paragraph to contribution guideline. --- docs/contributing/03-contribution-guideline.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/contributing/03-contribution-guideline.md b/docs/contributing/03-contribution-guideline.md index 2c0526e3..22bcb1d9 100644 --- a/docs/contributing/03-contribution-guideline.md +++ b/docs/contributing/03-contribution-guideline.md @@ -37,6 +37,18 @@ The process described here has several goals: 1. Create a meaningful description of the pull request or reference the related issue. The pull request template explains what the content should include, please read it. 1. Ask for merging your contribution by removing the draft marker. Repository maintainers (see [Code Ownership](#code-ownership)) are notified automatically, but you can also reach out to people directly on Slack if you want a review from a specific person. +## Usage of Generative AI Tools + +The metal-stack project generally accepts contributions that make use of generative AI tools. We believe that AI can increase productivity and improve quality when developers use it *consciously*. Using this technology unconsciously, however, comes with risks for the project and the community, which is why we expect contributors to respect the following aspects for AI-generated contents: + +- Copyright: The contributor is responsible for the disclosed sources and ensures that it complies with the Open Source definition and regulations of the metal-stack project. +- Communication: Comments, motivations and issues are genuinely written by humans. +- Transparency: Commits where substantial parts were generated by AI must include: + - Commit labels for the review process, like: `Generated-By: [tool name] ` . + - The names of the tools that were used with AI should be included in the pull request description. For this, you can find a snippet in the pull request template. As we usually squash commits when we merge, the commit labeling described above is not sufficient. +- Code Understanding: We expect full understanding of the contributed code. The code must have been executed and tested in some way by the contributor. The contribution guideline's overall style and design choices must be followed. +- Quality over Quantity: It is very easy to generate a lot of code with the help of AI in a very short amount of time. By contrast, reviewing large pull requests takes exponentially longer as they grow in size. Therefore, contributions are expected to be minimal. Large changes must be discussed in issues as usual and discussed in the community. + ## General Objectives This section contains language-agnostic topics that all metal-stack projects are trying to follow. From 52a128e80020ffca3524914d2ab72b543dc609b4 Mon Sep 17 00:00:00 2001 From: Gerrit Date: Thu, 19 Feb 2026 10:36:30 +0100 Subject: [PATCH 2/2] Rename copyright point to compliance. --- docs/contributing/03-contribution-guideline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/03-contribution-guideline.md b/docs/contributing/03-contribution-guideline.md index 22bcb1d9..8c2c3b94 100644 --- a/docs/contributing/03-contribution-guideline.md +++ b/docs/contributing/03-contribution-guideline.md @@ -41,7 +41,7 @@ The process described here has several goals: The metal-stack project generally accepts contributions that make use of generative AI tools. We believe that AI can increase productivity and improve quality when developers use it *consciously*. Using this technology unconsciously, however, comes with risks for the project and the community, which is why we expect contributors to respect the following aspects for AI-generated contents: -- Copyright: The contributor is responsible for the disclosed sources and ensures that it complies with the Open Source definition and regulations of the metal-stack project. +- Compliance: The contributor is responsible for the disclosed sources and ensures that it complies with the Open Source definition, copyright and license regulations of the metal-stack project. - Communication: Comments, motivations and issues are genuinely written by humans. - Transparency: Commits where substantial parts were generated by AI must include: - Commit labels for the review process, like: `Generated-By: [tool name] ` .