Educational Community License

Educational Community License
Name	Educational Community License
Author	University of California, Berkeley
Date	2003
Family	Permissive software license
Source model	Open-source software
Spdx license id	ECL-2.0

Educational Community License

The Educational Community License is a permissive open-source software license intended for use by educational institutions, research organizations, and related nonprofit organizations. It provides terms for redistribution and modification while preserving contributor attribution and patent grants, aiming to balance the interests of the University of California, Berkeley, Indiana University Bloomington, The Apache Software Foundation, and other stakeholders in the academic community. The license has been adopted by projects associated with institutions such as Massachusetts Institute of Technology, Stanford University, Harvard University, Carnegie Mellon University and international entities like University of Oxford.

Overview

The license is patterned after permissive texts like the Apache License and the BSD license, integrating provisions influenced by the GNU General Public License clarity on patent rights and the MIT License simplicity. It was designed to cover software distributed by institutions including University of Chicago, Princeton University, Yale University, Columbia University, and University of Michigan. Typical beneficiaries include projects hosted by GitHub, SourceForge, Eclipse Foundation, and Apache Software Foundation incubators. The license text has been reviewed by organizations such as Electronic Frontier Foundation and legal teams at Microsoft Corporation, Oracle Corporation, and IBM for compatibility with corporate contributions.

History and Development

Origins trace to collaborative efforts among legal counsels at University of California, Berkeley, Indiana University Bloomington, and community contributors from projects like Sakai and Kuali. Early drafts referenced precedent from the Apache License 1.1, the BSD license, and guidance used at MITRE Corporation. The license saw formalization amid discussions at meetings involving representatives from Carnegie Mellon University, National Science Foundation, and venture partners including Red Hat and Sun Microsystems. Subsequent revisions aligned with changes in patent policy debated at forums such as the Open Source Initiative conferences and advisories from American University Washington College of Law clinics. Notable contributors included counsel associated with University of California Office of the President and technology transfer offices at Johns Hopkins University and University of Pennsylvania.

License Terms and Conditions

Key terms include a grant of rights to use, copy, modify, and distribute source and binary forms, coupled with a requirement to retain attribution notices and disclaimers. It incorporates a patent license clause similar to that found in the Apache License 2.0 and addresses contributor license agreements as used by The Linux Foundation and Mozilla Foundation. The license demands preservation of notices for projects hosted by Internet2 consortia and aligns with export control considerations seen in policies from Defense Advanced Research Projects Agency collaborations. The text specifies limitation of liability and warranty disclaimers comparable to those used by Creative Commons in software-related frameworks.

Compatibility and Interoperability

Compatibility with other permissive licenses—such as the MIT License and the BSD license—facilitates integration with ecosystems managed by Debian Project, Ubuntu, and Fedora Project. Interoperability with copyleft licenses like the GNU General Public License depends on version interactions and patent clauses debated by the Free Software Foundation. Corporate entities including Google LLC and Amazon Web Services have evaluated compatibility for inclusion in cloud services alongside projects from Linux Foundation and Kubernetes-related initiatives. Legal interoperability has been analyzed in guidance from firms such as DLA Piper and academic centers like Harvard Law School's Berkman Klein Center.

Adoption and Notable Projects

Projects using the license include academic and research platforms such as Sakai Project, uPortal, and components developed by Kuali Foundation. Major institutions including Indiana University Bloomington, Duke University, Northwestern University, University of Illinois at Urbana–Champaign, and Penn State University have released software under the license. Community platforms hosted on GitLab and Bitbucket also show instances of adoption. International collaborations involving University of Melbourne, University of Toronto, and McGill University have released tools under this license for educational technology and research computing.

Legal and Community Responses

Legal commentary from entities like Electronic Frontier Foundation, American Bar Association, and university legal clinics at University of California, Berkeley School of Law has highlighted the license's balance of permissiveness and patent clarity. Community responses from open-source advocates at Open Source Initiative, contributors associated with Apache Software Foundation, and maintainers in the Debian Project have examined its use in academic projects. Some corporate legal departments at IBM, Microsoft Corporation, and Oracle Corporation have issued internal guidance regarding contributions under the license. Discussions at conferences including FOSDEM, OSCON, and Open Source Summit have shaped perceptions of its suitability for institutional software releases.

Comparison with Other Open Source Licenses

Compared with the Apache License 2.0, the license shares patent grant language and attribution requirements, while differing in institutional phrasing favored by university technology transfer offices at MIT Technology Licensing Office and Stanford Office of Technology Licensing. Against permissive texts like the MIT License and the BSD license, it adds explicit contributor and patent language similar to terms discussed by the Free Software Foundation for license compatibility. When contrasted with copyleft instruments such as the GNU General Public License and Affero General Public License, it imposes fewer distribution obligations, making it attractive to stewardship models used by The Apache Software Foundation and academic consortia like Internet2.

Category:Software licenses