Skip to content

πŸ“˜ πŸ›οΈ Decide on AI contribution policy and document itΒ #449

@e-lo

Description

@e-lo

As a contributor and reviewer, I'd like to know what our policy is w.r.t. use of AI in code submissions and if and how AI was used in the development of code submitted by a pull request in order to know how to evaluate contributions.

Question for discussion: If/how should we limit code submissions from AI?

Some thoughts:

  • Some projects with high throughput limit any contributions by AI - for very good reasons as it turns out.
  • We don't have very high throughput
  • We DO want to make sure we aren't adding slop and that the codebase is legible and managable

Straw-person policy:

AI-assisted contributions are welcome, but contributors are expected to thoroughly review, understand, and stand behind any AI-generated code or text as if they had written it themselves. Ensure all tests pass and that any new or AI-generated tests actually validate meaningful behavior β€” not just satisfy coverage metrics or placate a linter. Low-quality or poorly-understood contributions will be closed without extended discussion.

Metadata

Metadata

Assignees

Labels

docsDocumentation only changes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions