From: Aaron Wolf <wolftune@riseup.net>
To: Mike Gerwitz <mtg@gnu.org>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Adding [A]GPLv3+ code to Quake-based code base
Date: Wed, 30 Aug 2017 21:48:03 -0700 [thread overview]
Message-ID: <4d46ee30-edda-8c55-bc11-1a7bfbfe9d9a@riseup.net> (raw)
In-Reply-To: <87wp5k8ptx.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
On 08/30/2017 06:54 PM, Mike Gerwitz wrote:
> On Wed, Aug 30, 2017 at 09:19:13 -0700, Aaron Wolf wrote:
>>> So if someone downloads such combined work and start a server, do they
>>> have to publish the complete source code? What if they modify it?
>>>
>>
>> Yes, the AGPL terms apply to the whole work, *all* the code *as running
>> on the server* (i.e. including any modifications) must be published to
>> those who have access to the server.
>
> But only if modifications are made.
>
What do you mean "only if modifications are made"?
Can you cite the part of the license you read that way?
I certainly had the impression that, just like the GPL, the AGPL
required making the source available whenever conveying, regardless of
modified status.
It is *not* okay under AGPL to have a situation like this (at least as I
believe at this time and want to be true):
1. I publish code under AGPL
2. You get my code
3. My website that publishes the source disappears
4. You publish the software via giving people access over a server, make
no modifications, and refuse to share the source.
Under the GPL or AGPL, anyone doing the conveying is responsible for
providing the source code. That responsibility doesn't come into play
only if you modify the code.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 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 4:48 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 [this message]
2017-08-31 5:10 ` Mike Gerwitz
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=4d46ee30-edda-8c55-bc11-1a7bfbfe9d9a@riseup.net \
--to=wolftune@riseup.net \
--cc=libreplanet-discuss@libreplanet.org \
--cc=mtg@gnu.org \
/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).