{"id":21308,"date":"2020-01-30T11:39:05","date_gmt":"2020-01-30T11:39:05","guid":{"rendered":"https:\/\/www.arimetrics.com\/glosario-digital\/open-source"},"modified":"2026-09-28T05:32:55","modified_gmt":"2026-09-28T05:32:55","slug":"open-source","status":"publish","type":"encyclopedia","link":"https:\/\/www.arimetrics.com\/en\/digital-glossary\/open-source","title":{"rendered":"Open Source"},"content":{"rendered":"

\"OpenDefinition:<\/strong><\/p>\n

Open Source<\/strong> is software whose source code is distributed under a license that allows people to use, study, modify, and redistribute it, including derived versions. These rights remain subject to the conditions of the applicable license.<\/p>\n

Access to the code alone does not make a program Open Source. The license must grant effective modification and distribution rights without restrictions that conflict with the open model. The software remains protected by copyright and may carry obligations concerning attribution, notices, or the publication of modified source code.<\/p>\n\n

Origins and scope of Open Source<\/h2>\n

The term Open Source was adopted in 1998 to describe a software distribution model based on open licenses and collaborative development. The Open Source Initiative (OSI) was established that year and now maintains the Open Source Definition<\/a> and reviews licenses against its criteria.<\/p>\n

The OSI definition requires, among other conditions, free redistribution, availability of source code, permission to create derived works, and no discrimination against people, groups, or fields of endeavor. A license is not open merely because it allows people to read the code<\/strong>.<\/p>\n

Open Source may also describe transparent and collaborative development practices. A project can publish its repository without accepting external contributions, however, and an open community does not replace the legal permissions granted by its license.<\/p>\n

How an open project works<\/h2>\n

Development is commonly organized around a repository containing the source code<\/a>, change history, and supporting documentation. Maintainers review contributions, fix defects, prepare releases, and decide the technical direction of the project.<\/p>\n

Users may report issues, propose changes, or create an independent copy, known as a fork, when the license permits it. The right to modify the software does not require the original project to accept every contribution<\/strong>, nor does it grant access to the project’s infrastructure, trademarks, or official channels.<\/p>\n

Governance may rest with an individual, community, foundation, or company. Some projects accept public contributions, while others develop in the open but keep decision-making within a small group. Licensing, contribution processes, and governance are therefore related but distinct dimensions.<\/p>\n

Open Source licenses<\/h2>\n

Licenses determine how a program may be used and which conditions apply when it is redistributed. Two common families are permissive licenses and copyleft licenses.<\/p>\n

Permissive licenses, including MIT, BSD, and Apache License 2.0, allow reuse with relatively few obligations, usually requiring preservation of copyright and license notices. Apache License 2.0 also includes explicit patent provisions.<\/p>\n

Copyleft<\/a> licenses such as the GNU GPL allow modification and distribution but require certain derived versions to remain under the same license and make their source code available. Other licenses apply reciprocal conditions to a file, library, or software offered over a network.<\/p>\n

License compatibility must be checked before combining components<\/strong>. The fact that two programs are Open Source does not mean their conditions can be incorporated into every distribution without adjustment.<\/p>\n

Differences from related concepts<\/h2>\n

Open Source is related to several distribution models, but it is not equivalent to all of them:<\/p>\n

    \n
  • Free software:<\/strong> Protects four freedoms to run, study, modify, and share a program. Much free software is also Open Source, although the two movements use different frameworks and priorities.<\/li>\n
  • Freeware:<\/strong> Is available at no price but may keep its source code closed and prohibit modification or redistribution.<\/li>\n
  • Source-available software:<\/strong> Allows the code to be inspected but may restrict commercial use, redistribution, or derived works. Such restrictions can prevent the license from qualifying as Open Source.<\/li>\n
  • Public domain software:<\/strong> Has no applicable exclusive rights or has been dedicated to the public domain where the law permits. Open Source software, by contrast, usually retains copyright and is used under a license.<\/li>\n<\/ul>\n

    Proprietary software restricts access to the code or the rights to modify and distribute it. It may be free of charge or commercial, just as an Open Source program may be distributed without charge or sold with support, hosting, and other services.<\/p>\n

    Examples of Open Source projects<\/h2>\n

    Open projects include operating systems, web publishing tools, browsers, email clients, and data analysis software. Established examples include:<\/p>\n

      \n
    • Linux:<\/strong> A kernel used in many distributions and systems, released under GNU GPL version 2.<\/li>\n
    • WordPress:<\/strong> A content management system distributed under GNU GPL version 2 or later.<\/li>\n
    • Mozilla Firefox:<\/strong> A browser whose code is primarily released under Mozilla Public License 2.0.<\/li>\n
    • Thunderbird:<\/strong> An email and calendar client developed as an open project under Mozilla Public License 2.0.<\/li>\n
    • Matomo:<\/strong> A digital analytics platform that provides an installable edition under GNU GPL version 3.<\/li>\n
    • R:<\/strong> A language and environment for statistics and visualization distributed as free and open-source software.<\/li>\n<\/ul>\n

      GitHub can host and coordinate Open Source projects, but the platform does not automatically make the software it contains open<\/strong>. Each repository must state its own license. Without one, the author’s exclusive rights apply by default.<\/p>\n

      Contributions of the open model<\/h2>\n

      Access to the code supports technical inspection, adaptation to specific needs, and continuation of a project if its original maintainers stop working on it. It also enables teams to reuse existing components and share fixes with organizations facing similar problems.<\/p>\n

      A diverse group of participants may broaden review and accelerate defect detection, but the outcome depends on the project’s actual activity. The ability to audit code does not mean that someone has reviewed it<\/strong>, and it does not by itself guarantee security, quality, or freedom from vulnerabilities.<\/p>\n

      For businesses and public institutions, an open license may reduce dependence on one vendor and provide more choices for hosting, support, or development. It does not remove the costs of implementation, integration, maintenance, training, or license compliance.<\/p>\n

      Limitations and responsibilities<\/h2>\n

      A project may have limited documentation, few maintainers, or irregular release cycles. Its recent activity, vulnerability handling, compatibility, governance, and support options are relevant when another system depends on it.<\/p>\n

      Open Source licenses generally disclaim warranties and limit author liability. Anyone redistributing or incorporating the software must preserve notices, provide source code when required, and follow other applicable conditions. Dependencies, trademarks, and possible patent rights may also require review.<\/p>\n

      The open model provides rights to study, modify, and share technology, but sustainable use requires maintenance, governance, and legal compliance<\/strong>. The license defines the basic freedoms, while the quality of the project depends on how its components are developed and maintained.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Open Source software can be used, studied, modified, and redistributed under an open license. Learn about licenses, examples, benefits, and limitations.<\/p>\n","protected":false},"author":7,"featured_media":80861,"template":"","encyclopedia-tag":[1279],"class_list":["post-21308","encyclopedia","type-encyclopedia","status-publish","has-post-thumbnail","hentry","encyclopedia-tag-software-licensing"],"_links":{"self":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia\/21308","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia"}],"about":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/types\/encyclopedia"}],"author":[{"embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/users\/7"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/media\/80861"}],"wp:attachment":[{"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/media?parent=21308"}],"wp:term":[{"taxonomy":"encyclopedia-tag","embeddable":true,"href":"https:\/\/www.arimetrics.com\/en\/wp-json\/wp\/v2\/encyclopedia-tag?post=21308"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}