"Proof of use" as a requirement for open source contributions?
Post · https://lobste.rs/s/ki1l5r
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?
First seen by Oriel on .
No saved summary available.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 17, latest observation ; +12 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 6, latest observation ; +6 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | ki1l5r | https://lobste.rs/s/ki1l5r/proof_use_as_requirement_for_open_source Read discussion |