All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Shaver <shaver@netscape.com>
To: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
Cc: Philipp Rumpf <prumpf@suse.de>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Helge's commits
Date: Sun, 11 Jul 1999 18:36:01 -0400	[thread overview]
Message-ID: <37891C51.71A7F3F5@netscape.com> (raw)
In-Reply-To: 37886585.34B86082@ruhr-uni-bochum.de

Helge Deller wrote:
> From what I (and you too) saw, Utah CSS/CSL would be able to change that license,
> the only question is, if OSF is willing to change it too ?

OSF's license is _probably_ GPL-compatible as-is, though the requirement
for mention of permission notice in documentation might put it afoul,
and I'd want to check with a real lawyer to be sure.  The Utah CSS/CSL
license, as currently in place on pdc.h and such, is not at all
GPL-compatible.  Hopefully, we can get it changed, but in the meantime I
don't think we should be barging ahead and adding these files to the
tree. 

I and others (self-identify if you wish) think that until the issues are
cleared up, we should probably remove the OSF/CSS/CSL code from the
tree.  Hopefully we can get it all cleared up in short order, but until
then I'm nervous about what happens a month from now when Utah says
``no, you can't relicense'' and we have to redevelop lots of the code. 
Ask the 4.4LITE guys, it's not fun.

Mike

-- 
350842.71 306592.32

  reply	other threads:[~1999-07-11 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199907101141.FAA25297@puffin.external.hp.com>
1999-07-10 22:46 ` [parisc-linux] Helge's commits Philipp Rumpf
1999-07-11  9:36   ` Helge Deller
1999-07-11 22:36     ` Mike Shaver [this message]
1999-07-12  4:40 Mike Hibler
1999-07-12  5:00 ` Philipp Rumpf
1999-07-12  5:20   ` Jeffrey A Law

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=37891C51.71A7F3F5@netscape.com \
    --to=shaver@netscape.com \
    --cc=Helge.Deller@ruhr-uni-bochum.de \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.