Slashdot Mirror
OSS Projects Offer Bounties For Features
jtowndot writes "The market for open source developers seems to be heating up. Asterisk, Gnome, Horde, and Mozilla all have bounties for desired features. Recently, Lime Wire updated its wish list to include bounties on open source development work! Similarly, i2p also released a bounty list. Is it time to consider quitting my day job to do open source development full time?"
"We got the Feature. He's holed up over on the South side of the partition. Better bring your compiler."
If brevity is the soul of wit, then how does one explain Twitter?
Nobody likes your day job.
http://www.markshuttleworth.com/bounty.html
time to get away from all these damn M$ languages like C# and learn a real language for a change, maybe then ill make some money :-)
$150 buys about 3hrs of my time, most of those projects posted look to take much longer than that.
At these bounty rates you would be starving. As a professional doing open source work for free they are almost an insult: Do people really rate our work that low?
What, like NASM?
click me
Maybe someone should make it their day job. ;-)
I mean, someone might write code for the requested feature that works, kinda, but maybe not a good implementation or is uncommented obfuscated spaghetti code or something. How do they assertain whether or not the implementation should get the entire bounty or a portion?
Is outsourceing it's bounties to India then, heh. Just because me and you can't afford to live off of these bounties doesn't mean someone somewhere else couldn't.
click me
Hmmm...at "http://www.i2p.net/bounties" there are $450 of bounties...and $150 of it is for a "Content Distribution Network"
I wouldn't quit your day job yet.
Have you actually been able to get any of these bounties yet?
its also comparativly few projects hat do bounties, as a quick check, add up all the bounties you can find and then ask - is it bigger than a year's salairy?
In some cases at least, it seems as if these bounties are used to deal with the relative lack-of-glamour inherent in implementing some features in pieces of OSS. For the most part, its the cool hacks and features that people need individually that grab attention and get worked on. Bounties seem to redress that balance of developer attention towards less glamourous but key pieces of functionality & improvements which aren't imminently required. (although for the most part, it seems like a different class of hackers are attracted to the bounties within projects)
Of course, putting money into OSS through these kind of means is a great use, since similar amounts spent on commercial products has a minimal/neglible effect on their development. Its also a great way for those people who cant code to contribute to the software they use, and get features they'd like to see implemented.
Business Voyeur
I only looked at the Limewire bounty list, but the max they were offering is $500 for the hard projects.
There's probably a few things on there that someone could bang out in a weekend. The cash might me the needed incentive.
Although I wonder how long the project list has sat open. Maybe none of the projects were getting finished because of the lack of incentive.
I did some work on Rent-A-Coder, and the pittance you can get paid doing OSS projects makes it more worthwhile to simply get a job like everyone else.
The dangers of knowledge trigger emotional distress in human beings.
I was very glad to see that the bounties are actually reasonably set. I believe that a competent coder could actually make reasonable money, from these bounties. A few months working (in spare time) on two of the "large project" bounties would be a reasonable amount of cash.
I certainly don't mean that any coder should quit his day job and only work for OSS bounties. The work isn't realiable or regular. And probably the amount he'll make, on a $/hour basis, is not as much as he could make in a normal job or consulting. However, as an added revenue stream, it's great: there's no real commitment or even schedule to keep, and it's more fun/rewarding to code for an OSS project.
I donate regularly to OSS projects. However, if more OSS projects had donation pages where I could link my donation to a particular bounty (a particular feature I really want to see in the next version), then alot of cash could probably be pulled together. I think that in this case a coder might be able to quit their day job. Some features would be worth alot, and a bunch of people would be willing to pay. Give us the means to make a difference, and we'll do it!
In a way consumers have always been able to vote on features in a natural selection sort of way (lousy software dies off, the best stuff gets a year or letters next to the title). But this allows much more direct feedback while still allowing the project leaders to control what direction the software is developed in.
Additionally, it will perhaps put egos in check to see what users want and to be able to say you're giving them what they pay for, instead of getting upset when they feel they have a legitimate gripe about bugs in a free product and you feel they should be thankful for what they've got already (video game emulation community?)
And on top of that maybe it would allow even stronger claims to be made if a company violates your licence -- those users aren't paying for features to be appropriated by someone who's going to steal work and close the source.
Try not. Do or do not, there is no try.
-- Dr. Spock, stardate 2822-3.
Anyone who intends to count on the bounty opportunities as a source of income should make sure that there is a firm understanding as to what is required to earn the bounty (if not requesting a contract of some kind). I can certainly see folks plowing a lot of effort into this only to have the people offering the bounty say "that's not what I want...no bounty for you".
If there is one overriding reason that I hate MS Office, it is that it feels like the application was developed by a thousand independent programmers. Consistency between and within Office applications is very poor. Each feature seems to have its own UI logic, limitations, behaviors.
A bounty program is great. But if it creates a thousand independent bolt-on features, it will suck. Perhaps some high-level architect in each project can create some stub classes or documentation that define exactly what the bounty-earning feature must do and how it should conform to a set of UI guidelines.
Two wrongs don't make a right, but three lefts do.
One thing I've noticed about free software that differs vastly from the projects I've worked on in the commercial world is that with free software there is usually a push to do something right, even if it means waiting a while for a feature. With the bounties I've seen thus far, the mentality seems to be the commercial "do it as quickly as possible" idea. Granted, a lot of the bounties are for stuff no one really wants to do, so something is probably better than nothing, but it might also be nice to have rewards for those who do things well.
Tasks like removing dead code, simplifying existing code, etc are tasks that the commercial world seldom does with its software ("if it ain't broke...") but it's something that keeps open source code maintainable. It might be a good idea to set up some of these bounties in terms of rewards, such that projects could once a year give something to people who not only added features to a project, but who improved the quality of a project. The bounties going out now are great, but expanding them to support quality and innovation would be really, really great.
JAMWiki Java-based Wiki engine
This is a sign of what supporters of Open Source have been saying - that real companies are getting real value by using open source. It is cheaper for them to pay for a feature to be added to some open source software than to have proprietary software developed to their specifications. Licenses like GPL make it compulsory for those companies to contribute those changes back to the community, but unless you're in the software business this is really not a disadvantage at all. Open source lets you pay less to get the features you need and *still* reap the Public Relations benefits of having "contributed to the community". Sounds like a CEO's dream!
I'm thinking of a pledge drive where I put my credit card down for the pledge and when enough money is pledged, all the pending pledges are "fulfilled" (to use the commercial sales nomenclature).
A pledge drive like this has the benefit making me more likely to pledge, since I know my money will only be taken if the project is going to happen.
Ben in DC
Ben in DC
"It's the mark of an educated mind to be moved by statistics" Oscar Wilde
Let me see if I got this striaght. So the open source community will offer a monetary reward for the completion of a feature. Meanwhile closed source companies will pay competitive, if not higher, salaries to work on a product.
Clearly the resources of a closed source company does not guarantee any kind of quality in the product. However, "Dog" the code hunter is going to come along a code your feature for a few bucks. Oh yeah, that sure sounds like the quality is going to go through the roof.
Seriously, what form of QA is in place here?
This will definitely attract more developers to OSS. Whats more, its not just blind competition. i2p is promoting working in teams rather than competing and, I assume, sharing the bounty. So in that case there's only winners here.
But is it worth quitting your job for this?? Probably too early. Maybe experienced developers who have already made significant contributions to OSS projects could risk it.
This is really interresting trend that is forming. Software development is shifting more and more towards being a freelance, pay as you go profession, and less "I work for xyz company".
I wonder how long before the entire industry adopts this practice
What if I work on a feature with the expectation of getting the bounty, only to find it claimed before I'm done?
I'm assuming this is an attempt to speed development of some features, nothing more
This time, FOSS shoots first!
I'm not a CS grad, nor do I have any programming knowledge at all, but as a college graduate with no job, seeing this article raises a few questions for me: (I'm in a different field but with a similar predicament)
(1) How do the taxes on these "bounties" work out? Are you considered an independent contractor with your own 1199, or do payroll taxes kick in?
(2) Can CS grads who can't find jobs now use open source projects as a basis of experience, and can they not put the experience on their resume? Before, saying "I helped program XYZ chunk of Firefox" didn't really seem to mean too much on a resume, since there was no one over there you could ask to verify this. But now, if someone over there is willing to pay you cash, is there now a paper trail involved? i.e.: Can you now put down ABC's name on your resume as a reference if his payroll office paid you to build that XYZ chunk of Firefox? If you now could, this option could definitely help a lot of the unemployed CS people gain valuable experience.
Granted, I may not know what I'm talking about, but I'm just wondering. A lot.
Ubuntu has a list of favorite bounties...too modest for rent and ramen.
(n/t)
You can do it because you 100% want to (OSS), or because you 100% get paid (commercial). But what's wrong with there being a whole range from 1-99%? And on a simple "the higher the rates, the less people willing" basis, most of them will be on the low end. A small bonus perhaps. But what's wrong with that?
Kjella
Live today, because you never know what tomorrow brings
The answer is obviously: Depends how many of those damn bounties you intend to earn!
Seriously, don't let us talk you out of it. If you can pay your mortgage with bug/feature bounties, then millions of people will surely thank you.
you had me at #!
Would you have preferred "paid volunteers" instead?
It might be a nice bonus for a couple beer-and-pizza nights, but most people who would/could spend the required time for those projects would probably do it for free, anyway. I worry more for the starving student who spends a week on one of the projects only to be eclipsed by another starving student who submits his solution a day earlier.
If you can afford the time, help the projects out and, politely, refuse the reward. If you're hard-pressed for cash and have the skills to provide them a solution... you'll be much better off finding a real job and helping them later.
Don't mod GP, MOD UP parent.
There is an idea in your post, a really good idea. He just tells us what he thinks he is worth.
How about a p2p style standard to publish these bounties out where anyone and everyone can find them, work on them and submit responses.
meh
Wanted Dead Or Alive
Fugitive Name: ClippyBounty: $10,000
Details: For causing the Great Depression.
The Great Depression was a period of er, depression, among PC users. Clippy was known to smirk and annoy users who required genuine help. Many of the victims suffered brain damage and voted for George W. Bush. Clippy is known to travel naked and was last seen on Microsoft Windows (see Bill Gates wanted poster).
Along the same lines, a new company LxM Media http://lxmsuite.com/ has started up. They will be offering data services for MythTv http://mythtv.org/ as well as paying the Myth developers. From what I undstand, you pay $5/month, and you get bounty points to spend durring the month by putting them towards a specific feature or plugin. They will then pay the myth developer who implements the most popular function.
$150 buys 1 hour of my time! It's low skilled whores like yourself that screw up the market for real professionals.
Asterisk wants a small font for the legal small print in its eula. Gnome wants some horsemanure to stand on Horde wants some horses Mozilla wants a flash screen where its fighting against King Kong.
https://bugzilla.mozilla.org/show_bug.cgi?id=47838
Posted five years ago and still marked as "new" asking for the netscape 4 ability to paste a clipboard image straight into amozilla mail message. Lots of people pledged money but still zero interest.
Seems like it's cheaper to pay a modest bounty to add a feature, than hire a programmer and have to give the enhanced source away, too.
...some times you don't.
For those of you who don't get this, it's a reference to an old TV commercial for Bounty/Mounds chocolate candy.
Aren't these bounties missing the point?
It seems to me the biggest lacking in OSS is not the featureset, it is the usability of that featureset. Take gimp for example. It's an excellent image editor. It has every feature I need. And yet I keep getting drawn back to photoshop when I need to get real work done, because gimp is such a PITA to use (less so than it used to be admittedly, but still not anywhere near what it could be).
This pattern for me is repeated over and over in almost all OSS projects. The few open source products I use on a daily basis and like are all centrally designed, with one person, or a few people, dictating the entire user-visible interface, like with firefox.
The total lack of usability progress in the vast majority of OSS projects is what made me give up on linux on the desktop. Yeah, it's fine to tinker, and yes, it does anything you need. But to get real work done it just gets in my way.
I don't mean to flame-bait, but that's my honest opinion. And I think if someone really wants to promote open source software, they are better off investing their resources in convincing projects to appoint design czars who have absolute control over the user-visible part of the software. Even a poorly done single-person design is still better than a methodically executed design by committee. These bounties for me are missing the point, and won't really matter in the end.
Anyway, imho ofcourse.
I2P is not ready for a large userbase yet! The network code, for the moment, maintains a connection to every other router on the network (though this will be fixed soon.) If it receives a large influx of users (from, say, I don't know, being linked from the front page of Slashdot), the network will fall apart. Besides that, the developer prefers to keep a small userbase.
This might not be good.
I always think about NetBeans and Eclipse and how they are both these OSS projects that are funded by large companies. Most of the code for these projects has been written by developers on the dole from either Sun or IBM. The question is, why should companies like IBM or Sun limit themselves to the pool of developers they have working in-house? I currently work as a developer 40+ hours a week, and while I have ideas for features to contribute and bugs I would like to see fixed in these products, I can't see programming outside of my job since the programming I do for work I get paid for. If Sun or IBM would sign a reasonable check for me to fix their products, I would be more likely to help them out.
"Is it time to consider quitting my day job to do open source development full time?"
One word.....YES!
On a totally unrelated note, could you please provide me with the contact info for your company's hiring manager?
If you write a piece of code for one OS app, then all the other ones can use it. So, in effect, you're getting paid $x by company X to use it, and $0 by companies Y,Z,A, et al.
At first blush, the reasonable solution would be to increase bounties. However, you then get company X paying for everyone else. And the solution of having each company pay you would no longer make it open source.
Now, I am aware that a piece of code written for one particular program might not work for another (different function names, etc.) But these differences seem to be relatively easy to go over, and any well-written piece of code shouldn't even have these problems anyway.
So the demand curve is going to be pretty steep, since a feature doesn't mean as much if everyone has it. The fact that bounties might not get paid if someone else completes it first will make the supply curve pretty shallow. So you get very few bounties getting fulfilled with a price pretty close to the amount developers are willing to pay.
Of course, such a simplistic model can't possibly account for the full impact, but you get the picture.
I contribute to a software project. cvs-digest.org. The reports takes two maybe three hours each week, with a bit of other time for housekeeping.
In my work in a technical trade, that kind of commitment of time, hardware and expertise would be billed out at around $2-3000 per week.
To offer me a pittance is an insult. Yet I am willing to give my time because I enjoy what I am doing and enjoy the service I render to the project.
I'm sure these efforts are well meaning, but if the game is making a living from this stuff, the whole game changes.
Oct. 29 2004,16:31 (Post by Gamester17)
Donations for DVD-menu in XBMC campaign
We have had this idea in mind for a while and were planning to kick of this campaign at a later date but after a recent post in mplayer-dev mailing-list we have decided to bring forward the announcement. The 'donations for DVD-menu in XBMC campaign' basic concept is to encourage XBMC end-users to make donations (via PayPal) into a fund in order to motivate the XBMC developers to prioritize programming DVD-Video menu/navigation support for XBMC. This concept has been brewing for a few month now as many people have either posted in the forum or e-mailed us directly offering to donate money to this specific cause, which has been the #1 requested feature for quite a while. So come on, be generous and help support the XBMC project. Give donations for how much you feel XBMC is worth to you as a whole if this feature were added to XBMC's already very long feature list. The XBMC developer(s) who code this huge feature will collect the fund-pot on completion as a reward - they have adready started coding.
UPDATE (9/11-2004): Just thought we let everyone that the campaign is going very well which shows the demand for this feature, the fund have already received over 100 donations and so far the fund total is at just over $1,800(US), which includes one very generous donation today of $500(US) from Team-Xecuter (who said they will also donate 5 x X3-modchips to the fund). Short progress-report on the actual code development; our XBMC devs working on this internally have got basic DVD playback working and menus are also partially working, all showing great promise.
Make your donation towards DVD-menu support in XBMC via PayPal: $25, $50, $100 or other.
If like to make a none-PayPal (money or maybe a gift) donation please contact Gamester17.
Forum discussion: Donations for DVD-menu in XBMC campaign (link)
Is it time to consider quitting my day job to do open source development full time?"
I just love it when people even joke like this. Apparently noone even thinks about benefits anymore.
Let me tell you a little story. About a year ago I wanted to quit my job so that I could do development for my brother's company fulltime. Now I just bought a place and got engaged, but I had some money in the bank.
Not more than 2 months later my fiance has a chemical breakdown and has to put in the hospital. Thank GOD the Friday before we got our domestic partnership and was able to put her under my insurance and they even covered the bill for her hospital stay even though she was only on my policy for less than 7 days.
Long story short (too late), the I only had to pay out $135 for her treatment that cost $30K.
So before any you have dreams of quitter your job to fight the good fight against Microsoft, consider EVERYTHING first. Insurance costs $1500 a month for decent coverage. Nothing like the coverage I get from work here. One over night stay in the hospital could bankrupt you.
Want to add stability, a professional look and feel, extensibility, and a strong underlying core technology to GNOME?
It already exists. It is called KDE.
Just because it CAN be done, doesn't mean it should!
Some KDE projects have a very similar contribution system set. Kontact (email/groupware client) has a link to it under the help menu where you can "shop" for new features. Features are requested and people can donate to certain features. Once the price has been met on a feature development on it will start. Perfect for companies that would like to see certain features in Kontact. In fact, I'd encourage more companies to switch to Linux/KDE/Kontact for at least those machines that are primarily used for email/internet/word processing. the amount of money they would save on M$ Outlook licenses would be more than enough to request any 'missing' features. That said, I believe Kontact to be a very complete Outlook killer.
otherwise there would be no need for the bounty.
Jules: We should have shotguns for this kind of deal.
Vincent: How many up there?
Jules: Three or four.
Vincent: That's countin' our ap?
Jules: Not sure.
Vincent: So that means there could be up to five aps up there?
Jules: It's possible.
Vincent: We should have fuckin' shotguns.
Yes, if you're trying to make a living off these bounties forget it.
But it could be a nice bit of money for a student or someone just interested in the codebase and a good learning experience. I always find I learn a lot better if I'm trying to accomplish something in code rather than just browsing. That's part of the reason code reviews don't work as well as they should.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
The thing is that even if you work on a bounty you still have to do it in such a way that the maintainers will accept it, which means it also has to meet a general level of quality and cannot juse be thrown together.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Isn't the idea of a bounty perfectly consistent with the points you make or imply:
1. The UI needs improvement.
2. I {can't be bothered}/{don't know how} to improve it myself.
One obvious response: Offer an incentive to make the necessary improvements: A bounty! Seems like you're describing the premise and failing to see a fitting solution.
You also omit mention of the massive negatives associated with taking on a program like Photoshop, or any proprietary package. (Having used Adobe products for 20 years in commercial graphic arts, I am pretty intimate with the downside...)
One obvious and real advantage of open source packages, with or without bounties: You can make bug reports, even if you're not interested in actually fixing a problem yourself.
you had me at #!
Obviously you are right on the gimp issue. (Or any Gnome application for that matter) But the rest sounds a bit like You don't know it so you don't like it. Because it is visible, you deem it UI problems.
I have been using Linux/KDE for 4 years exclusively now, and I am kuite happy with it. I am pretty sure it would be quite painfull if I had to switch to windows or gnome. The layout of KDE is pretty consistent, the pain comes when i have to use a Gnome (or windows) application that uses different guidelines. But does that difference mean that they had their brains sucked out through the nose?
As for the UI czar you propose: that is not how most projects work. If you treat your developers bad, you will just get no code. However big a czar you might be, with such an attitude you probably work alone. Besides, most of the time, a developer already has absolute control over all the source. He can change whatever he likes, that is what open source is for: If you make it better, please show us.
The resistance you feel when you see something different is just a phase of learning. Except for the gimp, that program has been written especially to torment you.
This space is intentionally staring blankly at you
There should be rules if this is implemented in a large project that prohibit persons employed full-time on the project, and people with checkin priviliges, from taking bounties. Why? Because if they can take them, then they can withold popular features in order to collect the inevitable bounty that will develop. The longer they withhold, the bigger it will get. It's a negative incentive.
...all you do is drive the much lower rate even lower.
Not a smart move.
I would have to disagree with this in some situations.
I do a lot of custom programming/development work, and most of this work is to get a competitive advantage over other companies. Using something where they have to redistribute those changes annulls that advantage and even creates a disadvantage because while they get it cheap, their competition would get it for free.Problems are like gifts, it's better to give than to receive
Maybe MS should put on bounty on some of their developers?
:q!
that I would be interested in if:
a) The bounties were high enough to justify spending my time on the projects
b) Developers could "lock" bounties for a particular period of time (ie. so you don't spend a week or two.. only to have someone else submit their code a day earlier and collect the money).
I am the maverick of Slashdot
This really is one of the most interesting things I've seen developed on the 'net in a long, long time.
It has, of course, heaps of utility beyond just funding development of pet projects...
-- -pjk Perry Kundert perry@kundert.ca http://kundert.2y.net
Let's see, x dollar bounty divided by $0/hr volunteer work equals... damn, take the $150, cos 3 hours is a hell of a lot shorter than the alternative!
I read Slashdot for the articles.
I looked at the Limewire wish list. It seems to me that the modifications they want sometimes require changes that effect quite a few parts of the program's architecture. If someone wants to earn his dollars quickly, he'll add hacks here and there, and in the end the whole thing will be unmaintainable.
Are there any requirements for developers that go beyond "make it work"?
I've been following the i2p project for a number of months, and it appears that the bounties are working quite well for this project.
One of the most popular features (responsible for much of i2p's press and public recognition), the i2p-bittorrent port, was the result of a Bounty feature.
I'd love to see more projects take this sort of thing up, or better yet-- someone should setup a NonProfit Bounty Hosting System, that allows users to contribute small amounts for specific features via Paypal, etc. This would most likely result in much higher bounties, and much increased usage of bounties among the various OSS projects (as the project maintaners wouldn't be responsible for collecting and dispersing $$).
If someone feels up to the challenge of putting together the backend scripting for such a Bounty Provider, I'll gladly donate hosting, database storage, etc on one of my dedicated servers at EV1. I'll even give an initial bounty of $50 to the person who does this!
Hmm, that is trivial to do - I implemented the rich text copy and paste for many kde apps - including konqueror (well khtml - the html part of it)
I can't wait to see what the Nigerian scam artists do with these open-to-all bounties.
They'll probably ask for you to write the code for an RPN calculator, and then they will wire $10,000 to your checking account. You just need to send them the magic digits....
You mean like the Public Software Fund?
-russ
Don't piss off The Angry Economist
This is what the Public Software Fund does. Write up a bounty and pledge some amount for it. If nobody will do it for that amount of money, talk your friends into pledging more money .... until somebody decides it's enough to write the code.
-russ
Don't piss off The Angry Economist
The AROS project has been doing bounties for a while now. http://www.aros.org/
Have you considered that posting this to Slashdot front page will lead many coders to see it and cash in?
Have you thought that if that happens, there will be less bounties for you to claim?
I would try to keep this little-known.... That way you can make more money. Posting it to Slashdot (oh, and it's already been talked about here anyway) would be a mistake.
At a total value of $27,620, "the" OSS bounty market isn't worth even enough for one person to quit their day job. If that market evolves to accommodate bids as well as offers, it might attract enough activity to support thousands of developers.
--
make install -not war
Of course it's cheaper. But it screws over the programmer. Why you guys insist on devaluing your own profession is quite beyond my capacity. :-)
-- "I never gave these stories much credence." - HAL 9000
Every developer is familiar with being pulled into many different directions simultaneously and every user/company sees priorities differently. Then you've got your own interests to contend with. Balancing between these can be tricky, but necessary.
I use the familiar triage approach to organize bugs, feature requests, and my own interests. If there are common feature requests, those are (of course) weighted higher. However, I always make sure that I get something fun in there to keep me fresh.
open source support company, it looks like there's a bit of the rising temp in the mechanics market as well. I do not know if this is ready for announcement by IBM yet, so no more names...
I'll offer $100 for a linux port of my OSS project. Shouldn't be too hard for the linux people in these parts right?
Philosophy.
I just dumped this cup of warm yellow liquid on the counter...
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
Requirement: "Web interface for sales staff to assemble reports."
Acceptance criteria: "A member of the sales staff can browse to an internal web site and assemble reports using data sources X, Y, and Z."
When a customer has signed off on a proper requirements document that includes acceptance criteria, they agree to accept easily verifiable X as proof that requirement Y was met - they can't change their mind without admitting it anymore.
This works on management, too. :)
Well, the mechanism is in place....
... no one wanted to PLOW the fields and take out the trash.
Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
Many people are doing it for free... Or large companies are paying people to do write the source then give it away for free to sell support. That's how most of the projects now offering bounties came into exsistance.
You are making this logical jump:
There exist awards for coding desired things.
People receive these awards for coding desired things.
Therefore people only code desired things because they have the opportunity to receive awards.
Substitute "excellence in teaching" with "code for desired things" and you get:
There exist awards for excellence in teaching.
People receive these awards for excellence in teaching.
Therefore people only teach excellently because they have the opportunity to receive awards.
Do you see the problem with your statement now?
You complete ignore the fact that people want to code these things, and other people wish to reward these coders. There is not necessarily a connection between these two groups of people.
But that's not the point. Those Indians should be making the same amount of money as an American doing the work. It's only fair.
click me
That was nothing more than a clever plow to get some extra points.
Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
Each project might also need a product manager who gets bounties for functional designs and feature specifications that are accepted by a oommunity review.
Trivial? And yet after five years noone has been prepared to do it! Why don't you have a go and claim the money and much thanks?
I'm guessing there's a catch, but I can't for the life of me see where. Maybe I'll give it a shot tonight.
How many of us have helped someone move into a new house or apartment for no more than a few beers or a good meal?
When you can't afford to pay someone what they're worth it can often be better to offer an enjoyable non-monetary gift.