The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pepe@naleco.com (Pepe)
Subject: [TUHS] V8 - V10?
Date: Thu, 22 May 2008 02:45:36 +0200	[thread overview]
Message-ID: <20080522004536.GA26420@d600.naleco.com> (raw)
In-Reply-To: <20080521193153.GP14184@mercury.ccil.org>

On Wed, May 21, 2008 at 03:31:53PM -0400, John Cowan wrote:
> Pepe scripsit:
> 
> > It seems clear, now, that the copyright on that is Novell's, and that
> > The SCO Group *never* had the copyright for that transferred to them by
> > Novell, and that therefore the "open-sourcing" of that material done by
> > Caldera is void because Caldera was lacking just title to do such
> > re-licensing.
> 
> IANAL and TINLA, but Caldera *did* have a license to sublicense the
> content to third parties (which is not the same as copyright ownership),
> so the BSD license should be valid.

Wrong. Caldera had a License to UNIX (including System V and UnixWare)
furnished by Novell, and they could only sublicense with a different
license if under Novell's prior permission to do so, which didn't happen.

Section 4.16(b) of the "Asset Purchase Agreement" entered to by the old
Santa Cruz and Novell, states: "[Santa Cruz] shall not, and shall not
have the authority to, amend, modify, or waive any right under or assign
any SVRX License without the prior consent of [Novell]". It is true that
here they are talking about System V, and not about Version 8 - Version
10.

What Novell transferred to the old SCO was the UNIX and UnixWare
trademarks, the UNIX business assets, and a license to pursue the UNIX
business on their own; and it excluded the UNIX and UnixWare copyrights.

Judge Dale A. Kimball says in his ruling on the 10th of August of 2007:
"SCO contends that the exclusion of the UNIX and UnixWare copyrights
would render the APA meaningless because it would prevent Santa Cruz
from pursuing its UNIX business. [...] Contrary to SCO's assertions,
there is evidence that SCO did not need to own  the UNIX and UnixWare
copyrights to pursue its UNIX business. It is well established that a
contract involving copyrighted works confers an implied  license to use
the copyrights as needed to implement the transaction."

So, The SCO Group can operate the UNIX business it acquired from Novell,
but cannot change the license of that material is under because The SCO
Group does not own copyright of it, and because the APA the old SCO
and Novell entered prohibits such change of license without Novell's
permission.

It's not all clear cut, because the explicit reference to the
prohibition to modify the License only mentions SVRX, but it follows
quite clear that only the copyright owner, or those allowed to do so by
the copyright owner, can change the license of the material.

Therefore, only Novell can "open-source" V8 - V10, which is the point
being discussed here, and Caldera had no title to do it.

-- 
Pepe
pepe at naleco.com




  reply	other threads:[~2008-05-22  0:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1211335201.23443.tuhs@minnie.tuhs.org>
2008-05-21 18:52 ` Pepe
2008-05-21 19:31   ` John Cowan
2008-05-22  0:45     ` Pepe [this message]
2008-05-22  0:54       ` Larry McVoy
2008-05-22  4:59         ` Al Kossow
2008-05-22  9:09         ` Wesley Parish
     [not found] <mailman.5.1211508001.31735.tuhs@minnie.tuhs.org>
2008-05-23 14:05 ` Pepe
2008-05-22  5:05 Aharon Robbins
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20 18:58 Aharon Robbins
2008-05-21 12:31 ` John Cowan
2008-05-22  5:07 ` Warren Toomey

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=20080522004536.GA26420@d600.naleco.com \
    --to=pepe@naleco.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.
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).