AGPL

Producing Open Source Software: How to Run a Successful Free Software Project

by Karl Fogel  · 13 Oct 2005

network—that is, the software is usually part of a hosted service, rather than being distributed as a binary—then consider using the GNU Affero GPL instead. The AGPL is just the GPL with one extra clause establishing network accessibility as a form of distribution for the purposes of the license. See the

…

section called “The GNU Affero GPL: A Version of the GNU GPL for Server-Side Code” in Chapter 9, Legal Matters: Licenses, Copyrights, Trademarks and Patents for

…

license is the GNU General Public License (along with its network-oriented variant, the Affero GNU General Public License or AGPL, introduced later in this chapter in the section called “The GNU Affero GPL: A Version of the GNU GPL for Server-Side Code”), and one of the most important considerations in choosing

…

reflect this: GNU General Public License version 3 (GPL-3.0, gnu.org/licenses/gpl.html) GNU Affero General Public License version 3 (AGPL-3.0, gnu.org/licenses/agpl.html) Mozilla Public License 2.0 (MPL-2.0, mozilla.org/MPL) GNU Library or "Lesser" General Public License version 3 (LGPL

…

solve some future license compatibility problem that couldn't have been anticipated now (for example, see the compatibility discussion in the section called “The GNU Affero GPL: A Version of the GNU GPL for Server-Side Code” below). Not everyone feels the same way, however; most notably, the Linux kernel is famously

…

option or not. You now know that you have the choice, at least, and that different people come to different conclusions about it. The GNU Affero GPL: A Version of the GNU GPL for Server-Side Code In 2007, the Free Software Foundation released a variant of the GPL called the GNU

…

Affero GPL[93]. Its purpose is to bring copyleft-style sharing provisions to the increasing amount of code being run as hosted services — that is, software that

…

. The Wikipedia article on the AGPL is excellent: en.wikipedia.org/wiki/Affero_General_Public_License The Copyright Holder Is Special, Even In Copyleft Licenses One common misunderstanding is that licensing

…

was originally released by Affero, Inc, who based it on the GNU GPL version 2. At the time, this was commonly referred to as the AGPL. Later, the Free Software Foundation decided to adopt the idea, but by then they had released version 3 of their GNU GPL, so they based

…

their new Affero-ized license on that and called it the "GNU AGPL". The old Affero license is now rarely used and is more or less deprecated, but to avoid ambiguity, say

Roads and Bridges

by Nadia Eghbal  · 139pp  · 35,022 words

“dual license” to monetize their work, charging companies for access to a permissive MIT license instead of a more restrictive AGPL license that would require attribution. His theory is that by making AGPL the default license, businesses will pay to avoid it. To support this idea, Perham reminded his audience: Remember: Open

Seven Databases in Seven Weeks: A Guide to Modern Databases and the NoSQL Movement

by Eric Redmond, Jim Wilson and Jim R. Wilson  · 7 May 2012  · 713pp  · 93,944 words

. It’s important to note that all of the tools we used today require the Neo4j Enterprise edition, and so use a dual license—GPL/AGPL. If you want to keep your server closed source, you should look into switching to the Community edition or getting an OEM from Neo Technology

Forge Your Future with Open Source

by VM (Vicky) Brasseur  · 266pp  · 79,297 words

company policy as far as compliance, security, and approved licenses. Some companies, for instance, have a blanket ban on using the Affero GNU Public License (AGPL) or other copyleft licenses. Because these FOSS usage policies are highly specific to each company, I do not cover using FOSS for work in this

Ansible for DevOps: Server and Configuration Management for Humans

by Jeff Geerling  · 9 Oct 2015  · 313pp  · 75,583 words

consider something that requires more configuration (e.g. a distributed file system) and/or more hardware (e.g. a SAN). GlusterFS is licensed under the AGPL license, has good documentation, and a fairly active support community (especially in the #gluster IRC channel). But to someone new to distributed file systems, it

Mastering Structured Data on the Semantic Web: From HTML5 Microdata to Linked Open Data

by Leslie Sikos  · 10 Jul 2015

most commonly used graph databases is summarized in Table 6-1. 146 GPL/ Proprietary Proprietary Proprietary Public Domain Proprietary Apache Proprietary Apache Proprietary LGPL Proprietary AGPL/ Proprietary GPL/ Proprietary MySQL Oracle SQL Server SQLite AllegroGraph ArangoDB DEX FlockDB GraphBase Hyper GraphDB InfiniteGraph InfoGrid Neo4j License Java Java x86/ Java Java Java

ZeroMQ

by Pieter Hintjens  · 12 Mar 2013  · 1,025pp  · 150,187 words

make software by synthesizing knowledge, much as we make Wikipedia articles. Licensing and Ownership The project SHALL use the GPLv3 or a variant thereof (LGPL, AGPL). I’ve already explained how full remixability creates better scale and why the GPL and its variants seem the optimal contract for remixable software. If

Pragmatic Version Control Using Git

by Travis Swicegood  · 1 Dec 2008  · 184pp  · 12,922 words

Affero General Public License, which is similar to the GPL with one addition. You must release the source code from any service that uses the AGPL. http://gitorious.org B.4 Online Resources A ton of information about Git is available online. This section highlights the main stops for information online

Collaborative Futures

by Mike Linksvayer, Michael Mandiberg and Mushon Zer-Aviv  · 24 Aug 2010  · 188pp  · 9,226 words

technical support for a form of decentralization (remote subscription) and a legal requirement for service providers to release modifications as free so ware via the AGPL. This section barely scratches the surface of the technical and social issues raised by the convergence of so much of our computing, in particular computing