Navigating the Lexicon: Key Terms in Open Source

Last updated on:

If you’ve ever tried to explore the world of open source software, you’ve likely run into a cluster of terms – “free software,” “open source,” “FOSS,” “FLOSS,” “libre software” – often used interchangeably, yet carrying subtly different meanings. For law students studying the management of intellectual property rights, getting these definitions right isn’t just semantic housekeeping. It directly shapes how software is licensed, how rights are enforced, and how communities are built around shared code. This post breaks down each of these key terms clearly.

Table of Contents

What does “free software” actually mean?

The term “free software” was coined by Richard Stallman in the 1980s and is defined by the Free Software Foundation (FSF), which Stallman founded in 1985. The critical point – one Stallman emphasizes repeatedly – is that “free” refers to freedom, not price. The FSF often uses the phrase “free as in free speech, not free beer” to make this distinction. In French or Spanish, the word libre captures this meaning without ambiguity; in English, “free” unfortunately muddles both senses.

According to the FSF, a program qualifies as free software if it grants users four essential freedoms:

  • Freedom 0: The freedom to run the program for any purpose.
  • Freedom 1: The freedom to study how the program works and modify it. Access to the source code is a prerequisite.
  • Freedom 2: The freedom to redistribute copies to help others.
  • Freedom 3: The freedom to distribute modified versions so the whole community benefits. Again, source code access is required.

These four freedoms are not just technical permissions – for the FSF, they represent a moral and ethical stance. When users lack these freedoms, the FSF considers the software to be an instrument of unjust control over its users.

To ensure these freedoms are preserved legally, Stallman developed the concept of copyleft. Rather than abandoning copyright, copyleft uses copyright law to flip its usual effect. The GNU General Public License (GPL) – the most prominent copyleft license – requires that any derivative work also be distributed under the same terms. This prevents someone from taking free software, modifying it, and redistributing it as proprietary software. Copyleft is therefore both a legal strategy and a philosophical commitment to keeping software free in perpetuity.

What is “open source software”?

The term “open source” emerged in 1998, when developers including Bruce Perens and Eric Raymond sought a more business-friendly label for free software. They founded the Open Source Initiative (OSI) and drafted the Open Source Definition (OSD), which sets out ten criteria a license must meet to be considered open source. These include free redistribution, availability of source code, permission to create derivative works, no discrimination against persons, groups, or fields of endeavor, and more.

Crucially, the Open Source Definition was directly derived from the Debian Free Software Guidelines (DFSG), developed in 1997 by Bruce Perens himself. According to Perens, “open source” was originally intended as a synonym for free software – a rebranding exercise aimed at making the concept more palatable to corporations. Over time, however, the two terms diverged philosophically.

Open source vs. free software: same licenses, different philosophies

From a purely legal standpoint, the definitions substantially overlap – almost all software that qualifies as free software also qualifies as open source, and vice versa. The divergence is largely philosophical. The FSF frames software freedom as an ethical imperative, a matter of users’ rights akin to civil liberties. The OSI, by contrast, emphasizes the practical and economic advantages of open development models: better code quality, faster bug fixing (famously captured in Linus’s Law – “given enough eyeballs, all bugs are shallow”), and reduced cost.

Richard Stallman has described the open source approach as pragmatic but incomplete – addressing software openness as a technical and business question, while sidestepping the deeper ethical issue of whether proprietary software is morally acceptable at all. Eric Raymond, co-founder of the OSI, disagrees, arguing that the ethical framing alienates businesses and slows the spread of open development practices.

FOSS: free and open source software

FOSS stands for Free and Open Source Software. FOSS is an umbrella term that encompasses both free software (as defined by the FSF) and open source software (as defined by the OSI). It was coined to serve as a neutral, inclusive label that avoids taking sides in the philosophical debate between the two camps. Governmental institutions, academic researchers, and corporations frequently use FOSS when they want to refer to this broad category of software without endorsing either the FSF’s or OSI’s particular framing.

However, the term has its critics. Because “free” in English is ambiguous, FOSS doesn’t fully resolve the confusion – a reader might still wonder whether “free” means gratis or libre. Additionally, the GNU Project argues that the term “Free and Open Source Software” misleadingly suggests the two are a single unified viewpoint rather than two distinct philosophical positions that happen to agree on most licenses.

FLOSS: free/libre and open source software

FLOSS stands for Free/Libre and Open Source Software. The term was originally coined by a European researcher who wanted to study software development practices without taking a political position on whether “free software” or “open source” was the more appropriate framing. By inserting “libre” – borrowed from French and Spanish, where it unambiguously means freedom – FLOSS makes explicit that “free” is about liberty, not price.

