Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21545 ideas, 132412 comments, 2606687 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #1295: Allow users to attach "bounties" to Ubuntu Brainstorm ideas

Written by Auzy the 29 Feb 08 at 11:41. Related project: brainstorm.ubuntu.com. Status: New
Rationale
It would be great if users could attach money to Brainstorm ideas. Its all good and well to post hundreds of ideas, but as things go, ideas which are posted first may not be the best ideas, but will climb to the top fastest (and will stay there, because people will vote for them on most popular).

Lets make it possible for people to donate $5 or so to their own ideas. Sure nobody may implement it, or the patch may not be accepted but it opens things up a lot more. Nobody loses either.

For those who think that this will turn linux coders into people who only code for money are wrong. There have been many bounties in the past, and they have not wiped out the many developers (me inclusive) who code as a hobby. Even with the gnome bounties in place, I still continued coding my application at the time for instance.


Anyway, at the end of the day, its not hard to implement, and it will do nothing but speed up development for highly wanted features (and maybe even organisations like gnome could use the money on spreading word about linux, or improving their hardware support).

647
votes
up equal down
Solution #1: Implement bounties in brainstorm
Written by Auzy the 29 Feb 08 at 11:41.
Lets make it possible for people to donate $5 or so to their own ideas. Sure nobody may implement it, or the patch may not be accepted but it opens things up a lot more. Nobody loses either.
7
votes
up equal down
Solution #2: Pooled "Bounties" and Developer Pricing
Written by doctormo the 16 Jan 09 at 15:21.
I propose that developers use their good standing to set an amount of money they would be prepared to accept in order to complete a solution. Then users can pool together their money in order to meet that and vote on which developer (by cost or by name) should do the work.

This has a clear idea that in order to be the accepted developer, you must be able to prove your reputation and be able to clearly document what you plan on doing.

No money would be transfered unless the amount of people who have put their money in _and_ voted for one of the developers, is more than what the developer needs to complete the job.
-13
votes
up equal down
Solution #3: Copy or integrate the cofundos system
Written by luk156 the 14 Mar 09 at 08:54.
Give us the ability to offer money for a idea like on cofundos.org.
25
votes
up equal down
Solution #4: Just link to a cofundos project in your post
Written by cheesehead the 14 Mar 09 at 18:52.
Open (or find) a project on cofundos, and simply post a link to it in your Brainstorm solution, Brainstorm comment, blog, forum post, Launchpad page, etc.
5
votes
up equal down
Solution #5: Formal bounty system
Written by e the 2 Oct 09 at 13:39.
0. Someone proposes an idea.
1. Brainstorm users promise to donate to see an idea solved.
2. Developers suggest a solution and a minimum cost that they would perform the development for. The solution would include clear exit criteria, stating the deliverables; as well as a finishing date that the solution must be provided by.
3. Brainstorm users pick the solution they will pay for.
4. One or more judges are chosen who will sign off when the deliverables are completed. (These could be Canonical employees or Brainstorm users)
5. The developers and judges get in touch with the owners of the project in question, to coordinate the proposed solution (and increase the likelihood that it will be accepted into the project).
6. Brainstorm users donate money that is held in escrow until the judges have signed off or the finishing date has passed.
7. Developers implement solution showing their final result to the judge(s).
8. Developers iterate changes until judges are satisfied.
9. Money is released to developers.

If the finishing date elapses before the software is delivered, then the donations are released back to the Brainstorm users.

