Richard Stallman, 1986

“Free software is a matter of liberty, not price.”

Richard Stallman wrote or delivered these words in 1986 in “The Free Software Definition.” Stallman's GNU project defined software freedom around users' ability to run, study, modify, and redistribute programs. The phrase distinguishes freedom from zero monetary cost. The quotation emerged from a concrete argument about how computing should work. The date assigned to this NewsStreets series is a calendar placement, not a claim that the quotation originated on March 8. Restoring the source keeps the words connected to the problem, audience, and technical conditions that made them meaningful. It also shows which part of the argument belongs to Richard Stallman and which interpretations were added later as the technology spread into new settings.

Its central insight is operational rather than decorative. Access to source and permission to change it can give users durable control over tools that shape their work and communication. Teams can apply that insight by naming the outcome they want, identifying the people affected, and choosing evidence that would reveal whether the design actually helps. A memorable quotation is useful when it sharpens a decision: architecture, interface, governance, maintenance, or the allocation of power. It is less useful when it is used to borrow authority without examining the speaker's reasoning. In practice, the principle should change a review question, a test plan, or an ownership decision rather than merely decorate a presentation.

Important qualifications keep the idea from turning into dogma. Licensing freedom does not automatically create usable, secure, or sustainably maintained software. Communities still need governance, funding, documentation, and respectful participation. Technology operates inside organizations and communities, so performance on a narrow benchmark cannot settle every question. Responsible practice makes assumptions explicit, documents tradeoffs, invites criticism, and provides a way to correct harm. That discipline does not weaken innovation; it gives ambitious work a clearer relationship to evidence and a more honest account of who carries the risk. A careful reader should therefore ask what the quotation leaves outside its frame, which stakeholders are absent, and what contrary evidence would require a different conclusion.

Current systems have made the underlying question larger, not obsolete. Open-source infrastructure, right-to-repair debates, public code, and software dependency policy continue to turn on who controls essential digital tools. For individuals, the quote can guide the next choice without pretending to supply a complete formula. For organizations, it can prompt clearer goals, better measurements, and more accountable ownership. Its lasting value lies in translating an influential idea into careful practice: understand the source, test the claim, keep the limitations visible, and revise the system when real users or real conditions contradict the preferred story. The standard is not admiration for a famous technologist; it is whether the idea helps people build systems that are more understandable, dependable, useful, and worthy of trust.