From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/3] licenses: Add beerware license.
Date: Wed, 30 Mar 2016 10:01:08 -0700 [thread overview]
Message-ID: <87lh4zgati.fsf@dustycloud.org> (raw)
In-Reply-To: <87egaubc3h.fsf@gmail.com>
Alex Vong writes:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Mon, Mar 28, 2016 at 09:00:38AM -0700, Christopher Allan Webber wrote:
>>> Leo Famulari writes:
>>>
>>> > On Sun, Mar 27, 2016 at 02:02:11PM -0700, Christopher Allan Webber wrote:
>>> >> Efraim Flashner writes:
>>> >>
>>> >> > On Sat, 26 Mar 2016 18:50:53 -0700
>>> >> > Christopher Allan Webber <cwebber@dustycloud.org> wrote:
>>> >> >
>>> >> >> Leo Famulari writes:
>>> >> >>
>>> >> >> [...]
>>> >> >>
>>> >> >> Now there's a license name bound to cause some confusion!
>>> >> >>
>>> >> >> It looks free... I think it would be okay to push. But maybe if only
>>> >> >> one or two packages use it it would be better to just use the
>>> >> >> non-copyleft license option?
>>> >> >>
>>> >> >
>>> >> > I went and doublechecked the license, because I've heard in the past it's not
>>> >> > actually a copyleft license. According to wikipedia[0], it is not copyleft,
>>> >> > but is GPL compatable, and recognized by the FSF. The language of the license
>>> >> > does allow for not buying the author a beer.
>>> >> >
>>> >> >
>>> >> > [0] https://en.wikipedia.org/wiki/Beerware
>>> >>
>>> >> It's not a copyleft license, right. That's why I suggested non-copyleft
>>> >> :)
>>> >>
>>> >> For example, in unzip:
>>> >>
>>> >> (license (license:non-copyleft "file://LICENSE"
>>> >> "See LICENSE in the distribution."))
>>> >
>>> > I'll do whatever the consensus says.
>>>
>>> Okay, and again, I don't have strong opinions, just a suggestion.
>>>
>>> > But what about the IBM license on the base64 component of signify? What
>>> > should I do about that?
>>>
>>> I don't know, could you point to what the code is and the license?
>>
>> The issue is described in the cover letter:
>>
>> http://lists.gnu.org/archive/html/guix-devel/2016-03/msg01097.html
> For your reference, Debian maintainer calls this "IBM license". [0] I
> would call it a non-copyleft license with patent grant.
>
> [0]: http://metadata.ftp-master.debian.org/changelogs/main/s/signify-openbsd/signify-openbsd_13-1_copyright
I think the question is if it's used by anything other than this
particular software, to answer whether (non-copyleft) should be used or
to make a new license entry. If you know of it being used somewhere
else, I'd put it as its own license entry, otherwise just use
(non-copyleft) I think.
I'm guessing it's probably not used anywhere else, since the patent
grant is pretty specific to the domain of DNS?
Thanks Leo!
- Chris
next prev parent reply other threads:[~2016-03-30 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 23:18 [PATCH 0/3] Adding libbsd and signify Leo Famulari
2016-03-26 23:18 ` [PATCH 1/3] licenses: Add beerware license Leo Famulari
2016-03-27 1:50 ` Christopher Allan Webber
2016-03-27 7:08 ` Efraim Flashner
2016-03-27 21:02 ` Christopher Allan Webber
2016-03-27 21:31 ` Leo Famulari
2016-03-28 16:00 ` Christopher Allan Webber
2016-03-28 16:18 ` Leo Famulari
2016-03-28 20:07 ` Alex Vong
2016-03-30 17:01 ` Christopher Allan Webber [this message]
2016-04-01 9:54 ` Ludovic Courtès
2016-03-26 23:18 ` [PATCH 2/3] gnu: Add libbsd Leo Famulari
2016-04-07 21:19 ` Ludovic Courtès
2016-04-12 0:10 ` Leo Famulari
2016-03-26 23:19 ` [PATCH 3/3] gnu: Add signify Leo Famulari
2016-04-07 21:23 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lh4zgati.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=alexvong1995@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.