mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: license survey results
Date: Mon, 27 Feb 2012 20:55:57 -0500	[thread overview]
Message-ID: <20120228015557.GJ184@brightrain.aerifal.cx> (raw)

Here's what I compiled as the "results" of the license survey. I've
broken it down into very minimal classifications of the opinions
everybody expressed, so please let me know if you think I
misunderstood or misrepresented your ideas (or if I missed you).

non-copyleft (MIT/BSD/etc.) crowd:
chneukirchen
solar
nathan mcsween
hiltjo
khm
[rob landley] (in absentia ;-)

LGPL [non-]crowd:
luka

LGPL w/static-linking exceptions [almost-]crowd:
isaac dunham
gs

LGPL w/commercial licenses [non-]crowd:
aep

only-care-that-the-code-rocks crowd:
nsz

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. My idea right now (subject to change at my own whim
or suggestions from the community) is that the license might change at
the 0.9 or 1.0 milestone, especially if it looks like we could be
positioned to push musl into widespread usage "in the wild" at that
point.

Thanks for everyone who participated in the survey!

Rich


             reply	other threads:[~2012-02-28  1:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28  1:55 Rich Felker [this message]
2012-02-29 16:01 ` Luka Marčetić
2012-03-01  2:31 ` Isaac Dunham
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=20120228015557.GJ184@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).