-
-
Notifications
You must be signed in to change notification settings - Fork 344
ci: add mandatory LLM-involvement category disclosure #2343
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
base: master
Are you sure you want to change the base?
Changes from all commits
b867c1c
1697368
4fd52a5
20a9376
04f7769
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,6 +9,11 @@ Unless otherwise specified, the following checkboxes are not mandatory, but | |
| drastically accelerate the reviewing and merging process of this PR. | ||
| --> | ||
| - [ ] <!-- MANDATORY --> I certify that I have the right to submit this contribution under the [MIT license](https://github.com/nix-community/stylix/blob/master/LICENSE) | ||
| - [ ] <!-- MANDATORY --> I have disclosed the single most severe LLM-involvement category that applies to this contribution: | ||
| - [ ] `llm: 0`: Manual: The absence of LLMs would result in equal results and quality | ||
| - [ ] `llm: 1`: Syntactic: Includes non-negligible LLM content | ||
| - [ ] `llm: 2`: Semantic: LLM involved in design decisions or core logic | ||
| - [ ] `llm: 3`: Unaudited: LLM output with little to no human verification | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should make it clear that is level of LLM involvement is not welcome in Stylix, as was agreed on in #2178.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
IMHO, the categorization is already fairly discriminatory towards LLM contributions, making it somewhat obvious that unaudited contributions are unwelcome. These are also rude submissions, but this is irrelevant to the LLM categorization. I wonder whether we will even receive submissions categorized as unaudited. Keep in mind that you are free to ignore such submissions or only very superficially interact with them. |
||
| - [ ] Commit messages adhere to [Stylix commit conventions](https://nix-community.github.io/stylix/commit_convention.html) | ||
| - [ ] Theming changes adhere to the [Stylix style guide](https://nix-community.github.io/stylix/styling.html) | ||
| - [ ] Changes have been [tested locally](https://nix-community.github.io/stylix/modules.html#development-setup) | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
llm: 0is very open to interpretation, where as the other three are significantly more clear. I would prefer havingllm: 0be non-existent LLM usage andllm: 1be any LLM usage,There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It intentionally has a faithfull loophole inspired by:
I suggest initially going with this, allowing competent contributors to faithfully disclose their LLM dependency because it seems well-regarded Nix maintainers use LLMs for minor things. Regardless of the label description, it is suspect to dishonesty that I suggest ignoring for now:
This also intentionally has a smaller loophole, allowing trivial use cases like LLMs fixing trivial syntax issues or suggesting the most idiomatic function to use. I suppose what this really entails will be clear once we see how people interpret this.
I see your point of more explicitly disclosing LLM contributions, but I suggest going with this for now and later determining how much people abuse these faithfull definitions.