From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Cc: zimoun <zimon.toutoune@gmail.com>
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Thu, 19 Dec 2019 18:18:50 +0100 [thread overview]
Message-ID: <87k16si685.fsf@nckx> (raw)
In-Reply-To: <CAJ3okZ164w_95i=BOimS0u3OgB8bp9CS43r6u_z_X_pCyAXX2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Zimoun,
Thank you for fighting for this package in Guix. I hope upstream
sees the light and Clarifies things.
zimoun 写道:
> Ricardo Wurmus <rekado@elephly.net> wrote:
>> It would be great if they could use the Clarified Artistic
>> License
>> instead. It’s really close to the Artistic 1.0, so unless they
>> really
>> want the non-free interpretation of Artistic 1.0 it should be
>> no trouble
>> for them to switch.
This is the only solution. Any other licence in licenses.scm is
fine too.
> 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.
‘Non-copyleft’ does not mean ‘non-free’. All packages in Guix
must be free. The Artistic 1.0 licence is *not free*.[0]
I do understand your frustration & hacker instinct to ‘fix’ the
problem in some clever way, but that's not how licences work. The
Artistic 1.0 story really ends here.
I'm not trying to demotivate you. I just don't want you to waste
your time & effort in this dead-end direction. Bugging upstream
until they respond is the only solution.
> Well, I have read both licenses and the Clarified one does not
> appear
> me clearer; they are both doomed!
I hope you'll understand that I'm also not trying to be rude when
I say (y)our personal opinions are entirely valid and absolutely
irrelevant :-)
The FSF's legal counsel has decided that the Clarified version
does in fact ‘correct the vagueness of of the Artistic License
1.0’[2].
> Other said, calling Artistic 1.0 non-free in this Bioconductor
> case is
> more a flavour of taste than a real legal issue.
No, it's a very real legal issue. :-(
> Especially when this
> very Artistic 1.0 "qualifies as a free software license, but it
> may
> not be a real copyleft" [1].
…but that's not this very licence, it's a completely different
one: the (disjunct) combination of the Artistic 1.0 licence *and
the GPL*, i.e. ‘choose one’. The result is only free because you
can *ignore* the Artistic 1.0 part.
Kind regards,
T G-R
[0]:
https://www.gnu.org/licenses/license-list.en.html#ArtisticLicense
[1]: https://www.gnu.org/licenses/license-list.en.html#PerlLicense
[2]:
https://www.gnu.org/licenses/license-list.en.html#ClarifiedArtistic
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-12-19 17:19 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
2019-12-19 20:10 ` Ricardo Wurmus
2019-12-19 21:18 ` zimoun
2019-12-19 17:18 ` Tobias Geerinckx-Rice [this message]
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=87k16si685.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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).