On the funding of open source

What Does Not Kill Me Makes Me Stronger

Over the past week the question of who pays for open source and whether it faces a tragedy of the commons in the future has kept coming up. There seems an instinctive acceptance that open source is a charitable venture that should seek collective donations like any other non-profit. I don't think the tragedy of the commons applies to a true open source community, and I think the assumption it's all done "for free" is a mistake.

Three Threads

Three threads came together for me this evening from diverse sources:

  1. Chris Anderson, the author of The Long Tail, is now blogging his way to his new book about the impact of "free". I've found the posting stimulating and insightful and I'm finding the blog as valuable as his earlier "long tail" series. His posting last week about the three basic economic models involving getting something without paying was very clear, laying out all the approaches I could think of for leveraging "gratis". But at the end he made me wonder if he's completely clear about the "Free" in open source meaning "liberty" and not "price". The trigger was when he suggested the third model - "freemium" - was the model behind
    open source's "support included" commercial versions of Linux.
    While the models he describes can certainly apply to products delivered to consumers, I am not so sure they apply to the commons at the heart of peer production of which Yochai Benkler wrote.
  2. As it happens, I am currently reading Clay Shirky's (excellent) book Here Comes Everybody, which explores commons-based peer production in terms far more acessible than Benkler. I have reached the chapter called "Personal Motivation Meets Collaborative Production", which largely uses Wikipedia as an example1. Clay's book so far has been an ode to the power-law curve, and this chapter pointed out how the attribute of collaborative communities that, characteristically for power-law contexts, 80% of the work is done by 20% of the people (with one or two doing 80% of the work done by that 20%)2. Looking at Anderson's third diagram it's clear he's talking about the same sort of phenomenon.
  3. The third thread came from several conversations in different contexts about cash donations to open source communities. I have been being a a nuisance on some open source boards I participate in over accepting large donations from non-participants in return for giving them recognition. I've been asserting that it's not right to allow outsiders to gain the benefit of being seen as part of a community just because they made a large financial contribution. I still stand by that assertion, despite getting considerable push-back from several people whose opinions I respect.

Paying Your Own Way

Monarchs on Eucalyptus

These three threads all come together in the observation that open source is what happens when several different people choose to work together on the same code base rather than working separately. Each of them is there for their own reasons; each covers their own costs and contributes the code they choose to. There is no pooling of funds to pay for work to be done because everyone is solely responsible for their own costs.

As a consequence, there is no fiscal power that any contributor holds over others, so no-one has the right to tell the others what to do. An open source community is an example of a group of people choosing to synchronise their mutual interests, each at their own expense, for the benefit of all involved including themselves3. While there may be a non-profit organisation for administrative reasons, an open source community is not a non-profit or a for-profit.

Now, if the motivation of one or two of the participants is to then offer the software as part of a "freemium" plan, that doesn't mean the whole project is there to serve their activity. That's just the motivation of one or two participants at work. They are not giving away their work without payment; they are giving away the contents of the commons at the same price at which they acquired it.

As long as their activity doesn't "take over" and disrupt the interests of others, no-one minds too much. Your motivations for participating are rarely my business. There's a "long tail" out there too, made of a large number of others who have their own motivations to be there and who are covering their own costs as a part of executing on those motivations. And the commons isn't spoiled in any way by being more widely used.

If that's the case, allowing a donor to give only money to be able to use the community's "brand" flies in the face of the basic dynamic of the community. Whuffie is not for sale. I understand that some communities have created an adjunct non-profit, and that body can use the money for socially useful things like hosting or employing a facilitator. But the money that's needed ought to be coming from the community members themselves, not from an outsider trying to wrap themselves in the community's "flag". The community is only about contributing as far as that is about collaborating.

Mesh of Motives

