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?"

13 of 261 comments (clear)

  1. WANTED: Dead or Alive by Shadow+Wrought · · Score: 5, Funny
    Is it just me or does "Bounty" evoke ideas of something else entirely?

    "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?
    1. Re:WANTED: Dead or Alive by winkydink · · Score: 5, Funny

      Is it just me or does "Bounty" evoke ideas of something else entirely?

      The quicker picker-upper? Captain Bligh?

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  2. you forgot mark shuttleworths... by Simarilius · · Score: 5, Informative
  3. Not going to quit mine by Anonymous Coward · · Score: 5, Insightful

    $150 buys about 3hrs of my time, most of those projects posted look to take much longer than that.

    1. Re:Not going to quit mine by un1xl0ser · · Score: 5, Insightful

      Mod this up.

      A lot of the projects offer very little money for what they require.

      What is needed is a bounty system that users could pay into easily so the bounty could grow over time.

      --
      v4sw6PU$hw6ln6pr4F$ck 4/6$ma3+6u7LNS$w2m4l7U$i2e4+7en6a2X h
    2. Re:Not going to quit mine by Vorondil28 · · Score: 5, Interesting

      This is probably the smartest thing I've heard all day. Not only would bounties be bigger, but users would have an indirect say in what features got implemented. (i.e. - More users want feature X than Y, the bounty for X grows more rapidly than Y, X gets more man-hours of coding than Y and is implemented sooner.)

      --
      This sig rocks the casbah.
    3. Re:Not going to quit mine by duerra · · Score: 5, Funny
      What is needed is a bounty system that users could pay into easily so the bounty could grow over time.

      I'll give you $50 to do that.

    4. Re:Not going to quit mine by orfanotna · · Score: 5, Insightful

      To you $150 may be chump change, but to someone in let's say Russia (where a doctor with 10 years experience gets the equivalent of $18 a month), that's pretty good money. Is there a requirement that these features have to be implemented by North American/European/Japanese programmers?

  4. Bounties & 'Scratching an Itch' by Sv-Manowar · · Score: 5, Insightful

    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.

  5. Bounties Always for Adding Features by phidipides · · Score: 5, Insightful

    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.

  6. Because It Makes Economic Sense For The Sponsors by osewa77 · · Score: 5, Insightful

    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!

  7. Missing the point? by jsebrech · · Score: 5, Insightful

    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.

  8. to answer your question by Anonymous Coward · · Score: 5, Funny

    "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?