I know the escrow service sounds scary (because it's extra infrastructure), but I think it's necessary. Developers need know that they will be paid when the work is done.

Propose your solution

Attachments
No attachments.


Duplicates


Comments
bigdufstuff wrote on the 29 Feb 08 at 11:44
For bounties to work well for all parties involved the bounty must make a very clear description of what the deliverables will be. As it stands now, brainstorm does not do that.

I do like the idea of mass contribution to community goals through bounties, but it would need to be a bit more formal.

bgfeldm wrote on the 29 Feb 08 at 13:14
For this to work you would need a money broker to take the money until the bounty has been satisfied or a time frame passes to give the money back. This will ensure the bounty is good.

Vadim P. wrote on the 29 Feb 08 at 14:20
Yes, there are several websites that do bounties already:

http://www.cofundos.org/
http://bountycounty.org/
http://www.opensourcexperts.com/bountylist.html
https://www.bountysource.com/

Integration with any, or all of them, would be nice.

nixeagle wrote on the 29 Feb 08 at 20:27
I'm not so sure about this. Yes its useful, but I think this site was made just so that the community at large can be heard as to which issues are important to the most users.

As far as ideas being stuck on the front page, thats good, the issues I see on the front page are nothing to snigger at.

I see right now:

Fix Suspend and Hibernate - This has been an outstanding issue for so long, its good to have a place that the developers can really tell how much this bugs users.

Provide a simple graphical interface to manage _any_ type of network connection - Networking has always been a linux issue. As of gutsy they have improved the standards greatly, but more work does need to be done, to make it work with modems well and other devices.

There are a bunch more, but the vast majority of them are worthy issues, some of them I never knew existed! There is a bias towards the issues that cropped up first, but by the looks of it, the widely blogged/and publicized issues seem to be at the top of this list... so hopefully some of these are fixed going into the next release.

All in all, I will say that this system is awesome! It gives users who are afraid or don't know how to use bugzilla a place to request features, and comment without having to worry about the traditions of bugzilla/developer bug tracking systems.

blakerateliff wrote on the 29 Feb 08 at 20:31
I think that this is a great idea to get fixes pushed through.

kab wrote on the 29 Feb 08 at 21:15
It's also possible that the users can bet an amount of money to ideas they love and if a developer want to develop it and need some money, users who have bet some are notified and can decide if the make a donation through pay pal or something. Technically this should be very easy to implement.

stix213 wrote on the 29 Feb 08 at 23:02
I think this is a very good idea, but won't work with the current "brainstorm" format. I think this could greatly accelerate Ubuntu development.

rawsausage wrote on the 29 Feb 08 at 23:24
Good idea. I'd instantly pay gladly 1000 EUR for removal of Evolution from the default desktop. :-)

wolfier wrote on the 1 Mar 08 at 03:54
I'd pay 1001 EUR for them to keep it!

See the problem with bounties? The person who has more money is not necessary also the person who has a better idea.

Voted down.

Auzy wrote on the 1 Mar 08 at 12:12
Obviously they would need to have a high enough vote first, and be authorised by the ubuntu team.

maynoth wrote on the 1 Mar 08 at 16:14
allow users to see google ads in the idea and click to add funds

wolfier wrote on the 1 Mar 08 at 19:05
The problem is, the money attached may make it more viable to the ubuntu team - not saying that they're corrupt, but it's human nature. The bigger the lure the higher the incentive.

We should keep money out of this at all.

If you find Ubuntu good, donate. Otherwise, don't.

EJ wrote on the 5 Mar 08 at 23:33
I think this is a great idea. There are a lot of people who like to contribute but don't have the free time or knowledge. Developers needs to eat and life, donating money is very usefull. There are just not enough developers to implement all the good ideas.
This is my proposol: populair ideas will be checked by ubuntu/canonical. This means that they estimate the costs of realising the idea. The brainstorm idea will show a progress bar of the donations like wikipedia. When there is enough money the idea can be implemented. It's more fun to donate because you can see the direct results of your donation and you can donate on the things you think are important.

Quote:
Good idea. I'd instantly pay gladly 1000 EUR for removal of Evolution from the default desktop. :-)
I'd pay 1001 EUR for them to keep it!

See the problem with bounties? The person who has more money is not necessary also the person who has a better idea.
end quote

That's true, but ubuntu/canonical must determine if people can donate on it.

Auzy wrote on the 6 Mar 08 at 04:47
The patch would also need to be accepted into the main distribution


andrewmin wrote on the 15 Mar 08 at 18:53
I think that the bounty would only be paid if the entry was accepted. So the developers will still have control over it, there'll just be more incentive to fix the patches. Because of this, I think it'll work just fine.

Heck, it could even bring in more professional devs!

korvins wrote on the 23 Mar 08 at 22:47
Developers need to eat, and this could help more people to donate and improve Ubuntu faster.

Full time developers are necessary :)

saivann (Brainstorm moderator) wrote on the 3 Apr 08 at 20:11
This idea is incredible and can release the infinite power of opensource software. I vote +1 only under these conditions :

1. People can only donate to ideas / bugs that are approved by the authorized administrator of the projects.
2. Donations give no power of decision, decisions belong to the projects administrators (nothing changes).
3. All ideas refused/not implemented are refunded.
4. Donations go to the people(s) who implement the solutions.
5. Ideas/bugs need at least 2 administrators to review and accept the solutions before it is set to implemented and that the contributor receive the donations for is work.

someonestolemyname wrote on the 20 Apr 08 at 18:56
Not a bad idea!

I picture like at 750 votes the team checks it out, decides viability, then allows people to donate toward the bounty. The first developer[s] who fixes it gets the money. It would of course be tangible things, like 'Make Ubuntu work with this one device' rather than concepts like 'Make suspend/hibernate work'. although it could be cchanged to accomodate those.

Manos wrote on the 25 Apr 08 at 19:18
I completely agree with saivann.
The only problem is that it may take longer to implement then most ideas.

