public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	pavel@suse.cz, kernel@blackhole.compendium-tech.com,
	hps@tanstaafl.de, linux-kernel@vger.kernel.org,
	jmerkey@timpanogas.org
Subject: Re: Fasttrak100 questions...
Date: Sat, 2 Dec 2000 22:11:46 -0700	[thread overview]
Message-ID: <20001202221146.A21761@vger.timpanogas.org> (raw)
In-Reply-To: <20001202182126.A20944@vger.timpanogas.org> <200012030342.WAA17517@tsx-prime.MIT.EDU>
In-Reply-To: <200012030342.WAA17517@tsx-prime.MIT.EDU>; from tytso@MIT.EDU on Sat, Dec 02, 2000 at 10:42:29PM -0500

On Sat, Dec 02, 2000 at 10:42:29PM -0500, Theodore Y. Ts'o wrote:
>    Date: Sat, 2 Dec 2000 18:21:26 -0700
>    From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
> 
>    Under this argument, it is argued that the engineer who had source 
>    code access "inevitably used" negative knowledge he gained from 
>    his study of the Linux sources.  Absent the vague descriptions of
>    what a "derivative work" is in the GPL, it could be argued that 
>    conversion of any knowledge contained in GPL code is a "derivative
>    work".  
> 
> That's bullshit.  Copyright law very clearly states that it protects the
> fixation of an idea in a medium, and that copyright explicitly does not
> protect the idea itself.  The concept of what is a derived work is very

State Laws may be controlling if they involve contracts.  It has nothing 
to do with Copyright Law, but with the terms of license for someone's
code.  I've seen this crap applied.  I've even been on the receiving
end of it, and been enjoined from working on PUBLIC GPL CODE for 
18 months because of an AGREEMENT and not copyright laws.   

> clearly understood, and there have been a lot of court cases to define

Under inevitability, the neural impules in your brain can be ruled 
to be a derivative work.  Believe me, I am not arguing for the doctrine,
but informing you of it's existence and the broad scope it has 
in IP cases.  

> this precedent.  (My understanding is that in realm of music 7 notes in
> sequence, if copied, is prima facie evidence that there is a derived
> work.  Not 5 notes, and not 8 notes, but seven notes.  Gotta love those
> lawyers at work.  Aren't you glad they settled that?)
> 
>    Personally, I think the doctrine is one of the most evil fucking things
>    in existence, legal opponents call it "the doctrine of intellectual
>    slavery" because it has the affect under the law to be able to convert
>    simple NDA agreements into non-compete agreements, and I've seen it 
>    used this way.
> 
> That's a different matter.  If you use NDA and Trade secret law, then
> yes, might be able to enslave programmers using such a law.  However
> most courts have strict limits to how far they will take non-compete
> arguments, and if an NDA turned into a non-compete, past a certain point

The legal limit is 18 months in most states.  This "I have a right to 
make a living argument" only holds water if the other side refuses to
post a bond.  If they post a large enough bond, a court WILL rule 
in favor of inevitability if they make a good case for it.  (The 
bond required to keep me from programming for 18 months cost Novell 
$10,000,000.00.)

> they will say that a person has a right to earn a living.....
> Fortunately most judges will apply some amount of common sense, even

US Judges are pontius pilate's all -- with hearts as black as the robes
they wear.  They don't care about you, or your rights.  Remember, almost
all judges are lawyers who are too old or to incompetent to practice law
so they get themselves an appointment.  Most of them were crooked lawyers
who went into politics (which is how a lawyer gets made into a judge, BTW,
he goes into politics).

> despite their law school training.  In any case, the GPL doesn't involve
> NDA's or Trade Secrets, so saying that this doctrine could be used to

It has to do with contract law, which is what the doctrine of 
inevitability is all about.  Trade secrets have nothing to do 
with it, it's a question of knowledge gained via access to 
code through some form of agreement.  In employment 
situations, it's a trade secret agreement, here in Linux, it's 
a GPL agreement.

> contaminate non-GPL code simply by having people look at GPL code is
> bullshit.

I argued that looking at Novell Public Code under their form of GPL
would not contaminate -- a court ruled otherwise.  The court ruled 
that under inevitability, public code on Novell's website and 
slides presented at Brianshare, even though they were public, 
had the affect of contaminating our internal projects under 
this doctrine.  You don't want to kill all the lawyers, you want to 
kill all the judges -- it was a judge that came up with this 
inevitability doctrine in the first place....

:-)

Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-03  4:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24 22:46 Fasttrak100 questions James Lamanna
2000-11-25  1:35 ` Andre Hedrick
2000-11-25 12:10   ` Henning P. Schmiedehausen
2000-11-25 17:20     ` Andre Hedrick
2000-11-25 17:22     ` Andre Hedrick
2000-11-29 19:53     ` Dr. Kelsey Hudson
2000-11-29 20:08       ` Henning P . Schmiedehausen
2000-11-29 21:11         ` Andre Hedrick
2000-11-29 22:12           ` Stop your abusive language! (Re: Fasttrak100 questions...) Dominik Kubla
2000-11-29 23:52         ` Fasttrak100 questions Jeff V. Merkey
2000-11-30 15:14           ` Christopher Friesen
2000-11-30 18:43             ` Jeff V. Merkey
2000-11-30 18:09               ` Christopher Friesen
2000-11-30 20:10                 ` Jeff V. Merkey
2000-12-02  3:44             ` Peter Samuelson
2000-12-03 22:54               ` Pavel Machek
2000-12-05  4:10                 ` Peter Samuelson
2000-11-29 20:42       ` Alan Cox
2000-11-29 21:05         ` Andre Hedrick
2000-11-29 21:10           ` James A Sutherland
2000-11-29 21:18             ` Alan Cox
2000-11-29 21:30             ` Andre Hedrick
2000-12-02 16:50         ` Pavel Machek
2000-12-02 17:18           ` Alan Cox
2000-12-02 23:46             ` Theodore Y. Ts'o
2000-12-03  1:21               ` Jeff V. Merkey
2000-12-03  1:31                 ` Jeff V. Merkey
2000-12-03  3:42                 ` Theodore Y. Ts'o
2000-12-03  5:11                   ` Jeff V. Merkey [this message]
2000-12-05  7:07                     ` Brian F. G. Bidulock
2000-12-05  8:25                       ` Jeff V. Merkey
  -- strict thread matches above, loose matches on Subject: below --
2000-12-03 16:41 Wayne.Brown
2000-12-03 17:49 ` Pavel Machek
2000-12-03 18:45 ` Alan 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=20001202221146.A21761@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hps@tanstaafl.de \
    --cc=jmerkey@timpanogas.org \
    --cc=kernel@blackhole.compendium-tech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=tytso@MIT.EDU \
    /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