The FLOSS acronym gained official traction in international policy contexts. By 2004, it had appeared in official English-language documents issued by South Africa, Spain, and Brazil. The European Union also adopted FLOSS in various institutional contexts. Richard Stallman himself endorses FLOSS as a more accurate neutral term than FOSS, since it gives equal prominence to both “free software” and “open source” rather than burying “free” inside the compound. That said, Stallman still prefers “free software” when expressing his own movement’s values.

Not everyone is a fan of FLOSS. Eric Raymond, who coined “open source,” has criticized the acronym as unwieldy and counterproductive – arguing that neither FLOSS nor FOSS can be understood without first knowing both constituent concepts, making them poor entry points for newcomers.

Beyond these four principal terms, a few other labels appear in open source discourse:

Libre software: This term, borrowed directly from French and Spanish, simply means free software in the sense of freedom. It avoids the English ambiguity entirely and is preferred in many non-English-speaking jurisdictions and academic publications.

Freeware: This is a common source of confusion. Freeware refers to software that is available at no monetary cost but does not necessarily provide source code or allow modification and redistribution. Freeware is “free” only in price, not in freedom, and does not qualify as free software or open source under any of the definitions above.

Proprietary software: Software distributed under restrictive licenses that deny users access to source code or the right to modify and redistribute. Proprietary software is the direct opposite of FOSS/FLOSS. It is important to note that FOSS is not the opposite of commercial software – many FOSS projects are commercially developed and supported. The correct antonym of FOSS is proprietary or closed-source software.

Copyleft vs. permissive licenses: Within the FOSS/FLOSS ecosystem, licenses fall broadly into two families. Copyleft licenses (like the GPL) require that derivative works also be open source. Permissive licenses (like MIT or BSD) allow modified versions to be incorporated into proprietary products. Both families qualify as FOSS/FLOSS, but they represent different trade-offs between openness and flexibility.

Why these distinctions matter in IPR management

For a law student or IP practitioner in India, these definitions are more than academic. The Indian government’s Policy on Adoption of Open Source Software for Government of India, issued by the Ministry of Electronics and Information Technology (MeitY), explicitly promotes FOSS for e-governance. Understanding what qualifies as “open source” under the OSI’s definition – versus what might merely be “source-available” or freeware – determines whether a software solution actually complies with such a policy.

From an IP standpoint, the licensing model used in FOSS/FLOSS is a sophisticated inversion of traditional copyright. As copyright lawyers note, FOSS licenses use intellectual property law not to restrict, but to guarantee access and freedom. Violations of copyleft licenses are treated as copyright infringement – not breach of contract under the FSF’s interpretation – giving rights holders a powerful legal remedy. Indian developers, startups, and legal professionals working in the software space must grasp these distinctions to advise clients on licensing strategy, compliance, and contribution to open source projects without inadvertently triggering license obligations.

The Free Software Foundation Europe (FSFE) summarizes the practical takeaway well: both free software and open source describe the complete range of licenses that give users the right to use, study, share, and improve software. The terminology debate is real, but it should not obscure the shared legal reality – these are rights, enforceable through copyright law, that users either have or don’t.

Putting it all together

The terms free software, open source, FOSS, and FLOSS all refer to a largely overlapping category of software whose source code is publicly available and whose licenses permit use, study, modification, and redistribution. Where they differ is in emphasis and philosophy. “Free software” stresses user rights and ethics. “Open source” stresses practical development benefits. “FOSS” is a neutral umbrella covering both. “FLOSS” adds “libre” to remove linguistic ambiguity and give equal weight to both movements. “Freeware” and “source-available software,” by contrast, do not belong to this family at all, despite surface-level similarities.

For anyone working in IP law, policy, or software development, knowing which term to use – and why – signals clarity of thinking and avoids costly misunderstandings about what rights a license actually grants.

What do you think? When India’s government mandates “open source” software for e-governance, which definition should control – the OSI’s ten-criterion Open Source Definition, or the FSF’s Four Freedoms? And does the philosophical divide between the free software and open source movements still matter in practice, or has the widespread adoption of FOSS made it largely a historical footnote?

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

References
  1. https://www.gnu.org/philosophy/free-sw.en.html
  2. https://en.wikipedia.org/wiki/The_Free_Software_Definition
  3. https://copyleft.org/guide/comprehensive-gpl-guidech2.html
  4. https://opensource.org/osd
  5. https://fsfe.org/freesoftware/comparison.en.html
  6. https://ajuntamentdebarcelona.github.io/ethical-digital-standards-site/tech-sovereignty/0.1/free-software.html
  7. https://en.wikipedia.org/wiki/Free_and_open-source_software
  8. https://www.gnu.org/philosophy/floss-and-foss.en.html
  9. https://en.wikipedia.org/wiki/Alternative_terms_for_free_software
  10. https://dwheeler.com/essays/commercial-floss.html
  11. https://dwheeler.com/essays/floss-license-slide.html
  12. https://www.meity.gov.in/content/policy-adoption-open-source-software-government-india
  13. https://en.wikipedia.org/wiki/Open-source_license
