From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Julien Lepiller <julien@lepiller.eu>,
guix-devel@gnu.org, Yasuaki Kudo <yasu@yasuaki.com>
Subject: Re: Add Microsoft Cascadia Code font?
Date: Sun, 10 Jan 2021 14:09:03 +0100 [thread overview]
Message-ID: <00fda975a4dd79fbfc436d69461e5814ceb39426.camel@student.tugraz.at> (raw)
In-Reply-To: <9897CE46-E860-4BB2-BA5D-B262709FF112@lepiller.eu>
Hi Julien,
Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller:
> I might be wrong, but I thought fonts were considered non-functional
> data. If that's the case, isn't cc-by-nc-nd acceptable?
Not according to the FSDG:
> [Non-functional data] can be included in a free system distribution
> as long as its license gives you permission to copy and redistribute,
> both for commercial and non-commercial purposes.
IIUC CC BY-ND would be covered if we indeed consider fonts to be non-
functional data, but not CC BY-NC and certainly not CC BY-NC-ND.
It goes on to list a hypothetical example of a game map, which is
somewhat ironic, considering that games more often disqualify
themselves for the FSDG through the use of entirely non-free assets or
assets rather than being GPL-incompatible through the use of assets,
that don't allow derivative work. Of course, the former is a subset of
the latter, but the point I'm trying to make here, is that the latter
is sadly not even a concern for many (aspiring) game devs out there.
It also reminds me, that I have yet to code up a fully GPL/FSDG-
compatible game myself – I'll get there some day, I promise.
TL;DR: Non-functional data is fine if it is commercially verbatim-
copyable.
Regards,
Leo
next prev parent reply other threads:[~2021-01-10 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 9:16 Add Microsoft Cascadia Code font? Leo Prikler
2021-01-10 9:39 ` Vincent Legoll
2021-01-10 10:11 ` Yasuaki Kudo
2021-01-10 10:38 ` Leo Prikler
2021-01-10 10:56 ` Yasuaki Kudo
2021-01-10 12:28 ` yasu
2021-01-10 12:28 ` Julien Lepiller
2021-01-10 12:55 ` yasu
2021-01-10 13:09 ` Leo Prikler [this message]
2021-01-10 14:28 ` Julien Lepiller
2021-01-10 23:37 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2021-01-10 8:04 yasu
2021-01-10 8:46 ` Vincent Legoll
2021-01-10 8:51 ` Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00fda975a4dd79fbfc436d69461e5814ceb39426.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=yasu@yasuaki.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).