bountysource / bountysource/core
Allow to split bounty in two bounties
- Dominant language
- Ruby
- Stars
- 643
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Description
Use case: you're a developer of a Linux-only app.
What you want: you want your app to be cross-platform, but don't have time/energy to port it to other OSs in your spare time.
What you could do: create a first bounty for porting your app to Mac, create a second bounty for porting your app to Windows, create a third bounty for FreeBSD.
What happens: you get at most 3 people backing the bounty for Mac, 2 for the Windows one, and 1 for FreeBSD.
This way, the projects seems dead. It would give the "feeling" that the project has bigger community if you just create a bounty called "cross-platform support", and leave it ambiguous. Then let's say you receive the 6 backings mentioned above: "money calls money" so to speak, seeing a very high pledged bounty may motivate others to back more to see it happen (because if they only see very small number of backings they may think that it will be too low to be claimed by a dev, even if they contribute, so they don't bother). This could have a multiplicator effect, let's say it reaches 10 or 12 pledges.
Then, at that point, it would be fair to split the bounty in 3 different bounties, asking each backer to what sub-bounty should their bounty go. This way you can claim a smaller (but more easier to achieve) bounty, without writing a huge pull request that has too many different things in it.
##
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1376553-allow-to-split-bounty-in-two-bounties?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github).
Contributor guide
Assessment
This issue has not been assessed yet.