From: Kei Kebreau <kei@openmailbox.org>
To: 26300@debbugs.gnu.org
Subject: bug#26300: [PATCH] gnu: milkytracker: Update to 1.0.0.
Date: Wed, 29 Mar 2017 12:23:12 -0400 [thread overview]
Message-ID: <87y3vonjbj.fsf@openmailbox.org> (raw)
In-Reply-To: <20170329160821.3hdsx2pdevub6wtg@abyayala> (ng0's message of "Wed, 29 Mar 2017 16:08:21 +0000")
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
ng0 <contact.ng0@cryptolab.net> writes:
> Kei Kebreau transcribed 1.3K bytes:
>> ng0 <contact.ng0@cryptolab.net> writes:
>>
>> >
>> > Attribution-Noncommericial… doesn't that make them a candidate for
>> > exclusion in systems like Guix?
>> >
>>
>> Considering that the songs are data files and non-executable, the
>> software is still free. If the sample songs turn out to be a problem, I
>> can attempt to remove them in a snippet.
>
> It would help if we could document this. I don't think everyone will review
> upstream material (FSDG and similar) for data files (music, images).
> I would exclude CC licensed material which says "Noncommercial", but I'm
> not a lawyer.
It may also cause problems upstream as well. The software is under licenses
with no commerical restrictions and the sample songs are under a
noncommericial restriction, but they are shared in one tarball. That
would constitute a conflict, right?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-03-29 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 14:52 bug#26300: [PATCH] gnu: milkytracker: Update to 1.0.0 Kei Kebreau
2017-03-29 15:04 ` ng0
2017-03-29 16:01 ` Kei Kebreau
2017-03-29 16:08 ` ng0
2017-03-29 16:23 ` Kei Kebreau [this message]
2017-03-30 13:37 ` Ricardo Wurmus
2017-03-30 14:20 ` Kei Kebreau
2017-03-30 14:20 ` Kei Kebreau
2017-03-30 14:58 ` Ricardo Wurmus
2017-03-30 16:02 ` Kei Kebreau
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=87y3vonjbj.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=26300@debbugs.gnu.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.
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).