Skip to content

Commit d40a56e

Browse files
authored
Require disclosure of tool (e.g. LLM) usage to generate code (#8625)
* Require disclosure of tool (e.g. LLM) usage to generate code Vibe coding is a hot topic. In our experience, it doesn't produce acceptably-good code right now, but it is steadily improving, so we probably need a policy on it. Following a discussion in the dev meeting, we feel that it's fine to use tools like LLMs to generate Halide PRs. They will be held to the same standard as any other PR. The human that opens the PR will be treated as responsible for the code. In fact, we already have a history of accepting tool-generated code (some simplifier rules were discovered by superoptimization). However, we decided contributors must disclose the tools used in any significantly-tool-generated code, for a few reasons. 1) You shouldn't claim credit for something you didn't do. 2) It affects how a reviewer will review the code (e.g. what kind of bugs they will look for). 3) In a variety of possible future scenarios, it may be useful to know which commits were substantially authored by these tools. The credit issue makes it worthy of insertion into the code of conduct. * Update CODE_OF_CONDUCT.md Explicitly request "co-authored-by" tag
1 parent 0b2b6b7 commit d40a56e

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

CODE_OF_CONDUCT.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,11 @@ that end, we have a few ground rules that we ask people to adhere to:
5252
- **Give credit where it's due.** If you use code or ideas from other people,
5353
projects, or publications, say so. Add a comment in the source code at the
5454
point where the idea is used. If adapting code, this requirement is above and
55-
beyond any requirements placed on you by the license of the original code. We
56-
all like recognition for our work. To that end...
55+
beyond any requirements placed on you by the license of the original code.
56+
Additionally, any code generated by an AI tool (such as a large language model)
57+
must be clearly identified as such in the commit message using
58+
"Co-authored-by: The name of the tool". We all like recognition for our work.
59+
To that end...
5760

5861
**Acknowledgements.** This code of conduct is a mix of
5962
[LLVM's](https://llvm.org/docs/CodeOfConduct.html) and

0 commit comments

Comments
 (0)