No-Slop OSS, a checklist of contribution best practices when using AI (or not)
No-Slop OSS is a checklist of best practices for open-source contributions, covering guidelines for using AI-generated code as well as general contribution hygiene.
Background
- "Slop" is a pejorative term for low-quality, mass-produced, or carelessly generated content — often associated with AI output that hasn't been reviewed or refined. "No-Slop OSS" is a community checklist or manifesto urging open-source contributors (whether using AI or not) to follow basic quality, hygiene, and documentation standards.
- The repository (by user omkar-foss) offers a list of best practices — e.g., writing clear commit messages, avoiding junk files, reviewing AI-generated code before submitting, and keeping project history clean — aimed at reducing the maintenance burden on open-source projects.
- It matters because open-source maintainers are often overworked volunteers; unchecked AI-generated pull requests can flood projects with low-effort contributions that waste reviewers' time. The checklist is a response to the rise of AI coding assistants (like GitHub Copilot) that make it easy to generate code — and equally easy to generate "slop."
- The context is the ongoing debate in open-source communities about how to responsibly use AI tools without degrading project quality or disrespecting maintainers.