Slashdot Mirror


Proposal to Fund Debian Sparks Debate

lisah writes "The announcement earlier this week of 'experimental' group Dunc-Tank's plans to bankroll the work of certain Debian developers has sparked some controversy across the open source community. The leaders of Dunc-Tank say their primary motivation is to see that Debian version 4.0, also known as etch, is released on time this December. Debian developer Lucas Nussbaum, however, says that research shows that 'sometimes, paying volunteers decreases the overall participation.' Dunc-Tank member Raphaël Hertzog countered that the opposite is true and 'many Debian developers are motivated to work when things evolve,' a veiled reference to Debian's notoriously slow release cycle. Dunc-Tank member and kernel developer Ted Ts'o took the idea a step further and said, 'If money were among anybody's primary motivators...they probably wouldn't be accepting a grant from Dunc-Tank; they could probably make more money by applying for a job with Google — or Microsoft.'"

12 of 162 comments (clear)

  1. Microsoft already stole the best Debian devs by also-rr · · Score: 5, Funny

    Why do you think Vista's release cycle is so long already?

  2. How is this any different by aliscool · · Score: 5, Interesting

    than bounties paid by Ubuntu or Drupal to contributers?
    Dunc-Tank.org is organizing and raising money to step in and fund full time coding to ensure a deadline is met...
    I work a lot with Drupal and see this on the message boards often. "I'd like to see this feature built and I'm willing to pay XXX for it" Someone builds the feature and cashes in. Innovation and capitalism at work.
    I think Dunc-Tank.org has a great thing going here and wish them well with it.

    1. Re:How is this any different by QuantumG · · Score: 4, Informative

      No-one actually collects those bounties. It's a failed experiment.

      --
      How we know is more important than what we know.
  3. generalities and specificity by macadamia_harold · · Score: 5, Funny

    Nope. What you learned in an office does not hold true everywhere in life.

    Just like your specificity does not disprove the truthiness of my generality.

  4. Money isn't Everything... by denmarkw00t · · Score: 4, Insightful

    but is something, and that something is, well, money.

    I've rarely seen a better motivator for getting something done - especially in a timely manner - than money. If I'm volunteering with children or for a good cause (no, I know - Debian is a good cause too, but you know what I mean) then I'm going to do my best regardless because I feel like I'm helping benefit people who are less fortunate than me. However, if I'm working a job to maintain myself (and possibly my family) and I'm volunteering to develop a large open-source project and not getting payed for that extra work I do when I get home or when I'm up late at night, then a little money can go a long way.

    I don't think money would cause those being payed to work less at all, instead I think we'd see an increase in both the timeliness of development and the quality of code in the next Debian release.

  5. Nonsense by EmbeddedJanitor · · Score: 5, Insightful
    You speak of things you don't understand.

    Highly motivated people can often not devote as much time as they would like to OSS because they have to go to a regular job to pay for food etc.

    There are a lot of key Linux developers who provide huge benefit to the community, but would like to make it pay so that they can make a fulltime job of it. Go look at what some people like Hans Reiser have to say http://kerneltrap.org/node/5654 "Doing GPL work is doing charity work in our current legal and economic framework. That should be and could be changed, but for now it is so. I have done my share of charity, and I would not have a problem doing proprietary work.", and http://www.namesys.com/ "For free software based on support revenues to be viable, people have to be more inclined to use our support service than they are to use the support services of persons who bundle our software with what they sell. Frankly, they are not, and this is why providing service on free software is failing as a business model for producing free software."

    For my own part, I write OSS that saves people literally millions of dollars per year, yet I can only treat it as a hobby because it can't pay my bills.

    Hopefully at some stage people start **paying** for stuff that is valuable to them. Unfortunately people grab what they can get for free.

    Having good roads is very valuable, and you would not have those if they were not paid for. They are typically paid for by taxes because most people would not voluntarily dip into their pockets to pay for roads etc.

    I think any methods that help get money into the hands of **key** OSS developers is a good thing.

    --
    Engineering is the art of compromise.
    1. Re:Nonsense by Monkelectric · · Score: 4, Insightful

      You are right, but I would like to add a management perspective (although I am not a manager), I have worked on at least one very large OSS project. When you bring money into the equation -- you have to make a judgement call about who is most important, and who deserves money the most, and that inevitably pisses people off. There really is no fair way to distribute money in an OS project. So you loose people, and the project goes slower.

      --

      Religion is a gateway psychosis. -- Dave Foley

    2. Re:Nonsense by Kjella · · Score: 4, Insightful

      You're the one handing it out for free, what do you expect?

      Imagine for a moment, that you were working on an extremely specialized OSS project that only one company could profit from (absurd, I know). Since the code is free, they needn't pay you anything. However, you tell them that you need to put food on the table, and that to do any future work he will need pay. What can you expect of pay? If the expected value of having that developer work on that project is worth $X to the company, they should rationally be willing to donate up to $X voluntarily (ignoring some details like risk premiums). Why? Because the return on investment is good. Obviously in this case it'd be easier to hire him as an employee or contractor and make it an internal instead of OSS project, but that's not the point.

      Now instead imagine that there's a million people who each would get $1 of value if that developer kept developing. For a modest $50k salary, that means a ROI on 1900%. Sure you could not pay, but it'd be stupid. However, here's where it breaks down: Imagine one person doesn't want to pay. You now have 999,999 people to share the costs, which means it's still profitable (expected value > investment), but it is far more profitable to the one not paying at all. Repeat that 950,000 times and it's no longer profitable. And the last 50,000 will go "Why should we be paying for everyone else?" and not pay either.

      Basicly, it's the mass version of the prisoner's dilemma. They could have gotten a very good value for their money, but because everyone is acting egoistically, the result is that they don't.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Nonsense by QuantumG · · Score: 4, Informative

      Basicly, it's the mass version of the prisoner's dilemma.

      It's called the Tragedy Of The Commons.

      --
      How we know is more important than what we know.
  6. Re:What happened? by glwtta · · Score: 4, Insightful

    There does seem to be a lot of actual development activity as well. I wonder if the people bitching and the people doing work are, as usual, different people?

    --
    sic transit gloria mundi
  7. Re:the office by ex-geek · · Score: 5, Insightful

    I think you misunderstood Nussbaum. I believe he was trying to say that once some volunteers are paid, the other volunteers lose interest. I've witnessed this first hand in an originally volunteer based NPO.

  8. The difference between Work and Play by Respect_my_Authority · · Score: 4, Insightful

    Linus Torvalds started to build a Unix-like kernel "just for fun" and his fun project soon attracted contibutions even though Linus never offered any bounty or payment. So what's the difference between Work and Play? The former often sucks all the fun out of doing things while the latter usually encourages people to contribute simply because it's fun.

    Raising funds to employ one or two release managers for a short period of time just before the "etch" release may actually be a very good idea but I hope that the people behind this "Dunc-Tank" idea keep in their mind that fun and play will always be much more powerful motivators than money in a volunteer project like Debian. A crash course into understanding why this should be so can be found in the second chapter of "Adventures of Tom Sawyer" by Mark Twain:

    http://www.gutenberg.org/files/74/74-h/p1.htm#c2