mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: License survey
Date: Sun, 19 Feb 2012 11:18:12 -0500	[thread overview]
Message-ID: <20120219161812.GS146@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120219154859.GA16314@openwall.com>

On Sun, Feb 19, 2012 at 07:48:59PM +0400, Solar Designer wrote:
> Oh, and this does start to look like a bikeshed, so I think I won't
> comment further.  I think Rich merely wanted us to vote, which we did. :-)

This is totally a bikeshed, but sometimes the color you paint your
bikeshed matters when you live in a city full of biker gangs and
painting it the right or wrong color will determine who likes you and
who wants to kill you. :-)

And indeed, my main goal was to get a sampling of the opinions on
licensing from the community, and I think I've been successful in
that. Surely a lot more successful than any other time I'd asked for
input/opinions on this list.

A few thoughts I had myself on the matter...

One thing I like about copyleft and having external copyright holders
is that the rules apply to me too. If, for instance, I were working in
embedded systems as a job, and my employer asked me to prepare a
derived work of musl for purely-closed use, I could simply tell them
that's not possible without the consent of other copyright holders.
But with no copyleft, or if I'm the sole copyright holder, the choice
is pretty much to do it or quit (and if I do it, then of course there
becomes a contamination issue if I later try to make similar
improvements to the open version).

Another issue (I suspect Solar will feel differently than me about
this one) is the possibility of offering a non-free, closed version.
If I'm doing a BSD-licensed project and asking others to contribute
under BSD license, it feels like I'm taking their contributions to
build something I could turn around and make closed/commercial
derivatives of for my own benefit. And in a way it would be wrong to
deny myself the right to do this if everybody else who receives the
code has a right to do it, but the original author and/or project
maintainer is in a unique position of authority and trust that makes
it much easier to commercially exploit the code.

For these and of course all the more well-known, conventional reasons,
I tend to favor at least some sort of copyleft, but I also see that a
lot of the community and potential user base is worried about the
ugliness of LGPL with static linking, etc. I don't think there's a
quick and easy answer for what's best to do, but I'll keep everything
in mind as we move along.


Rich


  reply	other threads:[~2012-02-19 16:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19  4:12 Rich Felker
2012-02-19  7:00 ` Isaac Dunham
2012-02-19 14:31   ` gs
2012-02-19  7:27 ` Kurt H Maier
2012-02-19 11:55   ` Hiltjo Posthuma
2012-02-19 12:17 ` Solar Designer
2012-02-19 13:55 ` Christian Neukirchen
2012-02-19 15:48   ` Solar Designer
2012-02-19 16:18     ` Rich Felker [this message]
2012-02-19 17:08       ` Solar Designer
2012-02-19 22:25       ` Kurt H Maier
2012-02-19 22:51         ` Rich Felker
2012-02-20  0:55           ` Kurt H Maier
2012-02-22 17:51       ` Isaac Dunham
2012-02-22 23:20         ` Rich Felker
2012-02-19 14:01 ` Luka Marčetić
2012-02-19 16:03 ` aep
2012-02-19 16:28   ` Solar Designer
2012-02-21 15:42 ` Szabolcs Nagy
2012-02-21 16:59   ` Bobby Bingham
2012-02-21 17:16     ` Rich Felker
2012-02-21 21:22       ` Szabolcs Nagy
2012-02-21 18:31 ` Nathan McSween

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=20120219161812.GS146@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).