+1

ToSsMaStR wrote on the 11 May 08 at 21:55
(+1) i like! nice! agreed with saivann!

wladston wrote on the 23 May 08 at 21:32
I was wishing somethign like this since a long time ...

please, make it happen, let me pay to have stuff that I like to work!!

Manos wrote on the 24 May 08 at 23:00
We should also allow to attach threats.
"Do this by Monday or I'll send your Wife's index finger in the mail!"
I'm not sure how well the code will be :P

spanella47 wrote on the 5 Jun 08 at 00:05
agree with saivann as well with one exception:

- sometimes the hold on ideas being accepted upstream is reviewers not spending the time to review and merge the code. some % (say 5-10%) of compensation could be afforded to them for this time and effort that isn't always smooth.

spanella47 wrote on the 5 Jun 08 at 00:18
secondly Ubuntu could make a page that made it easy to give money to organizations like X.org or Gnome that are much larger than one person developing, but an easier donation center would maybe allow them to hire more full time developers rather than the part-time hackers that usually work on these projects.

This would work either through links to organization collection sites or by distributing the money through Ubuntu.

loonyphoenix wrote on the 20 Aug 08 at 08:29
Russian Firefox community has already successfully done something like this. Mozilla Russia launched a program called "Money for bugs", and three Russia-specific (or multilanguage-specific) bugs have already been corrected as a result. The bounties given for these bugs were $500, $470 and $400. Two paid bugs are still open for sale, both at currently the price of $300.

loonyphoenix wrote on the 20 Aug 08 at 08:45
http://mozilla.ru/contribute/bounty-en.html

Here's a link to the English project page. It's not exactly what this idea is about, but it's close.

Craig73 wrote on the 3 Oct 08 at 14:54
I think the ability to contribute money is an excellent idea... as other (duplicate) ideas suggested, this is a great way to bring momentum to issues that have no corporate momentum.

My concern, as stated by others, is how do you balance paying money to get a personal need met with undue influence of those with money (or in economies with stronger or more accessible dollars)?

Could we consider a maximum? For example, only allow people to contribute one dollar to an idea.

This would remove undue influence, and would required more people to contribute, but seems to better support "community decisions"

-----------------------------------------
Like Saivann above, I would think there are a number of needed restrictions/caveats/questions?

1. Does my contribution only pay for a developer? or how do we include a UI designer, architect, QA, reviewer in this process? [or is this a future enhancement to this?]

2. While I some how believe 'acceptance' into code base would somehow help ensure code quality, I do worry about the appearance of money creating a economy of crap code for a quick buck.

3. How do you assign a fair value to a project? IE - if 5000 users like an idea, contribute a dollar, there are $5000 in funds to spend...
- do you spend $500 for the 80% solution or $5000 for the 98% solution
- do we pay more for a good/expert developer or less for an adequate one? (the hourly rate might be a wash with the hours/skills balance)
- can we buy short term kludges until the long term infrastructure change is in place? (does some of the money go to that long term change?)
- what are the tax implications? Is this a donation or a payment?
- does this favour developers in economies with a lower dollar/lower cost of living? (or do I care, since we are all one happy family... that will exclude the expensive brother for the cheap one)

4) Unlike Saivann, I find it hard to believe that donations will not give power to a decision. I think the economic vs community contributions is a larger discussion that will swallow and destroy this idea quickly. We need to accept that there are multiple streams of contributions, and evolve the overall model separately.

Craig73 wrote on the 3 Oct 08 at 14:57
PS - I voted this up. While I think my suggestion is slightly different... I think the basic idea is sound [we just need to hash out the implementation]

jpka wrote on the 28 Oct 08 at 07:05
In some big and 'wild' countries, such as Russian Federation, more than 90% people in big cities and more than 99% people overall, not have a credit card and not able to (electronically) transfer money outside the country easy. The ways to transfer is exist, but very time- and cost consuming. Thus, almost no way to donate. I want this, but I can't do this.

saivann (Brainstorm moderator) wrote on the 16 Feb 09 at 06:07
Apparently, a similar system was (is??) in development for launchpad but the status is not clear :

https://wiki.ubuntu.com/UbuntuDownUnder/BOFs/BountyStrategy
https://bugs.launchpad.net/launchpad-foundations/+bug/91201

Previously, bounties existed directly through the wiki :

https://wiki.ubuntu.com/BreezyBounties

e wrote on the 2 Oct 09 at 13:41
I've proposed solution #5. It proposes a more formal system (that requires an escrow service) and involves coordination with the project that would be changed by the dev work.

I hope that addresses some of the concerns about the wrong solution being proposed/developed.


Post your comment