Saved
Software · Tech history

GNU Manifesto

A manifesto is not a licence—it’s a recruitment tool that turned a Usenet post into a movement.

Worth your time?4.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
9:37in productionCh. 1 · Call to arms/ 9:37 · ceiling 15 min
4 chapters · 9:37Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 9:37 planned

Read the brief

The GNU Manifesto is not code. It is a deliberate, public, repeatable act of movement-building—written to recruit, not just explain.

Chapters & takeaways4
  1. 1:06
    Call to arms

    It is a recruitment document—not philosophy first, but action first.

  2. 2:41
    The harm argument

    It diagnoses proprietary software as a social toxin, not just a technical constraint.

  3. 4:10
    From email to manifesto

    It formalises a plan first announced on Usenet in 1983—turning a mailing list post into a journal-published mission.

  4. 5:40
    Movement launch

    It launches the free software movement by naming the GNU Project as its vehicle.

1 more chapterFewer chapters
Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • makes proprietary software’s social cost legible
  • converts informal announcement into durable public record
  • enables coordinated development across distributed contributors
What does not
  • define software freedom in writing
Study it if
  • developers
  • policy-makers
  • historians of computing
Skip it if
  • end-users seeking immediate utility
  • engineers evaluating technical specs
Who should study it, and who should skipHide who it is for
The written brief1 min read

What it is and the problem it solves

It is a 1985 manifesto that solves the problem of user disempowerment under proprietary Unix by proposing a collaboratively built, Unix-compatible free operating system. It was published in March 1985 in Dr. Dobb’s Journal. Some parts of it began as an email announcement posted to Usenet on September 27, 1983. A major driver, according to Richard Stallman, was the rapid trend toward Unix and its components becoming proprietary software.

How it works

It is a written call-to-action. It explains the GNU Project’s goals, cites proprietary software as socially harmful, and solicits work, funding, programs, and hardware. It opens with an explanation of what the GNU Project is and how far the GNU operating system had progressed at the time. The project’s aim was to give users freedom and control over their computers by collaboratively developing software based on Stallman’s idea of software freedom.

What works

It successfully frames proprietary software as socially divisive. It converts an email announcement into a public, reproducible, and persuasive foundation for collective action. The philosophical basis it lays down is that proprietary software divides users, who are then no longer able to help each other.

What does not

It does not define software freedom in writing—the formal definition appeared in February 1986, a year later.

What it changes

It establishes the GNU Project as the vehicle for the free software movement—and makes that movement legible, actionable, and publicly anchored.

Is it worth your time

Yes—if you need to understand how software freedom was institutionalised as a movement, not just an idea.

Same field · Software4 of 114
Up next in Technology

Berliner Gramophone

1889 · 9:36

The Berliner Gramophone didn’t invent sound recording—but it invented the record label, the disc format, and the idea that music could be a stamped commodity.

9:36