From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-nfp@lists.gentoo.org
Subject: Re: [gentoo-nfp] Reconsider the license of the "g" logo (item for Trustees meeting)
Date: Tue, 22 Nov 2016 00:45:06 +0100 [thread overview]
Message-ID: <22579.34562.473649.127409@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <robbat2-20161120T203214-705878341Z@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 2544 bytes --]
>>>>> On Sun, 20 Nov 2016, Robin H Johnson wrote:
> TL;DR:
> 1. Move artwork to CC-BY v4
> 2. update name/logo page to say 'trademark licensing'
From reading the long version I guess that in 1. above you mean
CC-BY-SA (not CC-BY)?
> [...]
> So where do we go?
> 0. Educate users that they are taking two licenses (copyright & trademark)
> 1. Change copyright license on all Gentoo-owned to BY-SA (v4, further below)
> 2. EXPLICITLY grant trademark licenses (most of this is done in the
> name/logo page already):
> 2.1. Non-commercial works: no Foundation permission needed.
> 2.2. Non-transformative Commercial works with Foundation permission only.
> 2.3. Highly-Transformative commercial works UNCERTAIN (I'm not decided).
> 3. Note that the artwork remains available under prior versions of the
> license as well [6]
> 4. Note that the name/logo guidelines page is the trademark usage licensing.
I agree with all of these points.
About 2.3, I don't see why this needs to be distinguished from 2.2.
Who decides what is highly-transformative? (So anyone distributing
such works might be well-advised to ask the Foundation in any case.)
> Why CC v4?
> - v4 requires all modifications be noted [1]
> - v4 BY-SA (but not BY-NC-SA) is GPLv3 compatible [3]
> - v4 auto-reinstatement on violations [4]
> - v4 trademark explicitly-not-licensed [5]
> - v3+v4 "no endorsement clause" to block advertising [2]
The only reason I had suggested CC-BY-SA version 2.5 or 3.0 was
compatibility to the bulk of existing documentation which tends to be
under CC-BY-SA-3.0 (e.g. the wiki).
This is not really a problem though, because CC licenses have a
built-in upgrade clause allowing distribution of derived works under
any later version of the same license. So a work combining a v3 text
and a v4 logo can always be distributed under v4.
Ulrich
> [1] https://wiki.creativecommons.org/wiki/License_Versions#Modifications_and_adaptations_must_be_indicated
> [2] https://wiki.creativecommons.org/wiki/License_Versions#.22No_endorsement.22_clause_included
> [3] https://creativecommons.org/share-your-work/licensing-considerations/compatible-licenses/
> [4] https://wiki.creativecommons.org/wiki/License_Versions#Automatic_restoration_of_rights_after_termination_if_license_violations_corrected
> [5] https://wiki.creativecommons.org/wiki/License_Versions#Trademark_and_patent_explicitly_not_licensed
> [6] https://creativecommons.org/faq/#what-if-i-change-my-mind-about-using-a-cc-license
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2016-11-21 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 14:20 [gentoo-nfp] Reconsider the license of the "g" logo (item for Trustees meeting) Ulrich Mueller
2016-11-07 17:28 ` David Abbott
2016-11-20 22:09 ` Robin H. Johnson
2016-11-21 23:45 ` Ulrich Mueller [this message]
2016-11-23 23:56 ` Matthew Thode
2016-11-24 0:13 ` Ulrich Mueller
2016-11-24 1:03 ` Alice Ferrazzi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22579.34562.473649.127409@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-nfp@lists.gentoo.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