Skip to content

The Open Source Movement

Abstract

Open source is usually told as a technology story: Stallman writes the GPL, Torvalds posts a kernel, Linux conquers the server room. That version is in The Open Source Revolution. This article treats open source as what it also is: a social movement, with the anatomy every social movement has. It has a theory of motivation (a gift economy where reputation is the currency), invented forms of government (dictators-for-life, elected leaders, foundations), a founding schism (free software versus open source), internal culture wars (codes of conduct, the meritocracy debate), a constitutional safety valve (the fork), and a chronic crisis nobody has solved: the world’s infrastructure now depends on volunteers, and volunteers burn out.

The Gift Economy

The first question outsiders asked about free software was economic: why would skilled programmers give away work that companies pay six figures for? Eric S. Raymond offered the most influential answer in his 1998 essay “Homesteading the Noosphere”. Drawing on the anthropology of gift cultures, he argued that open source communities are not exchange economies but gift economies: in a group where the essential goods (code, bandwidth, computing) are abundant, status is earned by giving things away. The currency is reputation among peers, and the customs that look strange from outside (the taboo on forking, the obsession with credit in changelogs and AUTHORS files, the fury at anyone who strips an attribution) are property norms that keep the reputation market honest.

Empirical research complicated the picture without overturning it. When Karim Lakhani and Robert Wolf surveyed 684 open source developers in 2002, the strongest predictor of effort was neither reputation nor career signaling but intrinsic enjoyment: the largest group said the work itself was the most creative thing they did, more so than their day jobs. Payment mattered too, earlier than the mythology admits (roughly 40 percent of respondents were already paid to contribute). The movement’s self-image as a pure volunteer culture was out of date by 2002 and has grown more so since: the majority of Linux kernel changes have come from paid corporate developers for two decades. What survives of the gift economy is its etiquette. Credit is still sacred, and companies that take without giving back are still shamed in terms Raymond would recognize.

Inventing Government

A movement that rejects bosses still has to make decisions, and open source projects became an accidental laboratory of constitutional design.

The oldest form is the Benevolent Dictator for Life. The title was coined for Guido van Rossum in 1995 and describes the natural politics of a young project: the founder decides, because the founder wrote the code and everyone else can leave. Linus Torvalds still runs the kernel this way; van Rossum showed the model’s limit when he resigned the title in July 2018, exhausted by the fight over one contested language feature (the “walrus operator”, PEP 572). Python replaced its dictator with an elected five-person steering council, recapitulating in miniature the historical move from monarchy to republic.

Debian wrote the movement’s first real constitution. Its Social Contract (ratified 1997, drafted by Bruce Perens) is a promise from the project to its users: Debian will remain 100 percent free software, will give back to the community, and will not hide problems. The attached Debian Free Software Guidelines defined, testably, what counts as free. Debian also elects its project leader annually and decides disputes by general resolution, complete with a voting system and a technical committee: a volunteer software project with more formal democracy than most trade unions.

The third form is the foundation. The Apache Group incorporated as the Apache Software Foundation in 1999, and its consensus culture (“the Apache Way”: decisions on public mailing lists, binding votes, no dictator) became the template for hundreds of projects. The Open Source Initiative (1998) took custody of the definition itself, turning the Debian guidelines into the Open Source Definition and certifying licenses against it. The Linux Foundation (2007) completed the arc: a trade consortium funded by the largest technology companies on earth, employing Torvalds so that no single employer owns his judgment. Critics note what the arc means: a movement that began by rejecting corporate control now routes much of its governance through bodies whose budgets come from corporate members.

The Schism

Every movement has a founding split, and open source’s happened at its christening. The phrase “open source” was coined by Christine Peterson on February 3, 1998, at a Palo Alto strategy meeting called days after Netscape announced it would free its browser code. The explicit goal was rebranding: drop Richard Stallman’s morally loaded “free software”, which scared businesses and confused everyone about price, and sell the development model on engineering merit. Raymond and Perens founded the Open Source Initiative that month to promote the new term.

Stallman refused the rebrand, and still does. For him software freedom is an ethical claim about the rights of users, and “open source” amputates the ethics to make the remainder palatable. The two camps ship the same licenses and the same code, which makes the dispute look cosmetic; it is not. It is a genuine disagreement about what the movement is for, and it resurfaces in every argument about whether a permissive license that allows proprietary capture is a success (code everywhere) or a failure (freedom nowhere). Perens himself lasted a year at OSI before leaving with an essay titled “It’s Time to Talk About Free Software Again”. The schism was never healed; it was merely outgrown, as most participants stopped caring which church they attended.

Culture Wars and the Fork

