mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: SCO's copyright claims or lack thereof (was: Re: Linux v2.6.9 and GPL Buyout)
Date: Sat, 23 Oct 2004 18:58:23 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEPEPDAA.davids@webmaster.com> (raw)
In-Reply-To: <20041023124054.580.qmail@science.horizon.com>


> Just for everyone's information... this is a bit long, but ends up arguing
> that, if Caldera/SCO had a shred of evidence of copyright infringeent,
> they would heva introduced it in court by now.

	It seems pretty clear at this point that SCO has no actual copyright or
patent claims against code that is in the Linux kernel. All they have are
theft of trade secret and violation of the spirit of the contract type
claims against those entities that have had direct contact with SCO (and
thus could steal their trade secrets or violate their contracts with them).

	If there is one possibly good thing that has come out of the SCO fiasco, it
is a greater awareness of the risk of copyright infringement, especially
with open source code. Had SCO actually held copyright to any work that
actually wound up in the Linux kernel, we would all be at risk of serious
liability. One can even envision a situation where someone maliciously (but
with plausible deniability) allows their copyrighted expression to get into
an open source project to create the ability to go after people who
otherwise would have no interest in using their code.

	People who control the input of new source into large open source projects
do need to be vigilant with regard to the copyright and patent status of
that code.

	DS




      reply	other threads:[~2004-10-24  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 12:40 linux
2004-10-24  1:58 ` David Schwartz [this message]

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=MDEHLPKNGKAHNMBLJOLKKEPEPDAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®