-
Notifications
You must be signed in to change notification settings - Fork 104
Add policy for generative artificial intelligence #408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+115
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,115 @@ | ||
| # Cilium Generative AI Policy | ||
|
|
||
| To maintain the high quality and trustworthiness of contributions to the Cilium | ||
| community, we provide the following guidance on the use of "Generative | ||
| Artificial Intelligence", including large language models (LLMs), GitHub | ||
| Copilot, ChatGPT, Codex, Claude code, or similar tools ("Generative AI"). The | ||
| guidance in this document is intended for all contributors to the community. As | ||
| a Linux Foundation project, Cilium is also subject to the Linux Foundation | ||
| [Guidance Regarding Use of Generative AI Tools]. The guidance in this document | ||
| is intended to support you as a contributor in addition to the Linux Foundation | ||
| guidance. | ||
|
|
||
| ## Guiding Principle | ||
|
|
||
| Cilium is a community-driven organization that values expertise, clear | ||
| communication, and personal responsibility. The community prides itself on a | ||
| commitment to high quality and trust amongst its members. To maintain this in | ||
| the AI era, we follow a key principle: | ||
|
|
||
| **What you do with Generative AI reflects on you**. | ||
|
|
||
| Successful ongoing contribution to this community is contingent on building | ||
| trust with the members of the organization through ongoing collaboration. | ||
| Whether or not Generative AI tools were involved, you are fully accountable for | ||
| the correctness, security, and clarity of your contributions. Human review is | ||
| required for all code, including code generated or assisted by Generative AI | ||
| tools. If you contribute regularly, other contributors will become familiar | ||
| with your work, so we request that you mindfully consider the impact that your | ||
| use of Generative AI may have on other community members. | ||
|
|
||
| ## Acceptable Use | ||
|
|
||
| We recognize that Generative AI can be a helpful _tool_, for example you may | ||
| use it to: | ||
|
|
||
| - Explain parts of the codebase you don’t understand; | ||
| - Auto-complete routines or boilerplate code (such as error handling, test | ||
| scaffolding, function signatures); | ||
| - Reformat or refactor existing content; | ||
| - Brainstorm ideas for implementation cases, but write the actual code yourself; | ||
| - Draft test cases which you subsequently review, revise and simplify before | ||
| submission; or | ||
| - Analyze your own content submissions. | ||
|
|
||
| These uses are acceptable provided you: | ||
|
|
||
| - Are involved in the entire process for creating the contributions; | ||
| - Personally review and edit generated content before you submit it to the | ||
| organization; | ||
| - Fully understand and review the content prior to submission; | ||
| - Take personal responsibility for the content, in the same way as if you | ||
| authored the content without using Generative AI; | ||
| - Ensure the output adheres to project guidelines and licensing requirements; and | ||
| - Report the use of Generative AI tools for non-trivial preparation of | ||
| submissions (that is, at level 2 or higher on the [AI Influence Level]). | ||
|
|
||
| ## Unacceptable Use | ||
|
|
||
| It is not acceptable to use Generative AI tools to: | ||
|
|
||
| - Communicate in any Cilium community space with content that is substantially | ||
| written using Generative AI tools. For example, it is not acceptable to send | ||
| such text on Slack or GitHub, whether initiating or responding to discussion | ||
| with other community members. | ||
| - Submit code, documentation, or discussion content that you have not reviewed | ||
| in careful detail, including testing the content where applicable. | ||
| - Rely solely or primarily on Generative AI output for technical problem | ||
| solving, architectural decision making. | ||
| - Submit work produced via Generative AI tooling that copies from external | ||
| sources without correct attribution or licensing. | ||
| - Submit contributions where you cannot explain, contextualize, or justify the | ||
| submission as part of review. | ||
|
|
||
| ## Generative AI for Translation | ||
|
|
||
| If you are interacting in a Cilium community space which primarily uses a | ||
| language which you are not fluent in, community members will generally | ||
| appreciate your attempts to express your ideas in that language without the use | ||
| of Generative AI tools. However, we recognize that contributors from around the | ||
| world may want to participate in discussion in the Cilium community, and the | ||
| community can benefit from those discussions even if Generative AI is used to | ||
| facilitate those discussions. When communicating in a language you are not | ||
| confident in, consider drafting your intended response and attempt to convey | ||
| your ideas in the target language first. If you believe the ideas are not | ||
| conveyed clearly, consider using translation tools (either non-generative or | ||
| generative). Be aware that if you rely significantly on Generative AI for | ||
| translation, this itself may inhibit communication due to limitations in | ||
| Generative AI tooling. | ||
|
|
||
| ## Transparency & Attribution | ||
|
|
||
| We generally expect contributors to declare when Generative AI was used to | ||
| prepare a submission. For non-trivial text or code submissions (such as new | ||
| features, documentation pages, complex design proposals), you should describe | ||
| how Generative AI was used and explain the human review process applied. For | ||
| trivial use of Generative AI (such as spelling check or simple autocomplete) | ||
| you are not expected to declare use. Suspected use of Generative AI tooling | ||
| without transparency may lead to submissions being closed or rejected without | ||
| discussion. | ||
|
|
||
| ## DCO and Licensing | ||
|
|
||
| The [Developer Certificate of Origin] (DCO) is required for contributions to | ||
| the Cilium organization. AI tools often lack transparency into their training | ||
| data and may produce output with pre-existing copyright. If you submit | ||
| AI-assisted contributions, you are personally certifying that you have the | ||
| right to contribute the content under the project's license. The Linux | ||
| Foundation [Guidance Regarding Use of Generative AI Tools] provides a more | ||
| detailed description of your obligations as a contributor. If you’re unsure | ||
| about the licensing of code you created using Generative AI tools, | ||
| **don’t submit it**. | ||
|
|
||
| [AI Influence Level]: https://danielmiessler.com/blog/ai-influence-level-ail | ||
| [Developer Certificate of Origin]: https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin | ||
| [Guidance Regarding Use of Generative AI Tools]: https://www.linuxfoundation.org/legal/generative-ai | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.