From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Biopython.
Date: Thu, 16 Apr 2015 15:16:36 +0200 [thread overview]
Message-ID: <877ftcw6vf.fsf@gnu.org> (raw)
In-Reply-To: <20150416130209.GA668@jocasta.intra> (John Darrington's message of "Thu, 16 Apr 2015 15:02:09 +0200")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Thu, Apr 16, 2015 at 11:00:30AM +0200, Andreas Enge wrote:
>
> It starts like this:
> "Permission to use, copy, modify, and distribute this software and its
> documentation with or without modifications and for any purpose and
> without fee is hereby granted"
>
> Does the provision "without fee" make it non-free?
>
> I don't think it does.
>
> From a native English speaker's perspective, I think it is free. It
> says "for any purpose". Ipso facto, "any purpose" embraces for the purpose
> of pecuniary gain through charges for distribution.
>
> The important words are: "Permission ... without fee ... is hereby granted."
> In other words, the licensor does not demand a fee before granting that permission.
> If it had said "Permission ... upon payment of fee ... will be granted". Then that
> would have made the thing non-free.
Oooh. IOW “without fee” applies to “Permission”, not to “to use, copy,
modify, and distribute”, right?
That makes sense. I think I was fooled in the past by similar wording.
Does it sound like 100% non-ambiguous to native speakers reading here?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-04-16 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:47 [PATCH] gnu: Add Biopython Ricardo Wurmus
2015-04-15 19:55 ` Ludovic Courtès
2015-04-16 8:46 ` Ricardo Wurmus
2015-04-16 9:00 ` Andreas Enge
2015-04-16 12:36 ` Ludovic Courtès
2015-04-16 13:10 ` Ricardo Wurmus
2015-04-18 16:01 ` Ricardo Wurmus
2015-04-18 17:28 ` Andreas Enge
2015-04-16 13:02 ` John Darrington
2015-04-16 13:16 ` Ludovic Courtès [this message]
2015-04-16 15:40 ` Andreas Enge
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=877ftcw6vf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).