LLMpediaThe first transparent, open encyclopedia generated by LLMs

BSD license

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Open Source Initiative Hop 4
Expansion Funnel Raw 58 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted58
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
BSD license
NameBSD license
FamilyPermissive free and open-source software licenses
Source modelCopyright law
Date1990
Variants2-clause, 3-clause, 4-clause (original)

BSD license The BSD license is a family of permissive free and open-source software licenses originating from the University of California, Berkeley and used to govern redistribution and modification of software released under its terms. It emphasizes minimal restrictions on reuse, permitting binary redistribution, proprietary relicensing, and attribution, and it has influenced many projects across UNIX-derived systems, academic research, and commercial development.

Overview

The BSD license family grants rights to copy, modify, and distribute software while requiring preservation of copyright notices and disclaimers, with variations that affect advertising and endorsement clauses; notable institutions associated include the University of California, Berkeley, the FreeBSD Foundation, the OpenBSD project, the NetBSD Foundation, and corporate adopters such as Apple Inc., Google, and Microsoft. Its permissive stance contrasts with reciprocal terms championed by organizations like the Free Software Foundation, the Open Source Initiative, and projects such as GNU Project, Linux kernel, and Debian. The license text interacts with legal systems including the United States copyright law, international treaties like the Berne Convention, and court decisions involving software licensing disputes.

History

The license traces to the distribution policies of the Berkeley Software Distribution developed at the Computer Systems Research Group of the University of California, Berkeley during the late 1970s and 1980s, where contributors such as researchers collaborating with entities like DARPA and publications in venues tied to ACM and IEEE influenced software sharing norms. Early BSD releases incorporated an advertising clause reflecting obligations to acknowledge funding from agencies such as National Science Foundation and companies including AT&T Corporation, later prompting debate with advocates from the Free Software Foundation and maintainers of projects like NetBSD and FreeBSD, leading to revised 2-clause and 3-clause forms. Significant events in its evolution include litigation and policy shifts within institutions such as the University of California and interplay with corporate adoption by companies like Sun Microsystems and IBM.

Key Terms and Variants

Common variants include the original 4-clause BSD with an advertising clause, the 3-clause BSD removing the advertising requirement but retaining a non-endorsement clause, and the 2-clause BSD simplifying obligations to redistribution and disclaimer; these variants are maintained and promoted by projects and organizations including FreeBSD, OpenBSD, NetBSD, the FreeBSD Foundation, and corporate legal teams at Google and Apple Inc.. Key terms reference copyright notices, warranty disclaimers, redistribution in source and binary forms, and endorsement prohibitions, which intersect with interpretations advanced by bodies like the Open Source Initiative, legal analyses from firms appearing before courts such as the United States Court of Appeals, and academic commentary in journals tied to Harvard Law School and Stanford Law School.

The canonical BSD license text comprises short clauses addressing permission to use, redistribute, and modify, accompanied by a warranty disclaimer; legal interpretation has involved analysis from practitioners at firms that litigate under United States law as well as comparative studies in legal scholarship from institutions including Yale Law School and Columbia Law School. Courts have considered issues of warranty, attribution, and endorsement in contexts overlapping with other regimes administered by bodies like the World Intellectual Property Organization and have contrasted permissive terms with conditions in licenses upheld in cases involving entities such as Oracle Corporation and Microsoft. Legal counsel at foundations such as the Free Software Foundation and the Open Source Initiative provide guidance on compatibility, while universities such as MIT and Stanford University publish policy analyses on license compliance.

Adoption and Notable Use

The BSD license family underpins major operating system projects including FreeBSD, OpenBSD, NetBSD, and derivatives used by corporations like Apple Inc. for Darwin, and it is applied in libraries and tools developed at institutions including Massachusetts Institute of Technology, Carnegie Mellon University, and commercial projects from Intel, Cisco Systems, and ARM Holdings. Widely used software with BSD-family licensing includes network stacks and utilities incorporated into distributions overseen by organizations such as Debian Project, NetBSD Foundation, and proprietary products by firms like Cisco Systems and Juniper Networks. Academic projects at University of California, Berkeley, research groups funded by National Science Foundation, and collaborative initiatives coordinated through consortia like The Apache Software Foundation have engaged with BSD-licensed components.

Comparison with Other Open-Source Licenses

Compared with copyleft licenses such as the GNU General Public License and the Affero General Public License, the BSD family imposes fewer obligations on downstream redistribution and permits proprietary relicensing, which affects adoption by companies including Microsoft and Apple Inc. and influences policy discussions within organizations like the Free Software Foundation and the Open Source Initiative. Versus permissive licenses like the MIT License and the ISC license, differences hinge on wording about attribution, endorsement, and compatibility; license compatibility has been analyzed by projects like Debian Project, legal teams at Mozilla Foundation, and academic centers at Harvard Law School and Stanford Law School. Governance and community norms around license choice appear in debates at venues such as Kernel Summit, FLOSS conferences, and in documentation by foundations including Open Source Initiative and Software Freedom Conservancy.

Category:Software licenses