From: Mike Gerwitz <mtg@gnu.org>
To: Aaron Wolf <wolftune@riseup.net>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Adding [A]GPLv3+ code to Quake-based code base
Date: Thu, 31 Aug 2017 01:10:25 -0400 [thread overview]
Message-ID: <87shg87266.fsf@gnu.org> (raw)
In-Reply-To: <4d46ee30-edda-8c55-bc11-1a7bfbfe9d9a@riseup.net> (Aaron Wolf's message of "Wed, 30 Aug 2017 21:48:03 -0700")
[-- Attachment #1.1: Type: text/plain, Size: 1969 bytes --]
On Wed, Aug 30, 2017 at 21:48:03 -0700, Aaron Wolf wrote:
> What do you mean "only if modifications are made"?
> Can you cite the part of the license you read that way?
https://www.gnu.org/licenses/why-affero-gpl.html
"It has one added requirement: if you run a __modified__ program on a
server and let other users communicate with it there, your server must
also allow them to download the source code corresponding to the
modified version running there." (emphasis mine)
That page did not include "modified" some time ago (>1y); I brought it
to rms' attention out of confusion, and he corrected it.
As far as the actual license goes:
https://www.gnu.org/licenses/agpl.html
"The GNU Affero General Public License is designed specifically to
ensure that, in such cases, the modified source code becomes available
to the community. It requires the operator of a network server to
provide the source code of the modified version running there to the
users of that server. Therefore, public use of a modified version, on
a publicly accessible server, gives the public access to the source
code of the modified version."
Section 13:
"Notwithstanding any other provision of this License, if you modify
the Program, your modified version must prominently offer all users
interacting with it remotely through a computer network (if your
version supports such interaction) an opportunity to receive the
Corresponding Source of your version by providing access to the
Corresponding Source from a network server at no charge [...]"
> I certainly had the impression that, just like the GPL, the AGPL
> required making the source available whenever conveying, regardless of
> modified status.
I had that impression too, a while back.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-31 5:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 9:53 Adding [A]GPLv3+ code to Quake-based code base Lyberta
2017-08-29 16:12 ` Aaron Wolf
2017-08-29 21:58 ` Lyberta
2017-08-29 22:18 ` Isaac David
2017-08-29 23:06 ` Aaron Wolf
2017-08-29 23:30 ` Isaac David
2017-08-29 23:43 ` Aaron Wolf
2017-08-30 0:51 ` Isaac David
2017-08-30 1:43 ` Aaron Wolf
2017-08-30 3:07 ` Isaac David
2017-08-30 3:19 ` Isaac David
2017-08-30 9:15 ` Lyberta
2017-08-30 16:19 ` Aaron Wolf
2017-08-31 1:54 ` Mike Gerwitz
2017-08-31 4:48 ` Aaron Wolf
2017-08-31 5:10 ` Mike Gerwitz [this message]
2017-08-31 5:23 ` Aaron Wolf
2017-08-31 19:43 ` John Sullivan
2017-08-31 19:49 ` Aaron Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shg87266.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=wolftune@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).