This is different from https://www.bountysource.com/ how?
Was just about to mention this site. I'd also be interested in knowing on what points it will differ from it, assuming the founders of bribe.io know about the already-available alternative.
Bribe developers to fix bugs
21–30 of 32 posts
Re: Bribe developers to fix bugs
#22http://dilbert.com/strips/comic/1995-11-13/ Wally: "i am going to write myself a new minvan this afternoon"
[deleted]
Re: Bribe developers to fix bugs
#23This is different from https://www.bountysource.com/ how?
We have been looking at Bounty Source which has many similar ideas. It is tied into GitHub while Bribe.io will work with any source repository or issue tracker. Bribe.io may also work with smaller tasks while Bounty Source looks like it is taking on very large projects.
Re: Bribe developers to fix bugs
#24http://dilbert.com/strips/comic/1995-11-13/ Wally: "i am going to write myself a new minvan this afternoon"
We envision that many times the bugs will be fixed by someone who has not already been working on that Open Source project. We also do not expect any projects which are intentionally buggy to become popular enough to make a difference.
Bribe.io will also include work on enhancements to an existing Open Source project.
Re: Bribe developers to fix bugs
#25This is different from https://www.bountysource.com/ how?
Was just about to mention this site. I'd also be interested in knowing on what points it will differ from it, assuming the founders of bribe.io know about the already-available alternative.
We have been looking at Bounty Source. We think jobs on Bribe.io will not be on that scale. Some of those projects are quite involved while Bribe.io may be smaller efforts, like updating a WordPress plugin to be responsive for mobile so it works with a mobile theme. It may just take an hour and earn the developer $100.
There may be some crossover with Bounty Source which could be good to provide multiple resources for users and developers.
Re: Bribe developers to fix bugs
#26bribes, or bounties, or prizes, or whatever you want to call it work on the extrinsic motivations for people to act. In many cases, open source projects are a product of love, that is, intrinsic motivations. There's always a risk when introducing extrinsic motivations that they'll crowd out the intrinsic.
I see where you are coming from, but I find that for myself, I come to different conclusions.
I work on open source not just because I love my product, but due to an element of wanting to show off. It's kind of a badge of honor, a point of pride to have a project that people use and love.
Which is to say that, without the motivation of others using my project, wanting to contribute to it, and even wanting to donate money to the project, my personal level of interest declines ("nobody is using this anyway.")
Re: Bribe developers to fix bugs
#27bribes, or bounties, or prizes, or whatever you want to call it work on the extrinsic motivations for people to act. In many cases, open source projects are a product of love, that is, intrinsic motivations. There's always a risk when introducing extrinsic motivations that they'll crowd out the intrinsic.
Human motivation is complicated. Chances are that ones relationship to some kind of labour is mixed with both intrinsic and extrinsic motivations: implementing the back end might be fun for you, while the front end is tedious, or vice versa. Or maybe it was only fun to make 90% of the features, while polishing those features and delivering the last 10% is a lot of tedium. Things like this might help to make some open source products more well-rounded.
Re: Bribe developers to fix bugs
#28http://dilbert.com/strips/comic/1995-11-13/ Wally: "i am going to write myself a new minvan this afternoon"
We envision that many times the bugs will be fixed by someone who has not already been working on that Open Source project. We also do not expect any projects which are intentionally buggy to become popular enough to make a difference. Bribe.io will also include work on enhancements to an existing Open Source project.
An open-source environment is really the only place this kind of motivation could work. As you say, if the project is intentionally buggy, it's unlikely to be used.
Love the idea!
Re: Bribe developers to fix bugs
#29Earlier quoted context omitted.
Was just about to mention this site. I'd also be interested in knowing on what points it will differ from it, assuming the founders of bribe.io know about the already-available alternative.
We have been looking at Bounty Source. We think jobs on Bribe.io will not be on that scale. Some of those projects are quite involved while Bribe.io may be smaller efforts, like updating a WordPress plugin to be responsive for mobile so it works with a mobile theme. It may just take an hour and earn the developer $100. There may be some crossover with Bounty Source which could be good to provide multiple resources fo…
I see. Thanks for the quick reply!
Re: Bribe developers to fix bugs
#30This is amazing idea, but I'm wondering that how is transaction going to work? Will there be any amount of money that "staff" keep?
The way we are going to handle the money is to take the payment when someone creates a job. The money will be held in an escrow account. Then developers can work on the job and submit their solution. Once the user accepts the work by the developer the money from the escrow account will be released to the developer. There will be a fee for the user while the developer gets the full amount pledged. If there is a confli…
Since you are taking money from the user, it is your incentive always to decide in their favor in order to get their repeat business.