Skip to content

Carve out a space for experimentation#1

Open
jyn514 wants to merge 5 commits intollm-policyfrom
experimentation
Open

Carve out a space for experimentation#1
jyn514 wants to merge 5 commits intollm-policyfrom
experimentation

Conversation

@jyn514
Copy link
Copy Markdown
Owner

@jyn514 jyn514 commented Apr 28, 2026

No description provided.

Comment thread src/policies/llm-usage.md
- ℹ️ Be cautious about PRs that consist solely of trivial changes.
See also [the compiler team's typo fix policy](https://rustc-dev-guide.rust-lang.org/contributing.html#writing-documentation:~:text=Please%20notice%20that%20we%20don%E2%80%99t%20accept%20typography%2Fspellcheck%20fixes%20to%20internal%20documentation).
- Solicited, non-critical, high-quality, well-tested, and well-reviewed code changes that are originally authored by an LLM.
1. "Solicited" means that a reviewer has communicated *ahead of time* that they are willing to review an LLM-authored PR.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is broader than I expected - which I'm fine with if you think it would have support.

I expected that agreement with a maintainer would be required, as you've written here, but also that the maintainer would need to check with the relevant teams first if they wanted to experiment with LLM-involved contributions in an area/project they're working on (that might not even involve a non-project member, it could just be between some project maintainers). I figured it would be less ad-hoc than "we're explicitly trying something out in this corner to see how that goes and how it affects us".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants