BSD 3-Clause License

BSD 3-Clause License The BSD 3-Clause License is a permissive open-source software license that grants broad rights to use, modify, and redistribute code with limited restrictions. It is widely used in projects originating from academic institutions and technology organizations and has influenced license choices at companies and foundations worldwide. The license balances attribution requirements with minimal obligations, making it popular in ecosystems associated with Unix-like systems and network infrastructure.

History

The BSD 3-Clause License originated from the licensing practices at the University of California, Berkeley, following work on the Berkeley Software Distribution and collaborations with contributors such as those at DARPA, Bell Labs, and researchers associated with Project MAC. Early licensing debates involved institutions like Massachusetts Institute of Technology, Stanford University, and entities influenced by legal analyses from the Electronic Frontier Foundation and counsel advising Sun Microsystems and AT&T Corporation. The three-clause text evolved from the older four-clause University of California license after controversies linked to advertising requirements involving publications like IEEE proceedings and discussions in venues such as the USENIX conferences and the ACM Digital Library. Adoption grew through distribution channels maintained by organizations including FreeBSD, NetBSD, and OpenBSD, and it spread into projects hosted by infrastructure providers such as GitHub, SourceForge, and corporate stewards like IBM and Intel Corporation.

Terms and Conditions

The license requires preservation of copyright notices and a disclaimer of warranty by original copyright holders such as universities, companies like Red Hat, and developer contributors from groups like the Apache Software Foundation. It contains three operative clauses: retention of copyright and license text in redistributions, a prohibition on using the names of copyright holders to endorse derived products, and a warranty disclaimer limiting liability against plaintiffs such as private litigants and agencies like Federal Trade Commission. The clause barring endorsement references institutions and trademarks, often invoking policy concerns similar to those addressed by counsel from firms working with clients like Microsoft or Google. The warranty and liability language mirrors formulations debated in case law involving courts such as the United States Court of Appeals for the Ninth Circuit and doctrines discussed in journals affiliated with Harvard Law School and Yale Law School faculty.

Differences from Other BSD Licenses

Compared with the original four-clause BSD license used at University of California, Berkeley, the three-clause variant removes the advertising clause that required mention in promotional materials, aligning it with positions taken by projects like Linux kernel and foundations such as the Mozilla Foundation. Against the two-clause "Simplified BSD License" favored by organizations like Canonical and projects like OpenJDK, the three-clause license retains an explicit non-endorsement clause similar to terms employed by corporations including Apple Inc. and Facebook. In contrast to copyleft licenses used by entities such as the Free Software Foundation for GNU General Public License projects, the BSD 3-Clause imposes no reciprocal source-distribution obligations, a stance reflected in policy debates at conferences like FOSDEM and in governance discussions at bodies such as the Linux Foundation.

Compatibility and Use in Projects

The BSD 3-Clause License is compatible with many permissive and copyleft licenses and is commonly incorporated into stacks maintained by organizations like Debian, Fedora Project, and project ecosystems including Kubernetes and Docker. Enterprises such as Amazon (company), Microsoft Corporation, and Oracle Corporation have used BSD-licensed components in proprietary and open offerings, while foundations like the Open Source Initiative and Eclipse Foundation recognize its permissive nature for community collaboration. The license's attribution requirements make it straightforward to combine BSD 3-Clause code with libraries under licenses from entities like the Free Software Foundation and protocols standardized by IETF. Major software systems such as PostgreSQL, OpenSSH, and toolchains originating from GNU Project contributors have historically interoperated with BSD-licensed components in distributed systems deployed by providers like Google Cloud and Microsoft Azure.

Legal Interpretation and Enforcement

Legal interpretation of the BSD 3-Clause License has been shaped by litigation and counsel involving corporate actors like Oracle Corporation and academic licensors such as Cornell University. Enforcement typically focuses on preservation of copyright notices and the non-endorsement clause, with dispute resolution informed by precedents from courts including the United States Supreme Court and circuit courts that have considered issues of license preemption and contract formation in software contexts. Law reviews from institutions such as Columbia Law School and Stanford Law School have analyzed the license's warranty disclaimers in the context of product liability and commercial distribution, while transactional practices at firms representing clients like Cisco Systems and HP Inc. guide compliance strategies. Internationally, adoption and interpretation intersect with statutes and regulatory bodies in jurisdictions including the European Union and national courts in countries corporate licensors operate in, influencing licensing decisions by multinationals like Samsung Electronics and Siemens.

Category:Software licenses