The GNU Manifesto Defines a Cooperative Free-Software System
How Richard Stallman's 1985 manifesto turned the GNU operating-system plan into an ethical, technical, and economic argument for user freedom.
In March 1985, Richard Stallman’s GNU Manifesto gave the GNU operating-system project a longer technical, ethical, and economic argument. It expanded material from his September 1983 announcement, reported early development progress, requested help, and answered objections to software users being allowed to share and modify programs.
The manifesto was not the project’s starting gun. Stallman announced GNU on September 27, 1983 and began full-time work in January 1984. Nor is the online text an untouched March artifact: GNU’s introductory note says the manifesto received minor updates through 1987, while explanatory footnotes added from 1993 onward clarify language that readers had misunderstood.
GNU was a plan for a complete compatible system
GNU is a recursive acronym for “GNU’s Not Unix.” The project intended to build a complete Unix-compatible operating system without copying proprietary Unix implementation code. Compatibility gave existing users, programmers, and applications a path to adoption; it did not mean GNU would be Unix under another brand.
The manifesto listed an editor, debugger, parser generator, linker, utilities, compiler, shell, kernel, window system, communications software, documentation, and applications. An operating system meant a coordinated environment, not just a kernel. Independent contributors could reimplement documented utilities while a smaller group handled tightly coupled kernel work.
This scope explains both GNU’s influence and its long development. GCC, Emacs, the GNU C Library, shells, utilities, build tools, and licenses became foundational well before GNU’s own kernel was ready for general use.
“Free” concerned permission, not a mandatory zero price
The manifesto argued that recipients should be allowed to modify and redistribute GNU and that distributors should not be able to remove those freedoms downstream. It explicitly said GNU was not being placed in the public domain. That position anticipated copyleft, later implemented in detail through GNU licenses.
Some early wording used phrases such as “give away,” which readers could interpret as prohibiting payment. Later footnotes explain that this was not the intention: copies could be sold, while every recipient retained freedom to cooperate, inspect, modify, and share. Free software and free-of-charge software are not the same category.
The modern four-freedoms formulation was refined later. Reading the 1985 text as though it already contained every subsequent definition and licensing distinction would flatten the movement’s development. The manifesto supplied central principles, not a frozen final vocabulary.
The document made an economic argument too
Stallman addressed the claim that programmers and support organizations could not be paid without restricting copies. He proposed services, customization, maintenance, porting, teaching, donations, and collective funding as alternatives. The argument was not that programming required no labor or money; it was that payment did not require one vendor to control every recipient’s use and modification.
Some predictions and proposals were intentionally provocative and did not become GNU policy or industry practice. The manifesto even discussed a software tax as one possible funding mechanism. Historical importance does not make every economic forecast correct. It shows which objections the project expected and how its founder answered them in 1985.
The ethical claim distinguished GNU from later open source
The manifesto treated restrictions on sharing as a social and moral problem. It described nondisclosure agreements and proprietary licenses as barriers among programmers and argued that users should not depend on one source-owning vendor for changes.
The label open source was adopted in 1998, thirteen years later, by a separate campaign that often emphasized development and business benefits. Many programs and licenses qualify under both traditions, but projecting that later name backward erases why GNU framed cooperation as freedom. The free software and open source history explains the overlap without making the movements identical.
GNU’s later success did not follow the exact plan
The Free Software Foundation was established in October 1985 to support GNU development. GNU General Public License version 1 appeared in 1989, after the manifesto, and provided a more precise legal mechanism for preserving freedoms. By 1990, GNU had produced or adopted most major system components but lacked a production-ready kernel.
Linus Torvalds began Linux as a separate kernel project in 1991; it became free software in 1992. Combining Linux with GNU components produced the systems the GNU project calls GNU/Linux. Linux was not the kernel described as complete in the original announcement, and GNU did not suddenly begin when Linux appeared.
The manifesto’s durable significance lies in joining implementation to purpose. It did not merely promise a compiler or shell. It argued that a technically compatible operating system could be organized so users received source and enforceable freedom to change and redistribute it. Later licenses, organizations, and software made that claim operational in ways the 1985 document could only outline.