public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Licenses
Date: Tue, 9 Mar 2010 13:10:09 +0100	[thread overview]
Message-ID: <ea2499da1003090410s13d33a19xb24b4cbdb98f4334@mail.gmail.com> (raw)

I'm trying to add app-admin/supervisor (http://supervisord.org/) to
the tree, but its licensing situation kind of sucks.

The file talks about 4 different licenses.

1: the Repoze license (which I added to the tree in anticipation of this ebuild)
2: a copy of the regular BSD license, should be straightforward
4: the ZPL, which we also have

The third is this:

  Medusa was once distributed under a 'free for non-commercial use'
  license, but in May of 2000 Sam Rushing changed the license to be
  identical to the standard Python license at the time.  The standard
  Python license has always applied to the core components of Medusa,
  this change just frees up the rest of the system, including the http
  server, ftp server, utilities, etc.  Medusa is therefore under the
  following license:

  ==============================
  Permission to use, copy, modify, and distribute this software and
  its documentation for any purpose and without fee is hereby granted,
  provided that the above copyright notice appear in all copies and
  that both that copyright notice and this permission notice appear in
  supporting documentation, and that the name of Sam Rushing not be
  used in advertising or publicity pertaining to distribution of the
  software without specific, written prior permission.

  SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
  INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
  NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR
  CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
  OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
  NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
  WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  ==============================

The bit between === and === is the PERMISSIONS AND DISCLAIMER
STATEMENT from the CNRI license (which I think is the standard Python
license 10 years ago), but the CNRI license explicitly names the CWI
and Stichting Mathematisch Centrum (i.e. doesn't talk about
<Organization> or <Owner> like some of the other licenses).

Any clues on what to do with this would be greatly appreciated.

Cheers,

Dirkjan



                 reply	other threads:[~2010-03-09 12:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ea2499da1003090410s13d33a19xb24b4cbdb98f4334@mail.gmail.com \
    --to=djc@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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