CONTRIBUTING.md: elaborate LLM policy and add copy of LLVM's LLM policy #193
Conversation
I copied the LLVM policy wholesale. I considered search-and-replacing LLVM with "rust-simplicity" or "Simplicity" or something but this seemed like a lot of tedious work that would need to be repeated slightly-differently for every repo, and which wouldn't add much value.
apoelstra
force-pushed
the
2026-01/ai-policy
branch
from
00d9fa0 to
1943fe9
Compare
| This PR appears to be extractive, and requires additional justification for | ||
| why it is valuable enough to the project for us to review it. Please see | ||
| our developer policy on AI-generated contributions: | ||
| http://llvm.org/docs/AIToolPolicy.html |
There was a problem hiding this comment.
Heh, interesting. If you are feeling motivated, you could file an issue on github.com/rnk/llvm-project -- this comes from https://raw.githubusercontent.com/rnk/llvm-project/refs/heads/tool-policy/llvm/docs/AIToolPolicy.md and I didn't want to modify it because then I'd have to add a header describing my modifications.
There was a problem hiding this comment.
Left a comment here: llvm/llvm-project#154441 (comment)
There was a problem hiding this comment.
This link is supposed to be linking to this document itself, and should refer to the SimpliciytHL repo.
uncomputable
left a comment
uncomputable
left a comment
There was a problem hiding this comment.
ACK 1943fe9 The policy looks good besides one dead link
|
Added a commit clarifying that it's fine to use LLMs for machine translation or grammar improvements. |
|
ACK 3ef0434 |
5 participants
I copied the LLVM policy wholesale.
I considered search-and-replacing LLVM with "rust-simplicity" or "Simplicity" or something but this seemed like a lot of tedious work that would need to be repeated slightly-differently for every repo, and which wouldn't add much value.