I think this is a really solid move. This gives OSS contributors a lot of flexibility. You could set the limit to 0, and manually add contributors. You could set it to 1-3 to allow people to get their foot in the door. But the de facto limit today is infinite, which is spammed. Imagine if GMail did this! If I don't whitelist or reply within `n` emails, youre done. I would KILL for that.
I think, amusingly, the right thing to do for most open-source projects is to have each pull request summary and code read by an agent that just reimplements itself from a description of what the code is intended to be. Other people's code is not particularly valuable anymore.
There are some projects where you can provide a PR and they'll just reimplement and I think that's probably adaptive to the world where PR's are cheap and reviews are expensive.
There is also the solution of: No merge requests, just feature wishes and bug reports. All code is written solely by the maintainers (with the help of LLMs).
I think this is a really solid move. This gives OSS contributors a lot of flexibility. You could set the limit to 0, and manually add contributors. You could set it to 1-3 to allow people to get their foot in the door. But the de facto limit today is infinite, which is spammed. Imagine if GMail did this! If I don't whitelist or reply within `n` emails, youre done. I would KILL for that.
I get a lot of emails that I want to get but never reply to. I would not want to have to remember to whitelist all of those.
Yeah fair, then you could set it higher, even 100. Or default it off.
Oh stop, the noise is apart of your business model to stay relevant.
how so?
I think, amusingly, the right thing to do for most open-source projects is to have each pull request summary and code read by an agent that just reimplements itself from a description of what the code is intended to be. Other people's code is not particularly valuable anymore.
There are some projects where you can provide a PR and they'll just reimplement and I think that's probably adaptive to the world where PR's are cheap and reviews are expensive.
Thats just a coding agent the "peopple" use via you, with extra steps.
There is also the solution of: No merge requests, just feature wishes and bug reports. All code is written solely by the maintainers (with the help of LLMs).
Add a mechanism to donate tokens towards the maintainers' LLMs for a particular ticket and this whole class of problems will be resolved all at once.
And creates a new class of problems. Why not just fork the project and modify it yourself at that point, and cut out the maintainer middleman.
> Add a mechanism to donate tokens
Or donate money. Crazy idea, eh?
Similar to https://words.filippo.io/vuln-reports/, code is no longer special.
Vulnerability reports are not special anymore - https://news.ycombinator.com/item?id=48653216 - June 2026
(also like sibling comment about donating tokens or fiat to buy tokens)
Being able to submit an issue, description, test criteria along with a token budget would be pretty cool.