9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: EBo <ebo@sandien.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] license situation and OSI
Date: Wed, 26 May 2010 03:55:26 -0600	[thread overview]
Message-ID: <c06f7c7b65312b73c2fd4e334c8c1290@swcp.com> (raw)
In-Reply-To: <80a3558f-c291-4770-9945-57c3a3fbd15f@c22g2000vbb.googlegroups.com>


> I just ran into a number of discussions on the Internet about the
> fight against licence proliferation and then went to OSI to see how
> things looked for Plan9.
>
> According to their documentation [1, 2], it sort of looks like this
>
> LPL superseded by LPL 1.02, which in turn is redundant with CPL and
> CPL in turn is superseded by EPL [3].
>
> Does this mean that for all intents and purposes, Plan9 can be
> considered EPL (even if licence notices say otherwise)?
>
> ...

I would definitely be easier to have them all consolidated down into a
couple, but the problem is that any developer/creator can choose the terms
under which their work is distributed and used, and some of the terms are
truly BIZARRE (see the Death and Repudiation license --
http://github.com/indeyets/syck/blob/master/COPYING -- where you have to be
running the software while you are dead. I kid you not.  I just have to
wonder about the legal loophole for zombies...).  In order to truly
consolidate these licensing you would have to get explicit acceptance of
every developer on all the other licenses, and probably have them relicense
the software.  Do you think you can get Lucent to relicense pla9 as EPL?
Is it worth everyones time to make this happen?

  EBo --



  reply	other threads:[~2010-05-26  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  8:37 staalmannen
2010-05-26  9:55 ` EBo [this message]
2010-05-26 12:03 ` Anthony Sorace
2010-05-26 12:42   ` Charles Forsyth
2010-05-26 15:57     ` Jack Johnson
2010-05-26 17:24       ` Nick LaForge
2010-05-26 19:57         ` Jack Johnson
2010-05-26 20:08           ` Corey
2010-05-26 20:28             ` Jack Johnson
2010-05-26 20:42               ` Corey
2010-05-27  3:10     ` Anthony Sorace
2010-05-26 18:50 ` Russ Cox

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=c06f7c7b65312b73c2fd4e334c8c1290@swcp.com \
    --to=ebo@sandien.com \
    --cc=9fans@9fans.net \
    /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.
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).