-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New exception request: AGPL-3.0-only with trademark exception #2011
Comments
I didn't look at this too closely but I'm not sure this should be seen as an "exception" in the SPDX sense. It claims to be a section 7 additional term but this seems to refer to the language authorizing use of additional terms "[d]eclining to grant rights under trademark law for use of some trade names, trademarks, or service marks" which does not concern additional permissions (which is how SPDX understands exceptions for purposes of the exception list). However, the language in the LICENSE file basically just says "the licensing of the Program under the AGPL does not imply a trademark license" and references a separate trademark policy which grants certain permissions to use the "Z-PUSH" mark. Also, to be clear, this package is not in Fedora and therefore I don't think the "major distro" qualifier should apply here (EDIT: as a result of a connection to Fedora) unless SPDX wants to treat RPMFusion itself as a major distro. One further point: The AGPL additional terms I remember from Zarafa when it was packaged in Fedora were different from what's here. Those were basically badgeware terms, were the result of a negotiation between Red Hat and Zarafa lawyers, and I think today Fedora would probably not allow such terms. |
I'm not sure what qualifies as "major distro", but as of writing Z-Push is shipped with Debian (main) and Ubuntu (universe), too. |
Ah, I would think if it's in Debian main it should qualify as "major distro", yes, but that's up to the SPDX legal team. I was mainly concerned that someone unfamiliar with RPMFusion might assume this package is in Fedora. |
Debian qualifies for "used in major distro" for ease of reference, will paste text in comments |
from https://github.com/Z-Hub/Z-Push/blob/develop/LICENSE#L666 - key text in italics, as rest is standard AGPL-3.0 header Copyright 2007 - 2016 Zarafa Deutschland GmbH This program is free software: you can redistribute it and/or modify According to sec. 7 of the GNU Affero General Public License, version 3, "Zarafa" is a registered trademark of Zarafa B.V. Our trademark policy (see TRADEMARKS) allows you to use our trademarks This program is distributed in the hope that it will be useful, You should have received a copy of the GNU Affero General Public License |
@richardfontana FWIW This (or something similar) was on our "more research needed" list for Fedora license data. There was a listing for "Affero General Public License 3.0 with Zarafa trademark exceptions" and the Fedora shortname, "AGPLv3 with exceptions (as @robert-scheck already noted) on the old wiki "good list". It had a link that's now dead at http://www.zarafa.com/content/affero-gplv3 - since I couldn't find the actual text of the exception, it didn't get matched and added to the new Fedora-license-list data. As for whether this should be an exception on the SPDX License List, I know there was lengthy discussions on how to deal with a potential onslaught of additional clauses under GPL-3.0, section 7. That would apply to AGPL-3.0 as well. I'd have to dig into the email archive to remember any outcomes (other than there not being an onslaught) and it may very well have even pre-dated 2.0 when we added a separate exception list... |
@jlovejoy additional clauses under GPLv3 section 7 (in the sense I'm pretty sure you mean) are conceptually not "exceptions" in the SPDX exception list sense - they are not additional permissions. Additional permissions (corresponding to traditional GPLv2 "exceptions") are covered in a different part of GPLv3 section 7. I know this case shows how odd this is because in a sense it seems like this is mostly a grant of trademark permission. The relevant part of GPLv3 section 7 was meant to legitimize simple clauses like "This license does not grant you any rights to use licensor's trademarks". |
In my opinion this is an appropriate case for 'AdditionRef-' and is not appropriate for addition to the SPDX exception list under the current criteria. |
I tend to agree with @richardfontana on this. This seems closer to general "additional terms" that would be referenced using a custom "AdditionRef-" identifier as discussed here. I don't think this would meet the exception requirements for the SPDX Exceptions List, since to the extent it's granting additional rights, they appear to be trademark rights as dictated by Zarafa's corporate trademark policy. I think that's specific to Zarafa and is outside the scope of what would be counted as an "exception" for Exception List purposes. |
sounds good, I'll close then @robert-scheck - I'm not sure Fedora has documented the use of |
Introduction
The Z-Push RPM package in RPM Fusion (a third-party add-on repository for Fedora and RHEL) uses the license shortname "AGPLv3 with exceptions" from the old Fedora license shortname system – and a proper exception name is needed for updating to the SPDX system. The exception is that a trademark policy is added by using section 7 of AGPL-3.0-only (see the end of the license file itself).
Note that more or less the same exception exists for the Zarafa Collaboration Platform (abandonware, see source code copy at Fedora for EPEL) as well, but referring to the trademark "Zarafa" instead of "Z-Push". It might make sense to catch both with the same exception, e.g. "Zarafa trademark exception" or similar?
License Name
?
Suggested short identifier
No response
URL to license text
https://github.com/Z-Hub/Z-Push/blob/develop/LICENSE#L666 + https://github.com/Z-Hub/Z-Push/blob/develop/TRADEMARKS
OSI Status
I don't know
License author or steward
Zarafa Deutschland GmbH
URL to project(s) that use license
AGPL-3
andTRADEMARKS.txt
The text was updated successfully, but these errors were encountered: