"Proof of use" as a requirement for open source contributions?

34 points by twp


As an open source maintainer, I get a lot of AI slop PRs. Some of these have genuine value. Most address edge cases that almost never occur in real life. It's not that they're not fixing real problems, it's that they're fixing problems that nobody is ever likely to encounter.

I'm experimenting with "proof of use" as a requirement for submissions. Specifically, you need to show me that your project that depends on my project before I'll look at your PR.

"Proof of use" can be an existing open source project that imports mine (show me the git history!) or a clear description starting with "in our closed source project in production, we found that...".

The specific problem that I want to address is ensuring that contributions from people genuinely depending on my software are handled, while filtering out the OpenClaw/Github green square farming/drive-by LLM noise.

What are lobste.rs's thoughts on this?

valpackett

Alternative way to reduce green square farming is to not be on GitHub (or only be there as a read-only mirror), but rather on Codeberg or another less-mainstream more community-values-oriented host. But that sounds like a fine thing to put in CONTRIBUTING.md, sure.