Slashdot Mirror


Site tracks F/OSS coding bounties

chatooya writes "Bounty County is a new website that lists programming bounties for free and open source software projects. It was launched this week by the Participatory Culture Foundation, which has some bounties of their own. You can search, browse, or get feeds of new bounties and if your project is offering a bounty, you can list it here." This is, IIRC, the fourth incaranation of a site like this that I've seen. Maybe this one will work.

10 of 41 comments (clear)

  1. They forgot one by yogikoudou · · Score: 3, Funny
  2. Re:Gnome-centric by jascat · · Score: 2, Informative

    It lists other bounties, but seeing as it is so new, I'm guessing they haven't found very many yet. If people aren't visiting the site and sending them info for other bounties, then the listing on there will be very limited. There were bounties for Limewire, Horde and DTV. I'm sure if someone submitted a KDE bounty, they would post it.

  3. I wonder if... by bgibby9 · · Score: 2, Interesting

    there will ever be a single "decent" repository of any programming job available that enables anyone to take advantage of it!

    I know (myself included) that I could almost leave my full-time role and focus on this type of development for a while to come!

    --
    http://www.gibby.net.au
  4. 4th times a charm? by Michalson · · Score: 4, Insightful

    Frankly there is one problem with bounties - the vast majority of them are very, very low when compared to what even an entry level programmer could earn putting in the same number of hours as would be needed to complete most of them.

    By comparison, the bounties can have a habbit of pushing off the normal volunteers from those areas - some don't like the idea of getting paid for a free project (in much the same way people helping out a charity will often reject any attempt at compensation), while others don't want the pressure of a "paid" project; they just want to have fun and help out an open source project.

    That leaves you with only one big audiance for bounties - high school kids and bums in college who are riding on their parents money (actual paying students need to work real jobs to get enough money to pay tuition). Neither of these groups are all that great for accomplishing the goals of bounties - they tend to lack the drive and responsibility of more mature coders, and can easily turn in garbage that just fills the requirement list in order to get the money.

    To work bounties need to either be bigger and/or offer some of kind of other incentive, or they need to be tailored to that 14 year old high school student crowd - smaller, easier to evaluate, harder to screw up. Basically farm out the low level tasks with bounties, and have the core team work on the real features.

    1. Re:4th times a charm? by knipknap · · Score: 2, Informative

      Frankly there is one problem with bounties - the vast majority of them are very, very low when compared to what even an entry level programmer could earn putting in the same number of hours as would be needed to complete most of them.

      I think you miss the point of bounties. They neither are an equivalent to hiring a contract worker, nor are they intended to. They are an incentive for people who do the work for fun, or to help someone who is hesitant to take on a project. In fact, if the bounties were any higher they might be understood as a replacement for the coding fun, which is IMO undesirable.

    2. Re:4th times a charm? by Karma+Farmer · · Score: 2, Informative

      To work bounties need to either be bigger and/or offer some of kind of other incentive, or they need to be tailored to that 14 year old high school student crowd - smaller, easier to evaluate, harder to screw up.

      Well, you've apparently never had any involvement with professional programming, of any kind.

      The most difficult part of programming is dividing up a project into small, easy to evaluate, difficult to screw up pieces. Doing that takes about 90% of the time, involves 90% of the effort, and usually involves multiple iterations of the entire development cycle to get right. You should count on several months of work by a highly qualified, extremely skilled developer to spec each week's worth of work for a low skill 14 year old high school student.

  5. This is still charity by castoridae · · Score: 4, Interesting

    Nobody should think they'll actually make money at this. The # of hours required for the $ earned is going to far exceed what a competent programmer could earn doing standard contracting work. And that's not to mention that there may be multiple people working towards one "bounty" at the same time, winner-take-all. And don't forget about scope creep - from one of the limewire projects... "The code is done when we say it's done".

    That said, I don't disapprove of this - just want to clarify that open source is still basically a volunteer effort, and while this is a nice token and perhaps a nice incentive, it shouldn't be confused with actual contract work or a means of livelihood.

  6. Bounties are very interesting by Anonymous Coward · · Score: 3, Insightful

    I think this is frontier work. Hard to see how anyone can deny this is a worthy project. Looks like early days and this will surely get better. But here are my questions/thoughts about bounties..

    1) How is the project itself funding the site? Perhaps they take a small percentage of the bounties.

    2) Wages are VERY low. It's just a start. As a focal point will serve both ends. Eventually business who want OS changes but don't have inhouse skills will use it to post (hopefully valuable) bounties.

    3) A problem arises because bounties will be cherry picked with the most rewarding stuff getting done quickly and the difficult and boring stuff getting left to one side.

    4) It goes against the scratch-an-itch motive. As per (3) some stuff will just never get takers because it's too obscure or dull while some bounties will be overwhelmed with applicants thinking "I was going to do exactly that anyway"

    5) This needs to expand beyond mere code. Design, test, maintainance, documentation and secondary assets are all a vital part of good software. For example paying graphic artists to design an entire new icon set in a consistent theme, or a bounty for a test report on 20 different hardware platforms that a computer shop owner could complete.

    6) Better skill based categories and micropayments for quick consultancy. For example I am an expert on DSP and could probably fix a complicated sound/video problem by altering a few lines of code. How could I get just a dollar for looking in on the source and saying "Yeah you need to cast this var as an integer and wrap it"?

    7) How are multiple bounty collisions handled? If 10 programmers all took on the bounty on the first day chances are they will all finish at about the same time so a first to the post gets paid system is quite unfair. Also this gives incentive to the quickest and hence probably lowest quality/least tested effort (a bit like the rush to post on /. ;)
    However farming them out on a round robin basis is inefficient.

    So SkuttleMonkey finally went to bed!? Or died in his slashdot chair like one of those mad chinese gamers? Hemos is dragging up some unusual stories, actually its refreshing to see less popularist material, good stuff.

  7. Bounty Source is a... by rappo · · Score: 2, Informative

    ...project management system that incorporates bounties into the core of the system. It's run by myself and my buddy Warren. We act as the escrow for all bounties placed in the system, so if it says there X dollars for a request, there truly is.

    Think of a SourceForge.net site with bounty handling built-in to tasks (feature requests, bug reports, etc). Also, I'd like to think that we're a bit easier to use from both the project manager's perspective and the end-user's perspective.

    We have SVN support and a bunch of other good stuff, and we're adding new features constantly (it's still a "beta" service).
    http://bountysource.com/

  8. Developing Countries? by bigtrike · · Score: 2, Insightful

    I bet a number of these get completed by people in developing countries where wages are not be as high. Some of the current bounties pay what I'd estimate to be about $100 per 8 hours of work. Not a great wage for most American programmers, but very high for a developing country.