cfengine · olehermanse · Oct 2, 2025 · Oct 2, 2025 · larsewi · Oct 2, 2025
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -55,6 +55,17 @@ When submitting your pull request, please make sure you:
 * Become familiar with the *Northern.tech AS Contributor statement* as described
   in the [*AUTHORS*](./AUTHORS) file.
 
+### Use of AI/LLMs in contributions
+
+We allow the use of AI in source code and documentation contributions, subject to the following rules:
+
+- You must review, understand, and, if necessary, correct the source code output when using an LLM.
+  We don’t want submissions purely generated and submitted by automated AI systems without any human ensuring that it is correct and valid.
-  We don’t want submissions purely generated and submitted by automated AI systems without any human ensuring that it is correct and valid.
+  We don’t want submissions purely generated and submitted by automated AI systems without any human oversight to ensure that they are correct and valid.
-  We don’t want submissions purely generated and submitted by automated AI systems without any human ensuring that it is correct and valid.
+  We don’t want submissions purely generated and submitted by automated AI systems without any human oversight to ensure that they are correct and valid.
+  And we don’t want to put this review burden solely on our reviewers.
-  And we don’t want to put this review burden solely on our reviewers.
+  We also don’t want to place this review burden solely on our reviewers.
-  And we don’t want to put this review burden solely on our reviewers.
+  We also don’t want to place this review burden solely on our reviewers.
+- We have the same expectation of quality for source code whether AI was used or not (including security, readability, maintainability, correctness, commit history, etc.).
- We have the same expectation of quality for source code whether AI was used or not (including security, readability, maintainability, correctness, commit history, etc.).
+- We have the same expectation of quality for source code, whether AI was used or not (including security, readability, maintainability, correctness, commit history, etc.).
- We have the same expectation of quality for source code whether AI was used or not (including security, readability, maintainability, correctness, commit history, etc.).
+- We have the same expectation of quality for source code, whether AI was used or not (including security, readability, maintainability, correctness, commit history, etc.).
+- When AI is used as part of writing / editing some code, we consider the person using the AI as a tool, fact-checking / editing its output and ultimately submitting the code as a pull request to be the author.
- When AI is used as part of writing / editing some code, we consider the person using the AI as a tool, fact-checking / editing its output and ultimately submitting the code as a pull request to be the author.
+- When AI is used as part of writing / editing source code, we consider the person using the AI (as a tool), to be the author.
- When AI is used as part of writing / editing some code, we consider the person using the AI as a tool, fact-checking / editing its output and ultimately submitting the code as a pull request to be the author.
+- When AI is used as part of writing / editing source code, we consider the person using the AI (as a tool), to be the author.
+- When using AI, your use must be in compliance with applicable laws and terms, such as the EU AI Act, as well as the terms of service and acceptable use policy of your AI provider.
+- We may change these rules in the future as AI tools and regulation develop.
- We may change these rules in the future as AI tools and regulation develop.
+- We may change these rules in the future as AI tools and regulations develop.
- We may change these rules in the future as AI tools and regulation develop.
+- We may change these rules in the future as AI tools and regulations develop.
 
 ### Pull request title and description