GNU Affero General Public License
AuthorFree Software Foundation
Latest version3
PublisherFree Software Foundation, Inc.
PublishedNovember 19, 2007
SPDX identifierAGPL-3.0-or-later
AGPL-3.0-only
Debian FSG compatibleYes[1]
FSF approvedYes[2]
OSI approvedYes[3][4]
GPL compatibleYes (permits linking with GPLv3)[5]
CopyleftYes[2] Network-Based
Linking from code with a different licenceOnly with GPLv3; AGPL terms will apply for the AGPL part in a combined work.[2][5]
Websitegnu.org/licenses/agpl.html

The GNU Affero General Public License (GNU AGPL) is a free, copyleft license published by the Free Software Foundation in November 2007, and based on the GNU GPL version 3 and the Affero General Public License.

It is intended for software designed to be run over a network, adding a provision requiring that the corresponding source code of modified versions of the software be prominently offered to all users who interact with the software over a network.[6]

The Open Source Initiative approved the GNU AGPLv3[3] as an open source license in March 2008 after the company Funambol submitted it for consideration through its CEO Fabrizio Capobianco.[7]

Compatibility with the GPL

GNU AGPLv3 and GPLv3 licenses each include clauses (in section 13 of each license) that together achieve a form of mutual compatibility for the two licenses. These clauses explicitly allow the "conveying" of a work formed by linking code licensed under the one license against code licensed under the other license,[8] despite the licenses otherwise not allowing relicensing under the terms of each other.[2] In this way, the copyleft of each license is relaxed to allow distributing such combinations.[2]

Examples of applications under GNU AGPL

Stet was the first software system known to be released under the GNU AGPL, on November 21, 2007,[9] and is the only known program to be used mainly for the production of its own license.

Flask developer Armin Ronacher noted in 2013 that the GNU AGPL is a "terrible success, especially among the startup community" as a "vehicle for dual commercial licensing", and gave Humhub, MongoDB, Odoo, RethinkDB, Shinken, Slic3r, SugarCRM, and WURFL as examples.[10]

MongoDB dropped the AGPL in late-2018 in favor of the "Server Side Public License" (SSPL), a modified version which requires those who offer the licensed software as a service accessible to third-parties, to make the entire source code of all software used to facilitate the service (including without limitation all "management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available") available under the same license.[11] As approval for this license by the Open Source Initiative was not forthcoming the application for certification was withdrawn. It was banned by both Debian and the Fedora Project, who state that the license's intent is to discriminate against cloud computing providers offering services based on the software without purchasing its commercial license.[12][13]

See also

References

  1. ↑ Jaspert, Joerg (November 28, 2008). "ftp.debian.org: Is AGPLv3 DFSG-free?". The Debian Project. Retrieved December 1, 2008.
  2. 1 2 3 4 5 List of free-software licences on the FSF website: "We recommend that developers consider using the GNU AGPL for any software which will commonly be run over a network."
  3. 1 2 "OSI approved licenses". Open Source initiative. Archived from the original on 2021-10-23.
  4. ↑ "OSI approved", Licenses, TL;DR legal.
  5. 1 2 "Licenses section 13", GNU AGPLv3, GNU Project.
  6. ↑ "Why the Affero GPL". The GNU Project. Archived from the original on 2021-10-23.
  7. ↑ "Funambol Helps New AGPLv3 Open Source License Gain Formal OSI Approval" (Press release). Funambol. Mar 13, 2008. Archived from the original on 2013-06-07.
  8. ↑ The GNU General Public License v3 – GNU Project – Free Software Foundation (FSF)
  9. ↑ Kuhn, Bradley M. (November 21, 2007). "stet and AGPLv3". Software Freedom Law Center. Archived from the original on March 15, 2008. Retrieved June 14, 2008.
  10. ↑ Ronacher, Armin (2013-07-23). "Licensing in a Post Copyright World". lucumr.pocoo.org. Archived from the original on 2013-07-27. Retrieved 2015-11-18. The AGPLv3 was a terrible success, especially among the startup community that found the perfect base license to make dual licensing with a commercial license feasible. MongoDB, RethinkDB, OpenERP, SugarCRM as well as WURFL all now utilize the AGPLv3 as a vehicle for dual commercial licensing. The AGPLv3 makes that generally easy to accomplish as the original copyright author has the rights to make a commercial license possible but nobody who receives the sourcecode itself through the APLv3 inherits that right. I am not sure if that was the intended use of the license, but that's at least what it's definitely being used for now.
  11. ↑ "Server Side Public License (SSPL)". MongoDB. Archived from the original on 2021-10-23. Retrieved 2021-01-25.
  12. ↑ Vaughan-Nichols, Steven J. "MongoDB "open-source" Server Side Public License rejected". ZDNet. Archived from the original on 2021-10-23. Retrieved 2019-01-17.
  13. ↑ "MongoDB's licensing changes led Red Hat to drop the database from the latest version of its server OS". GeekWire. 2019-01-16. Archived from the original on 2021-10-23. Retrieved 2019-01-17.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.