Other meanings of Open-source software development
SOFTWARE ENGINEERING
Open-source software development is the development of software whose source code is openly available for modification and redistribution. The defining feature is not merely public access to code, but a license granting recognized rights to inspect, change, share, and reuse it. Projects may be volunteer-led, commercially sponsored, foundation-governed, or organized through a mixture of these models.
Open-source development combines publicly accessible source code with a license that permits modification and redistribution. The Open Source Definition requires rights such as free redistribution, access to source code, permission for derived works, and non-discrimination among users or fields of endeavor.1 This distinguishes open-source software from a source-available product whose code can be viewed but not freely reused. The related free software tradition expresses the same broad territory through user freedoms to run, study, modify, and share software.2
Licenses shape the practical boundaries. Permissive licenses generally allow reuse in proprietary products, while copyleft licenses require specified redistributed derivatives to preserve corresponding freedoms. The license is therefore part of the engineering design, not an administrative afterthought.
Open-source projects coordinate distributed contributors through visible version history, review, issue tracking, documentation, and release practices. Git is widely used to record changes as commits and to merge work through branches or comparable workflows; its distributed design allows contributors to work independently before proposing changes to a shared project.4 Automated tests, continuous integration, linters, and reproducible build procedures help maintain quality when contributors have different environments and levels of familiarity.
Governance determines who can merge code, interpret the project’s technical direction, resolve disputes, and make releases. Some projects use a benevolent maintainer, others use elected committees, foundations, or corporate steering groups. The Debian project illustrates a formal social contract and community guidelines that connect technical work with commitments about licensing and user freedom.3
Open-source development can enable peer review, reuse, interoperability, and rapid adaptation because a project’s code and discussion are available to a broad community. Companies may contribute upstream to reduce duplicated maintenance, influence project direction, or build services around a shared platform. Research has found that widely used open-source software represents substantial economic value while being supported by uneven patterns of paid contribution and maintenance.
Openness does not guarantee security, usability, or long-term maintenance. Projects can suffer from abandoned dependencies, concentrated knowledge, weak documentation, or an overloaded maintainer. Security work increasingly treats the software supply chain as a system requiring provenance, dependency analysis, vulnerability response, and controlled build processes. The NIST Secure Software Development Framework provides practices that can be applied to open and closed development alike.5
Open-source development includes more than writing code: translation, accessibility testing, design, documentation, release engineering, security triage, and community moderation can be decisive contributions. A project may also combine multiple licenses, use contributor license agreements, or offer dual licensing to serve both community and commercial users. These arrangements affect who may redistribute modified versions and how downstream products are built.
Small maintenance decisions can have large consequences. A change to a widely depended-on library may propagate through thousands of applications, while a minor documentation correction can remove a barrier for future contributors. The Linux kernel demonstrates a highly specialized review culture in which subsystem maintainers, mailing lists, signed-off contributions, and staged integration support a very large codebase.6 Open governance can therefore coexist with strict technical gatekeeping.
Open-source development describes a licensing and collaboration model; it does not require that software be free of charge, volunteer-produced, or governed without commercial participation.
Help improve the encyclopedia. Reports go straight to the site manager.