From: Marius Bakke <marius@gnu.org>
To: Brett Gilio <brettg@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Did nmap just become non-free?
Date: Thu, 15 Oct 2020 00:12:45 +0200 [thread overview]
Message-ID: <87r1q0pici.fsf@gnu.org> (raw)
In-Reply-To: <87mu0phd5n.fsf@debian>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Brett Gilio <brettg@gnu.org> writes:
> Marius Bakke <marius@gnu.org> writes:
>>
>> ...I'm fairly certain this is not an acceptable license for Guix, or
>> free software distributions in general.
>>
>
> This is definitely not a consistent license for us.
Having re-read the original text (without the annotations), the thing
that stands out is:
Proprietary software companies wishing to use or incorporate Covered
Software within their programs must contact Licensor to purchase a
separate license. Open source developers who wish to incorporate parts
of Covered Software into free software with conflicting licenses may
write Licensor to request a waiver of terms.
From <https://svn.nmap.org/nmap/LICENSE>.
So a "proprietary software company" cannot use or incorporate nmap
within a program, even if that program is free (as in software)?
>> So I think we should revert the license change, as well as the update
>> to 7.90 which introduced the new license.
>>
>> Now to read the previous license text, perhaps that will help me sleep..
>>
>
>
> As to how to fix it, I think we will need to revert the change, and also
> make note of the FINAL version of nmap that was still compliant with FSDG.
I'll see what licensing@fsf.org has to say first.
PS: Licenses make terrible bed-side reading!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2020-10-14 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 0:00 Did nmap just become non-free? Marius Bakke
2020-10-14 0:19 ` Brett Gilio
2020-10-14 22:12 ` Marius Bakke [this message]
2020-10-14 22:52 ` Brett Gilio
2020-10-15 0:13 ` zimoun
2020-10-15 16:02 ` Brett Gilio
2020-10-15 8:51 ` 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=87r1q0pici.fsf@gnu.org \
--to=marius@gnu.org \
--cc=brettg@gnu.org \
--cc=guix-devel@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).