
Does motivation matter? Open source contributors are increasingly people who are paid to work on open source. GNOME contributor Lucas Rocha asks how this impacts communities over the long term.
This is not a new question by any stretch. People worried about the influence of commercial interests in open source in the early days before Red Hat was a public company and when Slackware was still considered a major Linux distribution. I suspect people will still be asking this question for years to come.
Rocha poses several questions, including "Does being hired to do F/OSS work actually destroy the intrinsic motivations of a previously volunteer contributor?"
I don't think that it does, necessarily. It's been observed that many contributors start working on open source in college, and there's plenty of anecdotal evidence to suggest that is a norm. Not true of everyone, of course, but a lot of people discover and start contributing to open source when they're in college. This also happens to be when people have a lot of free time and very few financial obligations.
What happens when these folks don't find paid work doing open source? Often the contributions fall off because life intervenes and there's just not time to balance having a life, a full-time job, and making a lot of contributions to a project. That doesn't mean they disappear entirely, but often it means much reduced contributions.
The flip side, people hired to work on FLOSS projects, seem to remain involved and engaged. My observation of people who've taken jobs working on projects is that they often remain just as motivated, not by the paycheck but by the project. The paycheck is just a tool to allow contributors to continue to focus on FLOSS instead of something else to pay the bills. I've seen contributors continue working on projects even after being laid off or taking new jobs, at least until those new projects or jobs consume their available cycles.
Rocha also says that he believes communities should be "mainly measured by the number of volunteer contributors it has because those are the people who are surely giving their contributions based on intrinsic motivations."
This seems to be a bit too simplistic a view, in my opinion. If you look at, say, the Linux kernel community, few would say that it's a weak or unhealthy community. Yet, many if not most of the contributors are paid to work on the kernel. Certainly most of the core contributors are. They're not contributing because they are paid to (at least most of the time), they're paid because companies see value in the contributions they're making and see a need to support that work. Also, because companies want to have some influence on what those folks work on or to be able to draw on their experience.
The Linux kernel community isn't the only one, of course. If you look at Apache, PostgreSQL, and most successful projects, you'll find most core contributors are making a living related to their contributions. This is as it should be. The romanticized notion that communities are only healthy if a lot of people are contributing for free is misguided. Yes, a healthy community may inspire unpaid contributions, but healthy communities also have stable core contributors who can dedicate a lot of time to the project. That's not a reasonable long-term plan for unpaid volunteers who aren't independently wealthy.
Photo courtesy of @ericskiff on Flickr under CC SA 2.0