From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
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: Tue, 5 Dec 2000 01:25:07 -0700 [thread overview]
Message-ID: <20001205012507.A6216@vger.timpanogas.org> (raw)
In-Reply-To: <20001202182126.A20944@vger.timpanogas.org> <200012030342.WAA17517@tsx-prime.MIT.EDU> <20001202221146.A21761@vger.timpanogas.org> <20001205010730.A5760@openss7.org>
In-Reply-To: <20001205010730.A5760@openss7.org>; from bidulock@openss7.org on Tue, Dec 05, 2000 at 01:07:30AM -0600
On Tue, Dec 05, 2000 at 01:07:30AM -0600, Brian F. G. Bidulock wrote:
> Jeff,
>
> Have you also seen this applied where it is to the employer's
> disadvantage? For example, given that I looked at and worked
> with GPL code (say Linux kernel) in University before taking
> employment as a programmer that the employer's product is
> inevitably contaiminated and no longer a trade secret? Can
> a previous employee get an injunction against their former
> employer to cease and desist from using this negative knowledge?
>
> If so, I might have a solution: make the Linux kernel required
> reading in University programming classes!
Trade Secrets are defined by something called the Uniform Tade Secret
Act, which has been adopted in most states. It calls for several points
that must be met in order for something to be protected as a "trade
secret". Before this act, Muna vs. Microbiological (1964) was one of the
landmark cases outlining trade secret law in the US. A lot has happened
since Muna, but basically, these are the points.
1. A trade secret, must of course, be a "secret".
2. Cannot be readily ascertainable to someone skilled in the art.
3. Reasonable safegards must have been taken to protect it's secrecy.
4. Must have indendent economic value.
Technically, based on the premise of negative knowledge, someone could
work for company A trying to build a software product, and fail at
each attempt, thereby, accumulating negative knowledge. This person
could then quit and go to work for Company B, build the same
product, this time completing it, using previous negative
knowledge gained from Company A. If Company A, had an agreement
respecting trade secrets, under inevitability, Company A could
claim the Company B's product was based on their IP if the
employee did it within 18 months of departing Company A.
This is why I think inevitability is a ridculous doctrine. It
makes claim to the work experinece of employees as IP.
In theory, an employee could not obtain the injunction because
he would have no standing to bring a cause of action, but the copyright
holder would have standing and could if he could show that the
employee used negative knowledge and that he did so within a
certain period of time. It's even more complicated, trade
secret law makes claims that common software components
arranged in new ways would qualify as a trade secret. This could
also mean that any new software this person wrote would
necessarily be intertwined with GPL code and trade secrets of
the employer. In such a case, a Judge would "balance the
equities", and would have to make a call, like telling the company
to remove the GPL sections, and/or requireing the portions of the
code be open sourced. He could also go the other way, and rule
some sections are not covered under inevitablity.
It would be a very complex case, BTW (trade secrets cases always
are).
:-)
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/
next prev parent reply other threads:[~2000-12-05 8:00 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
2000-12-05 7:07 ` Brian F. G. Bidulock
2000-12-05 8:25 ` Jeff V. Merkey [this message]
-- 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=20001205012507.A6216@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