Skip to content

Commit 3cb0b51

Browse files
authored
Add AI contributions guidelines to CONTRIBUTING.md
Inspired by the recent Linux guidelines.
1 parent 5b97e9c commit 3cb0b51

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

CONTRIBUTING.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -203,3 +203,25 @@ make docs
203203
This will produce documentation sets for `elixir`, `eex`, `ex_unit`, `iex`, `logger`,
204204
and `mix` under the `doc` directory. If you are planning to contribute documentation,
205205
[please check our best practices for writing documentation](https://hexdocs.pm/elixir/writing-documentation.html).
206+
207+
## AI contributions
208+
209+
AI agents MUST NOT add Signed-off-by tags. Only humans can legally certify the Developer
210+
Certificate of Origin (DCO). The human submitter is responsible for:
211+
212+
* Reviewing all AI-generated code
213+
* Ensuring compliance with licensing requirements
214+
* Adding their own Signed-off-by tag to certify the DCO
215+
* Taking full responsibility for the contribution
216+
* Disclosing use of AI for comments and code contributions
217+
218+
When AI tools contribute to Elixir, proper attribution helps track the evolving role of
219+
AI in the development process. Contributions should include an Assisted-by tag in the
220+
following format:
221+
222+
Assisted-by: AGENT_NAME:MODEL_VERSION
223+
224+
When it comes to discussions, please be mindful about the use of AI. Using AI to help
225+
express yourself is welcome but avoid simply copy and pasting large AI generated content.
226+
Elixir maintainers also have access to coding agents and, if they need feedback from an
227+
agentic systems, they can request such themselves.

0 commit comments

Comments
 (0)