From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix@gnu.org
Subject: Re: DISTRHO-Ports license situation
Date: Fri, 25 Jun 2021 15:14:25 +0200 [thread overview]
Message-ID: <20210625151425.5e8fa3252ccdfe01e9c7a5a4@freenet.de> (raw)
In-Reply-To: <20210622211235.8c5668977fc4aebb031a2e1a@freenet.de>
On Tue, 22 Jun 2021 21:12:35 +0200
Thorsten Wilms <t_w_@freenet.de> wrote:
> I created a package for https://github.com/DISTRHO/DISTRHO-Ports.
> I now wonder if I should submit a patch, because the licensing
> situation is a mess, with several of the plugins having no information
> attached at all, though most have at least a pointer to a repo that
> claims a license (gpl2, gpl3, gpl3+, agpl3, MIT).
>
> The original versions of all plugins have been created with JUCE,
> which I though would require GPLing when using the free/personal
> license, but at least currently does so only when exceeding $50k
> revenue (https://juce.com/juce-6-licence).
>
> So parts of this is Free Software, other parts are ... just
> technically open-source. Would you accept this in Guix?
I went ahead and submitted http://debbugs.gnu.org/cgi/bugreport.cgi?bug=49224
prev parent reply other threads:[~2021-06-25 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 19:12 DISTRHO-Ports license situation Thorsten Wilms
2021-06-25 13:14 ` Thorsten Wilms [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=20210625151425.5e8fa3252ccdfe01e9c7a5a4@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@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.
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).