Free and open-source software (FOSS)

Core characteristics

FOSS projects typically provide a set of explicit rights through a license: the right to use the software for any purpose, to inspect how it works, to make and publish improvements, and to share copies with others. Those rights are enforced by legal licenses rather than by technical restrictions. Common examples of such licenses include the GNU General Public License (GPL), the Lesser GPL (LGPL), and permissive licenses such as the BSD family.

Licenses and distribution models

Licenses fall into two broad classes: copyleft (or reciprocal) licenses, which require derivative works to carry the same license terms, and permissive licenses, which allow code to be incorporated into proprietary projects without the same reciprocity. Organizations choose licenses according to goals for control, compatibility, and commercialization. For discussion of freedom-oriented philosophy, see Free software.

History and development

The modern FOSS movement traces its roots to academic sharing of software and to activist projects in the late 20th century that emphasized user freedoms and collaborative development. Over decades, communities around kernel, office, and development tools grew; prominent examples include the Linux kernel and suites such as LibreOffice. Development is often collaborative: contributors from individuals to corporations submit patches, review code, and maintain releases.

Uses, examples, and importance

FOSS is widely used in servers, desktops, embedded devices, scientific research, and public infrastructure. Organizations adopt it for reasons including transparency, cost control, security audits, and vendor independence. Business models built around FOSS include paid support, managed hosting, dual licensing, and open-core products where a permissively licensed core is supplemented by proprietary components.

Notable distinctions and considerations

• "Free" vs. "gratis": freedom does not always mean free of charge; commercial distribution and paid services are common.
• Governance varies: some projects are led by foundations, some by companies, and others by loose volunteer communities.
• Legal and compatibility issues can arise when combining code under different licenses; projects typically track compatibility carefully.

FOSS continues to influence software practices by promoting reuse, peer review, and collaborative innovation while offering multiple pathways for both community-driven and commercial ecosystems.