From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Thu, 19 Dec 2019 18:29:08 +0100 [thread overview]
Message-ID: <CAJ3okZ3OqBdnz9T-MFHnoixhyGBfRuSjXgv-vj9g0xgxJSSMJQ@mail.gmail.com> (raw)
In-Reply-To: <87fthgqloc.fsf@elephly.net>
Hi Ricardo,
Thank you for the quick feedback.
On Thu, 19 Dec 2019 at 18:18, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
> > The file guix/licenses.scm contains "non-copyleft" therefore why do
> > not put the licenses Artistic 1.0 under this label? It will allow the
> > inclusion of this package -- and probable others from Bioconductor.
>
> That wouldn’t be correct. non-copyleft is for free licenses only, and
> the Artistic 1.0 does not qualify.
The Perl License section says:
<<
This license is the disjunction of the Artistic License 1.0 and the
GNU GPL—in other words, you can choose either of those two licenses.
It qualifies as a free software license, but it may not be a real
copyleft. It is compatible with the GNU GPL because the GNU GPL is one
of the alternatives.
We recommend you use this license for any Perl 4 or Perl 5 package you
write, to promote coherence and uniformity in Perl programming.
Outside of Perl, we urge you not to use this license; it is better to
use just the GNU GPL.
>>
https://www.gnu.org/licenses/license-list.en.html#PerlLicense
I read "It qualifies as a free software license, but it may not be a
real copyleft." therefore it means non-copyleft.
> https://www.gnu.org/licenses/license-list.en.html#ArtisticLicense says:
>
> “We cannot say that this is a free software license because it is
> too vague; some passages are too clever for their own good, and
> their meaning is not clear. We urge you to avoid using it, except
> as part of the disjunctive license of Perl.”
>
> However:
>
> https://www.gnu.org/licenses/license-list.en.html#ClarifiedArtistic
>
> “This license is a free software license, compatible with the
> GPL. It is the minimal set of changes needed to correct the
> vagueness of the Artistic License 1.0.”
>
I already know these statements. And I disagree. Currently, the
license is considered free when applied to Perl but non-free
otherwise. It does not make sense.
Well, if I understand well, as GNU Guix maintainer, you will have the
official GNU position, right?
So let discuss this official GNU position. :-)
Do you know in which mailing list can I post?
Cheers,
simon
next prev parent reply other threads:[~2019-12-19 17:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 15:02 Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-07-24 21:15 ` Ricardo Wurmus
2019-07-25 9:58 ` zimoun
2019-07-25 12:47 ` Ricardo Wurmus
2019-12-19 16:38 ` zimoun
2019-12-19 17:17 ` Ricardo Wurmus
2019-12-19 17:29 ` zimoun [this message]
2019-12-19 20:10 ` Ricardo Wurmus
2019-12-19 21:18 ` zimoun
2019-12-19 17:18 ` Tobias Geerinckx-Rice
2019-12-19 17:29 ` Tobias Geerinckx-Rice
2019-12-19 18:04 ` zimoun
2019-12-19 17:56 ` zimoun
2019-12-19 20:24 ` Tobias Geerinckx-Rice
2019-12-19 21:40 ` zimoun
2019-12-20 9:28 ` Giovanni Biscuolo
2019-12-20 10:47 ` zimoun
2019-12-20 14:40 ` Ricardo Wurmus
2019-12-20 11:55 ` Guix and Bioconductor Giovanni Biscuolo
2019-12-20 14:38 ` Ricardo Wurmus
2019-12-21 10:06 ` [OT] " Giovanni Biscuolo
2019-12-19 18:18 ` Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-12-20 10:24 ` Perl modules dual licensing (was Re: Bioconductor package flowPeaks license Artistic 1.0?) Giovanni Biscuolo
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=CAJ3okZ3OqBdnz9T-MFHnoixhyGBfRuSjXgv-vj9g0xgxJSSMJQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).