GitHub Community
Replies: 7 comments 10 replies
-
|
Hey @whawker, this is a great idea and something we've been thinking about. I have a couple questions around how you'd expect this to work, if you don't mind!
Would you imagine anyone could attach a bounty to an issue, or only the project owner?
How would you want to verify that the attached PR fixes the issue? Would you expect the project owner or bounty poster has to "accept" the PR as something that works as promised? |
Beta Was this translation helpful? Give feedback.
-
I guess in a similar vein to StackOverflow, anyone could attach a bounty to an issue.
I guess this would have to be a manual approval step by the bounty poster. I suppose bad actors comes into again though, saying the PR doesn't fix the issue, when in reality it does, to avoid actually having to pay. Further thoughts on deterring bad actors:
|
Beta Was this translation helpful? Give feedback.
-
Supposedly project owners/maintainers would have to accept the bounty as well. Otherwise someone could, for example, attach a huge bounty on a feature which the project does not need or explicitly does not want. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it would be good to check how it works in https://bountysource.com/ ? |
Beta Was this translation helpful? Give feedback.
-
|
I was thinking of something like this except for feature requests. Like there might be a feature many users are requesting, but it might be particularly time consuming or difficult to implement, so someone could effectively "sponsor" a feature request to give the developer an incentive to implement it sooner. Makes me think of the countless times I've seen features in programs being requested for years. |
Beta Was this translation helpful? Give feedback.
-
|
That's exactly what this feature request is about though?! |
Beta Was this translation helpful? Give feedback.
-
|
I believe this is a must have feature in GitHub 🚀 That said, I guess the obvious issue which stops GitHub from implementing this essential issue is regulatory problems. Most likely developers who are working and solving those issues won't be able to accept money with the current GitHub Sponsorship tools. Otherwise GitHub would enable Sponsorship option for residents from all over the world. From technical side of this issue I also think that all the problems of unfairness or bounty split should be solved when we really see them being an issue. At the begging I would prefer to use KISS principle for this feature. Nevertheless, there could be potentially many features about sponsoring specific issues. Some projects implementing this functionality are below:
Also, there is a list of other bounty projects here: https://github.com/fossjobs/fossjobs/wiki/resources#bounties P.S. This problem is definitely worth implementing as this is an obvious "pain" for many users. I would be more than happy to donate money to some issues, but currently there is no an easy way of doing so 🥲 P.P.S. I'm also thinking this could be solved slightly differently from the legal / bureaucracy perspective. Probably far from ideal, but it could work for many cases quite nicely. |
Beta Was this translation helpful? Give feedback.
-
With Opire it's super easy and you only pay when there is a PR or the issue is closed - takes 4% on top of the bounty |
Beta Was this translation helpful? Give feedback.
-
|
I think one angle that is rarely talked about is developers at companies can sponsor creators through the company org account. In that same regard developers should be able to put a bounty on issues through the company org. Companies would be able to budget for these expenses, get invoiced via the regular invoice system thus giving developers at a company more freedom by reducing the bureaucracy one has to go through if they want to sponsor projects/issues. This may require some adjustments to the permission system since you may only want your technical leads/managers etc make those calls. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing thread – thanks for starting it @whawker! We're building Polar to give maintainers complementary tools for better funding and add-on services. Our first feature now is the ability to get funding towards specific issues/features (and soon milestones too). It's built for maintainers vs. bounty hunters, and built as a GitHub App to integrate beautifully in context of the issues you want to support funding towards. It embeds a badge at the bottom of the issues body/description. Polar is also open source (Apache 2.0): https://github.com/polarsource/polar Example of the Polar badge embedded on an issue at the bottom: |
Beta Was this translation helpful? Give feedback.
-
|
Polar seems to be the best solution out there (at least for now). But it still lacks on some functionalities like a way of discovering projects using it. |
Beta Was this translation helpful? Give feedback.
-
|
Polar is 100% way better then GitHub. Tools wise. Just know there are fees unlike GitHub which is fair but should be known. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you both for the kind words :) @pktiuk What would you use discovery for? Is it to find all issues with funding & rewards as a potential contributor? |
Beta Was this translation helpful? Give feedback.
-
|
@birkjernstrom But in general it could be used by freelancers willing to earn some money. |
Beta Was this translation helpful? Give feedback.
-
|
i'd like to use this for regular issues (not bug bounty related), |
Beta Was this translation helpful? Give feedback.
-
|
Check out Opire, that's exactly what it's for |
Beta Was this translation helpful? Give feedback.
-
I think a great addition to sponsors, would be the ability to attach a monetary value (or "bounty") to a GitHub issue. This could incentivise developers to address the issue, and perhaps attract new maintainers to an open source project.
In my mind, this would work via automatically paying the creator of a PR the attached bounty, when their PR is merged.
Risks:
Beta Was this translation helpful? Give feedback.
All reactions