From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: brobecker@adacore.com, gdb@sourceware.org
Subject: Re: SVG version of GDB mascot (archer fish)
Date: Wed, 04 Oct 2017 14:08:00 -0000 [thread overview]
Message-ID: <918df632-2881-8d8b-68a9-a30a227ebc3b@redhat.com> (raw)
In-Reply-To: <83efqp8ztc.fsf@gnu.org>
On 09/29/2017 01:16 PM, Eli Zaretskii wrote:
>> From: Andreas Arnez <arnez@linux.vnet.ibm.com>
>> Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
>> Date: Tue, 26 Sep 2017 13:35:57 +0200
>>
>> Since the SVG is strongly based on the original drawing,
>> it seems to me that we can not choose the license independently. The
>> original fish is licensed as "CC BY-SA 3.0 US":
>>
>> http://www.bluebutton.com/misc/archer.comment
>>
>> So I assume that the SVG version has to be licensed in the same way. In
>> my patch I'll update the "mascot" page with the licensing information
>> and a link to the license
>> (https://creativecommons.org/licenses/by-sa/3.0/us/).
>
> FWIW, https://www.gnu.org/licenses/license-list.en.html#OtherLicenses
> only mentions CC BY-SA 4.0, so I think we should first find out
> whether version 3.0 is GPL-compatible.
>
Note that:
- we've been using the original image with CC BY-SA 3 for
many years, so that would not be a new problem.
- the website is not GPL, AFAIK. All pages end with:
"Verbatim copying and distribution of this entire article is permitted
in any medium, provided this notice is preserved."
But in any case, I agree that it's good to upgrade the license to
avoid questions if we ever want to combine it with GPLv3 sources.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-10-04 14:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 17:04 Andreas Arnez
2017-09-25 22:28 ` Joel Brobecker
2017-09-25 23:12 ` Pedro Alves
2017-09-26 11:36 ` Andreas Arnez
2017-09-26 11:46 ` Pedro Alves
2017-09-26 12:06 ` Andreas Arnez
2017-09-26 13:16 ` Pedro Alves
2017-09-29 12:41 ` Eli Zaretskii
2017-09-29 17:19 ` Andreas Arnez
2017-09-29 18:13 ` Eli Zaretskii
2017-10-04 13:30 ` Andreas Arnez
2017-10-04 14:08 ` Pedro Alves [this message]
2017-10-04 14:45 ` Eli Zaretskii
2017-10-04 14:48 ` Pedro Alves
2017-10-04 16:56 ` Eli Zaretskii
2017-10-06 9:17 ` Andreas Arnez
2017-09-26 11:40 ` Andreas Arnez
2017-09-26 12:40 ` Joel Brobecker
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=918df632-2881-8d8b-68a9-a30a227ebc3b@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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