From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: license survey results
Date: Wed, 29 Feb 2012 18:31:21 -0800 [thread overview]
Message-ID: <20120229183121.069de4ab.idunham@lavabit.com> (raw)
In-Reply-To: <20120228015557.GJ184@brightrain.aerifal.cx>
On Mon, 27 Feb 2012 20:55:57 -0500
Rich Felker <dalias@aerifal.cx> wrote:
<snip>
> non-copyleft (MIT/BSD/etc.) crowd:
> chneukirchen
> solar
> nathan mcsween
> hiltjo
> khm
> [rob landley] (in absentia ;-)
..
> LGPL w/static-linking exceptions [almost-]crowd:
> isaac dunham
> gs
>
I was thinking "LGPL is semi-bearable, non-copyleft is better, and
static link exceptions are a good-enough compromise for now; I don't
have any code that gives me a reason to expect you to change to non-
copyleft."
So if you want, you can put me under non-copyleft...which is ~7 vs 1
for each of four options.
<snip>
> In summary, it looks like everyone except Luka (and perhaps aep) who
> responded would like to see at least *some* additional level of
> permissiveness to musl's license terms, and the largest single group
> is in favor of non-copyleft/"permissive" terms. As such I'll
> definitely be making some licensing changes down the line. Please give
> me some time to weigh the benefits of the different options and focus
> on the code, especially at this time while widespread deployment is
> still a ways off.
For the record, I'd prefer a license like MIT/BSD to Apache 2.0 & co.
(where there's a patent clause)--patent clauses just don't sit so well
with me. Not sure that it legally makes sense though!
--
Isaac Dunham <idunham@lavabit.com>
next prev parent reply other threads:[~2012-03-01 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 1:55 Rich Felker
2012-02-29 16:01 ` Luka Marčetić
2012-03-01 2:31 ` Isaac Dunham [this message]
2012-03-01 2:39 ` Rich Felker
2012-03-06 16:55 ` aep
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=20120229183121.069de4ab.idunham@lavabit.com \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).