mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: License survey
Date: Tue, 21 Feb 2012 16:42:54 +0100	[thread overview]
Message-ID: <20120221154253.GV31975@port70.net> (raw)
In-Reply-To: <20120219041242.GR146@brightrain.aerifal.cx>

* Rich Felker <dalias@aerifal.cx> [2012-02-18 23:12:42 -0500]:
> Which is more important, copyleft or widespread usage of musl?

i think the goal should be quality software that can be
audited, modified, maintained, studied and is useful

copyleft is not a goal, widespread usage should be a
side effect

> Which copyleft issue(s) matter most: ensuring the project gets access
> to third-party improvements, protecting users' rights to study and
> reverse engineer, or protecting users' rights to access the code and
> make source-level modifications?
> 
> Is it important to have a license where the official distribution is
> not privileged over third-party redistributions?
> 

i'd encourage sharing third party improvements
(and try to make it easy)
but would not try to enforce it
(except may be by publishing evildoers on a wall of shame)

i'd try to provide source code access, allow modifications etc
and signal that it will remain this way in the future

i'd allow binary or source code redistribution
with the only restriction that the origin of the information
must not be misrepresented and should be provided when asked
(but this should be dealt with by some general law against
fraud and not in individual licenses)

> Is the LGPL's handling of static linking problematic to you?

it haven't caused me problems yet, but i don't think it's practical

> What would be your ideal license to see musl under?

i don't mind lgpl and i don't mind non-copyleft licensing either

i support penalizing those who treat software as
private consumable instead of public good
i support punishing any evil non-cooperative
behaviour
but i'm not sure if licensing is the right place
to fight these
(it's more of a user education issue,
licensing is based on bogus ideology itself)

oh and i definitely don't want to litter precious
source code with legal nonsense (copyright notices)


  parent reply	other threads:[~2012-02-21 15:42 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ć
2012-02-19 16:03 ` aep
2012-02-19 16:28   ` Solar Designer
2012-02-21 15:42 ` Szabolcs Nagy [this message]
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=20120221154253.GV31975@port70.net \
    --to=nsz@port70.net \
    --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).