The movement’s second generation fought about conduct rather than licenses. Open source had long celebrated itself as a meritocracy: only the code matters, so the best code wins regardless of who wrote it. (GitHub’s headquarters displayed the slogan on an Oval Office style rug, “United Meritocracy of GitHub”, until criticism persuaded the company to remove it in 2014.) The counterargument, made mostly by women and minority contributors, was that the ideal did not match the mailing lists: communities whose norms tolerated flaming, harassment, and abusive review drove away exactly the contributors the meritocracy claimed to welcome, and the demographics (a few percent women, far below even the industry’s poor baseline) were the evidence.

The institutional answer was the code of conduct, most influentially Coraline Ada Ehmke’s Contributor Covenant (2014), adopted by tens of thousands of projects. The fights over adoption were bitter, because both sides understood them as constitutional questions: what may a project judge besides patches? The argument reached the movement’s summit in September 2018, when the Linux kernel adopted a Contributor Covenant based code and Torvalds, whose profane public demolitions of maintainers had been quoted and collected for years, took a month away from the kernel and apologized for years of “unprofessional and uncalled for” attacks. A year later Stallman resigned from MIT and from the presidency of the Free Software Foundation over remarks he posted about the Jeffrey Epstein case; his return to the FSF board in 2021 split the community again, with thousands of developers and dozens of organizations signing letters for and against. The movement discovered what older movements know: founders are load-bearing and human, in both directions.

Through all of this, open source retained a conflict-resolution mechanism no ordinary institution has: the fork. Because the license guarantees anyone the right to take the code and leave, every governance dispute is negotiated in the shadow of secession. Usually the threat suffices; sometimes it is carried out. When Oracle acquired Sun and neglected OpenOffice, the developers left in 2010 and founded LibreOffice, which is why every Linux distribution today ships the fork rather than the original. Oracle’s Hudson project became Jenkins the same way in 2011, by community vote. XFree86 changed its license in 2004 and was abandoned within months for the X.Org fork. The fork is the movement’s ultimate answer to the political question of exit versus voice: exit is always available, so voice is usually heard.

Dead End: SourceForge

For most of the 2000s the movement’s town square was SourceForge, launched in 1999 as free hosting for open source projects; at its peak it hosted hundreds of thousands of them. Its decline is a parable about entrusting a commons to an advertising business. As GitHub drained away developers after 2008, SourceForge’s owners monetized the remaining traffic: a 2013 “DevShare” program bundled adware into project installers, and in 2015 the site took over the account of GIMP for Windows (a project that had left in protest) and served its downloads wrapped in ad-laden installers. The reputational collapse was total, and no exodus in the movement’s history was faster. New owners ended the practices in 2016, but the lesson had been absorbed: the community now treats its infrastructure’s ownership as a live risk, which is also why GitHub’s 2018 acquisition by Microsoft, the movement’s old enemy, was met with wariness rather than trust, and why GitLab gained a hundred thousand imported repositories in a week.

Who Pays the Maintainers

The movement’s unsolved problem is sustainability. Open source won so completely that free code became load-bearing for everything, while the social structure paying for its upkeep remained, in many places, one tired person.

The demonstration case was Heartbleed (April 2014): a catastrophic bug in OpenSSL, the encryption library securing most of the web, which turned out to be maintained by a handful of people on about $2,000 a year in donations. The pattern has repeated on schedule since. In March 2016 a developer deleted left-pad, eleven lines of JavaScript, from the npm registry over a naming dispute, and build systems across the industry stopped. In December 2021 the Log4Shell vulnerability put a logging library maintained by unpaid volunteers at the center of a global security emergency. In March 2024 the xz backdoor showed the darkest variant: a years-long social engineering campaign that targeted a burned-out solo maintainer to insert a backdoor into the software supply chain (the fuller story, and the pattern of one-volunteer infrastructure it exemplifies, is in David Mills and NTP). The situation was drawn permanently in a 2020 xkcd cartoon: all modern digital infrastructure balanced on “a project some random person in Nebraska has been thanklessly maintaining since 2003”.

Nadia Eghbal’s Ford Foundation report Roads and Bridges (2016) reframed the issue in the movement’s own terms: open source code is infrastructure, and infrastructure needs maintenance budgets, not applause. The responses since have been real but partial: the Linux Foundation’s Core Infrastructure Initiative and its successor funded audits of critical projects, GitHub Sponsors (2019) and Open Collective route money to individuals, companies like Tidelift sell maintenance subscriptions and pay maintainers from the proceeds, and Germany’s Sovereign Tech Fund (2022) made maintainer funding state policy. None of it has changed the baseline fact, which is the movement’s founding bargain running in reverse. The gift economy produced the commons; the question the movement has not answered is what the commons owes the givers.


📚 Sources