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: Tue, 21 Feb 2012 12:16:14 -0500	[thread overview]
Message-ID: <20120221171614.GA184@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAFNaaxSPA0vNj3+R+ykeK96dwYzvGNsJ1go3Qn3WdqJQ4UUjag@mail.gmail.com>

On Tue, Feb 21, 2012 at 10:59:17AM -0600, Bobby Bingham wrote:
> On Tue, Feb 21, 2012 at 9:42 AM, Szabolcs Nagy <nsz@port70.net> wrote:
> > [...]
> > 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)
> >
> 
> This sounds like a contradictory position to me.
> 
> The whole point of a license is as a place for you to spell out your
> requirements for others to use/redistribute the software.  If you want
> them to share their improvements, that's exactly the sort of thing
> that belongs in the license.

Indeed, especially with corporate users. If you treat sharing
improvments as The Right Thing to do, but don't spell out a
requirement to do so, then people improving the source in a corporate
environment have their hands tied. They may want to share their
improvements, but without a legal requirement to do so, they're going
to have a really hard time convincing their boss and/or legal
department that it's a good idea. Ideally "It will save us having to
maintain our own tree internally and resolve conflicts merging
upstream changes." would be a good enough reason, but I think that's
wishful thinking...

> It sounds odd to me to use a license allowing others to keep their
> improvements closed, and then to shame them for actually following the
> license.

I'm uncertain whether I agree with this or not. All free software and
open source definitions seem to exclude any license that puts
restrictions on use based on field of endeavor (e.g. using the
software in controversial settings the copyright holder disagrees
with), but I would still feel perfectly comfortable shaming somebody
who used free software to censor the internet or track down dissidents
for imprisonment and torture.

In short, I think there's some merit to saying: I acknowledge that
it's not my right or responsibility to impose condition X on use of
code, because if we as a community tolerated that, everyone would come
up with their own pet conditions and combining code from different
projects would become impossible. But you're still a bad
person/company if you do [thing condition X would have prohibited].

Rich


  reply	other threads:[~2012-02-21 17:16 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
2012-02-21 16:59   ` Bobby Bingham
2012-02-21 17:16     ` Rich Felker [this message]
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=20120221171614.GA184@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).