mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: License survey
Date: Sun, 19 Feb 2012 15:01:41 +0100	[thread overview]
Message-ID: <4F4100C5.2010603@gmail.com> (raw)
In-Reply-To: <20120219041242.GR146@brightrain.aerifal.cx>

On 02/19/2012 05:12 AM, Rich Felker wrote:
> What would be your ideal license to see musl under?

Hey Rich,
Ah, you know the implications of (non)copyleft as well as we do. I'd 
show the flaws in reasoning of those who advocate permissive licenses, 
but I'm getting tired of the discussion. Instead of philosophizing about 
how freedom to leech is bad (oops?), I'll just present a list of facts. 
You and I know this, and others do too, but if I try and be objective, 
maybe there's some perspective to be gained on either side. I hope both 
sides can agree that:

  ° Permissiveness has a potential for more contributors and bug reports *
  ° Permissiveness supports development of proprietary products
  ° Copyleft is somewhat harder to apply, harder still to properly 
explain **
  ° Copyleft ensures reciprocity via legal restrictions on derivatives
  ° GPLv3 adds restrictions on patents and tivoization

* Current trend is favoring permissive projects (Webkit, LLVM, 
web-related tech, Apache) over GPL'd ones (GCC, Linux). Apart from the 
hardworking BSD community, this may be caused by companies' FUD 
regarding GPL, or the exact opposite - their understanding of GPL. 
Hopefully, free software can emancipate from proprietary software makers 
in the future.
** Though some free help is available from SFLC, both for explaining and 
enforcing (GPL).

Entering the subjective mode again, just to address the second point. I 
am of opinion that companies, if enabled to produce non-free software 
based on free software, should at least compensate the community for it 
(or else, use another, possibly inferior, solution). In reality, 
however, the adoption by a commercial entity might be what brings you 
money. With that said, anything GPLv3-related is good in my book, but 
it's your decision. Not sure if this helps...

Good luck,
-Luka


  parent reply	other threads:[~2012-02-19 14:01 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
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ć [this message]
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=4F4100C5.2010603@gmail.com \
    --to=paxcoder@gmail.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).