Affero General Public License
Generated by GPT-5-miniExpansion Funnel Raw 95 → Dedup 0 → NER 0 → Enqueued 0
| Affero General Public License | |
|---|---|
 Free Software Foundation · Public domain · source | |
| Name | Affero General Public License |
| Author | Affero, Inc.; Free Software Foundation |
| Date | 2002 |
| License | copyleft, free software |
| Source model | Open source |
| Osi approved | No (original), Yes (later variants) |
Affero General Public License
The Affero General Public License emerged as a response to networked software distribution debates involving Free Software Foundation, GNU Project, Richard Stallman, Harvard University, Massachusetts Institute of Technology. It sought to address remote interaction use cases raised by Apache HTTP Server, Mozilla Firefox, MySQL, Red Hat, providing an alternative approach to distribution-focused instruments such as GNU General Public License, Berkeley Software Distribution, MIT License. The license intersected with discussions at Electronic Frontier Foundation, OSI, European Commission, and influenced projects connected to Debian, Ubuntu, OpenOffice, LibreOffice.
History
The license was drafted in part by developers associated with Affero, Inc. and debated within forums including Free Software Foundation, GNU Project, Open Source Initiative, with public commentary from representatives of Debian Project, FSF Europe, Software Freedom Law Center, and corporate entities such as Sun Microsystems, IBM, Google. Early versions responded to incidents like distribution debates around Server-side scripting languages, controversies connected to MySQL AB, PHP Group, and legal considerations discussed at venues including DEF CON, FOSDEM, LinuxCon. Over time, the trajectory included reinterpretation by attorneys at Electronic Frontier Foundation, Software Freedom Conservancy, and adoption discussions at Apache Software Foundation, GNOME Foundation, KDE e.V..
Versions and Variants
Notable iterations include the original Affero release and later harmonized texts associated with Free Software Foundation efforts, paralleled by variants influenced by GNU Affero General Public License drafting, contributions by legal teams from Software Freedom Law Center, Fei-Fei Li-adjacent academic technologists at Stanford University, and consultations with Harvard Berkman Klein Center. Forks and localizations were created by communities around Debian Project, Fedora Project, Arch Linux, and by companies such as Canonical Ltd., SUSE, Red Hat. The evolution mirrors versioning practice evident in GNU General Public License version 2, GNU General Public License version 3, and compatibility discussions similar to those surrounding Mozilla Public License and Eclipse Public License.
Key Provisions
Primary terms require source availability when users interact via networked services, reflecting concerns raised by projects like Amazon Web Services, Google Cloud Platform, Heroku, and by initiatives including OpenStack, Kubernetes, Docker. The text addresses modification disclosure obligations, patent-related clauses debated by Microsoft, Oracle Corporation, Apple Inc., and includes termination and injunction mechanics similar to language in GPLv3 drafts considered by Richard Stallman and legal advisors from SFLC. Clauses also engage with contributor licensing models practiced in Apache License 2.0 projects, trademark considerations linked to Linux Foundation projects, and compatibility topics seen in Creative Commons discussions.
Compatibility and Licensing Issues
Questions of compatibility invoked stakeholders such as Free Software Foundation, Open Source Initiative, Debian Project, and corporations like Red Hat, IBM, Google, especially where combined works referenced GNU Lesser General Public License, Apache License 2.0, MIT License, BSD licenses. Legal analysis by entities such as Software Freedom Conservancy, Software Freedom Law Center, Electronic Frontier Foundation, and commentary from academics at Harvard Law School and Stanford Law School examined interplay with patent grants, copyleft scope, and distribution definitions as litigated in cases or debates involving Oracle Corporation and Sun Microsystems. Compatibility debates also reflected practices in ecosystems centered on GitHub, GitLab, Bitbucket, and package systems like npm, PyPI, CPAN.
Adoption and Notable Use Cases
Adoption occurred among projects concerned with network-deployed software, including web applications originating from communities around GNU Project, OpenStack Foundation, Eclipse Foundation, and companies such as Diaspora Project, Mastodon, and smaller organizations influenced by Mozilla Foundation policies. Platforms for collaborative editing and content management similar to MediaWiki, Drupal, WordPress featured community discussions of switching to Affero-like terms, and research groups at MIT Media Lab, Stanford University, UC Berkeley evaluated institutional policy impacts. Several startups and non-profits dealing with cloud computing services and social platforms weighed Affero-style terms against permissive alternatives used by Facebook, Twitter, LinkedIn.
Controversies and Legal Interpretations
Controversy arose over enforceability in jurisdictions including United States, European Union, United Kingdom, and litigation-adjacent interpretations were debated by counsel from Software Freedom Law Center, Electronic Frontier Foundation, Public Knowledge, and academics at Yale Law School, Columbia Law School. Critics from organizations like Apache Software Foundation, Debian Project, and corporations such as Red Hat and Oracle Corporation argued about incompatibility with existing ecosystems and business models exemplified by Amazon Web Services, Microsoft Azure, Google Cloud Platform. Supporters cited precedent from copyleft enforcement by Free Software Foundation and community governance practices seen at GNU Project and Debian Project to defend public network-source requirements.