Comment by tfrancisl
3 days ago
Better yet: give them cold hard cash instead of what is arguably monopoly money for many OSS devs. Ironically this is something GitHub made "easy" with sponsorships several years ago.
3 days ago
Better yet: give them cold hard cash instead of what is arguably monopoly money for many OSS devs. Ironically this is something GitHub made "easy" with sponsorships several years ago.
How do you ensure that funds ear-marked for a donor-specified issue goes toward that issue and not something else?
You don't sponsor people or projects to complete specific issues or build specific features in the first place. Sponsorship is a reward and token of appreciation for doing good work.
Some don't mind doing the overall reward and appreciation thing. And some just have that particular issue that they want handled so the project works - better - for them. Both cases are valid.
6 replies →
You hit up the maintainer and negotiate a deal for that?
If all you’ve got is relative pocket change they probably aren’t going to agree but if you put real money behind it and it doesn’t go against their vision of the project then most people would be willing to accept actual contracting work to expand their project.
Sounds like a lot of trouble to go through, vs just sending some funds to a wallet with the assurance it'll go where you want it to or return to you.
Then you offer to pay the maintainer their consulting rate to do it if they are willing.
That's one way to go about it, but doesn't exactly work when one has targeted requirements in 20 different projects.
You actually hire a developer to work on that issue and not something else.
Pretty much what this ensures. Just that the "developer" is a LLM agent.
2 replies →