"Proof of use" as a requirement for open source contributions?
0 comments · ai, ask, culture
- Comments22
0 comments · ai, ask, culture
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…
Story details from Lobsters ↗.
"Proof of use" as a requirement for open source contributions? was first seen on Lobsters · Hottest on Nov 17, 2026. Since then it has appeared in 40 checks on 2 different days. Its best position was #12 of 25, reached on Nov 17, 06:51 UTC. It dropped off the list after Nov 18, 15:51 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
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.
Well, as a maintainer, I will then be glad not to have merged your patch. Because merging the patch is more than often not about the code written. As a maintainer, it would probably takes me less time to implement your patch myself the way I want it than to review your patch (let’s be honest, most first time…
I mean it's your project. But if I use it and report a bug, and even go to the lengths of providing a patch and it gets rejected with this, chances are good you'll never see me again except complaining about your project. Of course this might be worth it. But I'm relatively sure you'll remove most of the "trying to…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 18, 15:51 UTC, after 2 days of trending.
#12 on Lobsters · Hottest, on Nov 17, 06:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 17, 2026 and has been on the list on 2 days (40 checks) since.