PDF 📄

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Management of IPRs

1 Overview of Intellectual Property Management

  1. Concept of IP Management
  2. History of Patent Management
  3. History of Brand Management
  4. Importance of Intellectual Property Assets
  5. Intellectual Capital Management Movement
  6. Concept of Hidden Assets

2 Economics of Intellectual Property

  1. Economic of Patents
  2. Creativity and Economic Growth
  3. IPRs as Source of Economic Value
  4. Changing Concepts in IPRs Values
  5. Growth of IP Activity
  6. Intellectual Property Rights and Economic Development
  7. Invention and Innovation Differentiated
  8. Economic Nature of IPRs
  9. Economic Theory and Approaches to IPRs

3 Stages in Intellectual Property Asset Creation

  1. Conception of an Idea
  2. Present Day Inventors
  3. The Difference Between an Idea and an Invention
  4. Actual Method of Inventing
  5. Stages from Mind to Patent

4 Financing of Intellectual Property

  1. Financing of Intellectual Property
  2. Valuation of Intellectual Property Assets
  3. Role of Intellectual Property in Financing
  4. Challenges in Financing IP
  5. Government and IP Financing

5 Theories and Approaches – IP Valuation

  1. Importance of IP Valuation
  2. Reasons for Evaluating IP
  3. Uses for IP Valuation
  4. When Valuation of IP is Required?
  5. Theoretical Approaches to Valuation
  6. Qualitative Evaluation Approach
  7. Quantitative Evaluation Approach
  8. Econometric Approaches to Patent Valuation
  9. Evaluation of Value Indicators: IP Score
  10. Types of Valuation Methods

6 IP Valuation – Methods of Patent Valuation

  1. Why Value Patents?
  2. Patent Suits and Patent Damages
  3. When Patent Valuation is Required?
  4. Who Needs Patent Evaluation?
  5. Popular Methods of Patent Valuation
  6. Econometric Methods of Patent Valuation
  7. Methods to Monetize Patent
  8. Patent Value Predictor Model

7 Intellectual Property Audit

  1. Definition of IP Audit
  2. Intellectual Property Audit Team
  3. When to Conduct an Intellectual Property Audit
  4. Key Areas of IP Audit
  5. Benefits of an Intellectual Property Audit

8 Concept of Intellectual Property and Commercialization

  1. IPR as Natural Rights or Social Privilege
  2. Evolution of Patent Rights
  3. Scientific Property to Commercialization
  4. Restrictions on Patenting of Drugs
  5. Scientific Theories and Invalidation of Patent
  6. Scientific Principles and Patentability
  7. Scientific Discoveries and Utility
  8. Patent Controversy
  9. Commercialization of Intellectual Property in 20th Century
  10. Abuse of Patent Rights and Compulsory Licensing

9 Type of Licensing

  1. What is a License?
  2. The License as Contract
  3. The License as Business Relationship
  4. Inward-Licensing and Outward-Licensing
  5. Voluntary License and Non Voluntary License
  6. Exclusive License Non Exclusive or Sole Licenses
  7. Types of Intellectual Property Licenses
  8. Non-Voluntary or Compulsory Licensing

10 Portfolio Development and Licensing/Cross Licensing

  1. Purpose of Patent Portfolio
  2. Benefits of a Patent Portfolio
  3. Types of Patent Tactics
  4. Licensing
  5. Cross Licensing

11 Royalties for Licensing

  1. Types of Licensing Practices
  2. Royalty Defined
  3. Fixing Royalty Rates
  4. Types of Royalty Payments
  5. Royalty Rate Assessment

12 IP Strategy – Patent Strategies

  1. Defensive Patent Strategy
  2. Offensive Patent Strategy
  3. Transactional Patent Strategy
  4. Patent Trolls

13 Patent Mapping / Data Mining / Freedom to Operate

  1. Definitions
  2. Patent Mapping / Patent Landscaping
  3. Objective of Patent Mapping
  4. Purpose of Patent Mapping
  5. Patent Landscape Search
  6. Difference between Patent Searching and Patent Landscaping
  7. Patent Data Mining
  8. Freedom to Operate (FTO)

14 IP and Standards Patent Pools

  1. History
  2. Standards Defined
  3. Purpose of Standardization
  4. Benefits of Standards
  5. Drawbacks of Standards
  6. Patent Pools
  7. Concerns Over Patents Standards and Trade

15 Open Source

  1. History
  2. Freeware and Free Software
  3. Need for Free Software Distribution
  4. Free Software Movement
  5. Difference Between Free Software and Proprietary Software
  6. Philosophy Behind Open Source Movement
  7. The Open Source Definition (OSD)
  8. Examples of Open Source Software Products
  9. Terms Used in Open Source Definitions
  10. Free Software Foundation vs. Open Source Initiative
  11. Impact of Free/Libre/Open Source Software on Innovation