Any open source project that actually has a co-developer community is thus not an example of Anderson's third model because profit doesn't come into it. Some of the contributors might be, but the community as a whole is actually a mesh of different participants, all with their own motivational models and all paying their own way to achieve them outside the context of the community. If those motivational models involve business, I am sure they will be about payment at the point of value. But the community itself is about the liberty to align interests, not about the presence or absence of profit. Once again "free" deceives english speakers...

  1. All the way through the chapter I've been wondering the effect of the strong Wikipedia culture. Shirky somewhat idealises contribution and the fact that there's an inner circle of "Wikipedians" taking actions like deleting non-notable entries rather than developing them isn't reflected.
  2. When I read about this at the end of last year it was a small revelation: whenever you see an 80/20 rule at work, there's an underlying power-law curve involved. I wonder how I had managed to miss this for so long.
  3. Before I get accused again of saying open source doesn't involve altruism, let me be clear that I don't think that. I do, however, reject the definition of altruism as being "an act that benefits other but not me."

'the community as a whole is actually a mesh of different participants, all with their own motivational models and all paying their own way to achieve them outside the context of the community.' - and what if my way of paying my own way (at least partially) is to get companies to give me money to code stuff so they can say 'We sponsored that'.

Looking at it bottom up - I'm a developer on ProjectX, and I need to find some way to fund my contribution; win the lottery; some other job, contribute on the side; contract for various companies as and when I can get them; work fulltime for AcmeCorp on ProjectX; create my own company around ProjectX; and so on. I don't see why I should be prevented from getting paid by a company or group of companies who then wants to say 'We sponsored that work'.

My understanding of your argument is that you would rather the ProjectX Foundation was not complicit in the 'We sponsored that' message, ie is OK for an AcmeCorp to sponsor some work, and crow about it in their marketing or on their site, but the Foundation should not sanction such on ProjectX material and sites.

Whuffie is for sale - companies large and small 'donate' their contributors code to gain recognition, whether in general, or specifically in that community. Are you saying Sun never touts it's contribution to open-source codebases? Do Sun never sponsor conferences? Does Sun never join project foundations? All these things, to me anyway, work, at least in part, to assign some of the project's whuffie to Sun.

Is what you are really annoyed about with sponsorship is that AcmeCorp could use it as a cheap way to buy whuffie without getting their hands dirty? What if ProjectX Foundation put the sponsorship threshold up to, for example, the full on costs of a developer for a year? 10 developers + a project manager?

Posted by Paul Cooper on September 08, 2008 at 10:01 PM PDT #

@Paul: I have no problem whatever with you getting sponsorship for yourself. As you say, that's completely reasonable and appropriate. But it's the responsibility of the contributors, rather than of the collective.

Posted by Simon Phipps on September 08, 2008 at 10:19 PM PDT #

Altruism... Open source may involve altruism... but I believe altruism is always motivated by selfishness.

An altruist does altruist things because in their mind, in there moral balance, it's the things that balance out positively. They are being altruistic because it fits their frame of mind and ethics. As such, they perform altruist acts to satisfy themselves at a possibly deep unconscious level.

Altruists are selfish people that get a driving satisfaction out of performing acts that are perceived as benefiting others...

Posted by Gilles Gravier on September 08, 2008 at 10:24 PM PDT #

Here is me being selfish : http://www.blastwave.org/dclarke/stuff/dennis_and_disks.jpeg

Feel free to visit www.blastwave.org and click on the donate button ( on the left ) such that others may be selfish also year after year.


Posted by Dennis Clarke on September 09, 2008 at 06:27 AM PDT #

[Trackback] I was reading Simon Phipps' recent blog on the funding of open source.  In it, he talks about how open source communities work. …there is no fiscal power that any contributor holds over others, so no-one has the right to tell the others ...

Posted by OpenLogic Blogs on September 11, 2008 at 08:27 AM PDT #

Post a Comment:
Comments are closed for this entry.

Thoughts and pointers on digital freedoms and technology markets. With a few photos too.


« June 2016