They'll add it to issues the maintainers won't do otherwise, which in turn leads maintainers to hold the code hostage, not doing something they'd have done had there been no bounty structure, hoping that someone posts a bounty for it. Of course a maintainer is one of the world experts in that codebase so knows really well which things can or have to be done. So that behaviour will lead to maintainers not addressing issues they know will annoy users. It leads to annoyance driven development.
Regular payments are far better IMO for projects long term because they allow maintainers to actually maintain the software instead of hunting for bug bounties. They give more security to maintainers (rent is pretty much a constant for example) and less overhad for users (unless they want to save money and use it most efficiently, but IMO that's not what donations should be about). That being said, bounties aren't bad overall, they are definitely great ideas if used here and there, but funding of open source projects shouldn't be bounty-driven.
If you're asking what we benefit from doing this, not much. We could have released proprietary software, but as users of software ourselves, we enjoy having these freedoms, so we don't want to restrict users of the software we write.
I don’t see an issue with people saying “here’s my contrib if the community is willing to pay for it XX”.
One could even see maintainers becoming the budgeteers of aforementioned projects.
To be fair, GitHub Sponsors doesn't even allow you to sponsor a specific project, but only users or organizations.
I think BountySource (https://www.bountysource.com/) was the first player on the "Bounties for GitHub issues" side of things. Long time ago I actually came across a issue with a bounty though, so not sure it's actually working at the moment.
https://gitcoin.co/ is another attempt at aligning the incentives, but it's heavily involved in the cryptocurrency ecosystem and also been spamming projects in order to be setup on their platform, so I've been kind of avoiding it.
I think Open Collective seems to be the best platform for supporting projects with funding, but they don't have any "per issue" funding as far as I know. But it's a open project, someone should propose that feature!
It's a tool where users post bounties for features. Usually the owner of an open source project would set up a bounty and say "$xxx to fix this" and open source developers can apply to work on the problem, once its approved they get the funds.
But, if community members really value the project they can chip in more funding to the issue.
Currently the system is set up to use Ethereum and DAI (an ethereum USD stablecoin) to handle transactions, and Gitcoin's smart contract acts as the escrow account for the work.
In most parts of the world, that's an extremely high level salary and could easily fund most peoples month, granted they live outside of Silicon Valley.
I'm sure many people would be more than happy to receive 300 or much less for half a day of work.
Your talking windows audio /video internals which is not a common skill
The $10,000 bounty is about right for this sort of work. In fact it might be a little low, but I have no idea how OBS works internally so I could be completely wrong.
I like the concept of a utility-based market.
Yes, I'm aware this is based on a cryptocurrency system. But I would never want to force my users to navigate that mess in order to simply give me a few bucks. I'm just joking around above, but I don't think Gitcoin gets close to solving the problem.
GitHub Sponsors (https://github.com/sponsors) already exists, but I feel that they missed the point. As a user, I don't want to throw money at a project like it's a charity, I want to throw money so issues will be solved. As a developer, I don't want to accept unconditional donations (and all the unwritten, assumed responsibilities it comes with), I want to be funded in a concrete way so I can work on the issues users want so much they'd pay for it.