From: zimoun <zimon.toutoune@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Kei <kkebreau@posteo.net>, Pierre Neidhardt <mail@ambrevar.xyz>,
41967@debbugs.gnu.org
Subject: [bug#41967] [PATCH] gnu: Add tesseract.
Date: Mon, 29 Jun 2020 20:23:02 +0200 [thread overview]
Message-ID: <CAJ3okZ1xgYz5Qyx8V5jy1rhLSMZL6wJFaWN3ud9QetR=KpMRYw@mail.gmail.com> (raw)
In-Reply-To: <20200629061213.GB14409@E5400>
On Mon, 29 Jun 2020 at 08:13, Efraim Flashner <efraim@flashner.co.il> wrote:
> > > * media/sound/game/soundsnap/info.txt: Non-commercial clause (
> > > https://www.soundsnap.com/licence)
> >
> > Are "non commercial" licenses still free licenses?
>
> I'm pretty sure no, even for non-code. But I'd love to hear from someone
> else who's more sure than I am.
"non-commercial" and "free license" are not related.
Well, it is hard to predict what the FSF would conclude for a such
license. Because the terms are not really clear. On one hand, you
can "transit the sounds as long as they are included with other
materials" and on the other hand you cannot "transmit the sounds 'as
they are' in any context".
b. To copy and transmit the sounds and available content in various
mediums or formats as long as the sounds and available content are
included in another work or with other materials;
i. Resell, rent, sublicense, transmit, and/or distribute or
re-distribute the sounds 'as they are' in any context,
prev parent reply other threads:[~2020-06-29 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 18:07 [bug#41967] [PATCH] gnu: Add tesseract Pierre Neidhardt
2020-06-26 23:04 ` Kei
2020-06-27 6:57 ` Pierre Neidhardt
2020-06-28 15:26 ` Kei
2020-06-28 20:04 ` Pierre Neidhardt
2020-06-29 6:12 ` Efraim Flashner
2020-06-29 17:41 ` Msavoritias
2020-06-29 18:23 ` Pierre Neidhardt
2020-06-29 19:19 ` Nicolas Goaziou
2020-06-30 14:38 ` Pierre Neidhardt
2020-06-29 18:23 ` zimoun [this message]
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='CAJ3okZ1xgYz5Qyx8V5jy1rhLSMZL6wJFaWN3ud9QetR=KpMRYw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=41967@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=kkebreau@posteo.net \
--cc=mail@ambrevar.xyz \
/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).