Open source software

Characteristics and common practices

Open source projects typically exhibit several recurring features that shape how they are created and used:

• Source availability: the original program code is distributed so people can review how it works.
• Right to modify and redistribute: contributors can alter the code and share their improvements under the terms of a license.
• Collaborative development: many projects are built by a community of volunteers and companies working together, often using version control systems and public issue trackers.
• Transparency and auditability: open access to code makes it easier to find bugs, verify security, and understand behavior.
• Integration with business: companies use open source in product stacks and offer services, support, or hosted versions as commercial models (business models).
• Language and tooling: open source software is written in many programming languages and commonly packaged to be reused across ecosystems.

Licenses and legal distinctions

Licensing defines what users may do with open source code. Broadly, licenses fall into two categories: permissive and copyleft. Permissive licenses (for example, the BSD family) allow code to be reused with minimal obligations. Copyleft licenses (for example, the GPL family) require that derivative works be distributed under the same or compatible terms, preserving recipients' rights. The opposite model is closed source, where the source is not shared and redistribution is restricted. Popular open source licenses include the GNU GPL, LGPL and the BSD licenses.

History and development

The practices behind open source grew from decades of shared code and academic cooperation. Early collaborative efforts and permissive redistributions in academic and hobbyist communities set the stage for larger projects. The modern distinction between the "free software" and "open source" labels became more prominent in the late 1990s, when an industry-oriented movement and the Open Source Initiative formalized the open source term and principles. Communities around Unix-like systems such as Linux and BSD played a central role in demonstrating the productivity and reliability of community-developed software over time [history].

Uses, examples, and importance

Open source software appears across computing and the internet: operating systems, web servers, developer tools, content management systems and more. Well-known examples include Linux-based operating systems, the Apache web server, Mozilla projects, office suites and content platforms. Many widely used services and websites are built on open source components; for instance, collaborative encyclopedia software behind projects like Wikipedia is itself open source. Organizations adopt open source to reduce vendor lock-in, accelerate innovation, and leverage community testing.

Notable distinctions and practical considerations

When choosing or contributing to open source software, practitioners consider license compatibility, governance (who makes decisions), contributor agreements, and security processes. Businesses may combine open source with proprietary offerings via dual licensing or provide paid hosting and support. The open source model does not guarantee quality by itself, but when combined with active maintenance, transparent review and good governance it can produce robust, widely trusted software used in servers, devices and cloud infrastructure around the world.