From 991ec3c4e49de1c7a10183c763dee05c0c4e9515 Mon Sep 17 00:00:00 2001 From: Axel Huebl Date: Mon, 16 Jun 2014 13:08:04 +0200 Subject: [PATCH] AGPL: Highlight the Affero Feature This is a follow up to #197 A new point in the "required" section of the AGPL highlights the difference to the plain GPL. It states that running a network service of the software triggers the disclose-source requirement, e.g. in SaaS use cases. This is my personal interpretation of the paragraph 13 AGPL, IANAL. Comments are welcome! --- _config.yml | 3 +++ licenses/agpl-v3.txt | 1 + 2 files changed, 4 insertions(+) diff --git a/_config.yml b/_config.yml index beb77ed..5e45d98 100644 --- a/_config.yml +++ b/_config.yml @@ -16,6 +16,9 @@ rules: - description: Source code must be made available when distributing the software. In the case of LGPL, the source for the library (and not the entire program) must be made available. label: Disclose Source tag: disclose-source + - description: Users who interact with the software via network are given the right to receive a copy of the corresponding source code. + label: SaaS is Distribution + tag: saas-disclose - description: The library may be used within a non-open-source application. label: Library usage tag: library-usage diff --git a/licenses/agpl-v3.txt b/licenses/agpl-v3.txt index c5db592..0006fb2 100644 --- a/licenses/agpl-v3.txt +++ b/licenses/agpl-v3.txt @@ -16,6 +16,7 @@ required: - include-copyright - document-changes - disclose-source + - saas-disclose permitted: - commercial-use