From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: SVG version of GDB mascot (archer fish)
Date: Tue, 26 Sep 2017 11:46:00 -0000 [thread overview]
Message-ID: <a3f06235-7a05-02b3-3fc3-8676d3d13db6@redhat.com> (raw)
In-Reply-To: <m3r2uty9nm.fsf@oc1027705133.ibm.com>
> On Tue, Sep 26 2017, Pedro Alves wrote:
>
>> On 09/25/2017 11:28 PM, Joel Brobecker wrote:
>
>> Is this an Inkspace SVG? If so, I believe that it's a good
>> idea to export it as an Optimized SVG for the web.
>>
>> If already optimized / stripped of custom extensions, it
>> may be desirable to also provide access to the original file
>> for future editing and adaptation, if Andreas is willing.
>
> It's already optimized. Yes, I can provide the Inkscape version as
> well. I'll add it to the patch.
Thanks so much.
>
>> Do we need to say something about copyright/license?
>
> 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
Interesting. How did you find this, OOC? I couldn't
find a link in the page. I wasn't around when the drawing was
created, and I wonder whether there's something in the
mailing list archives that we could link to.
>
> 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/).
Makes sense to me.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-26 11:46 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 [this message]
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
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=a3f06235-7a05-02b3-3fc3-8676d3d13db6@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--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