From: christos gentsis <christos_gentsis@yahoo.co.uk>
To: Valdis.Kletnieks@vt.edu
Cc: root <root@mail.gadugi.org>, linux-kernel@vger.kernel.org
Subject: Re: Cherokee Nation Posts Open Source Legisation - Invites comments from Community Members
Date: Wed, 12 Jan 2005 07:03:31 +0000 [thread overview]
Message-ID: <41E4CBC3.4070302@yahoo.co.uk> (raw)
In-Reply-To: <200501061935.j06JZMq4013855@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Thu, 06 Jan 2005 12:37:25 CST, root said:
>
>
>>It's based on the design of the license. Under Cherokee Nation Law, you
>>can have and claim trade secrets in public code released under a public
>>license. This makes it very easy for individual contributors to
>>enforce their rights in the US. We spent months researching this, and yes,
>>it holds up under our laws.
>
>
> You will have trouble with "rights in the US", because of the definition of
> "trade secret" includes 18 USC 1839 (3):
>
> (3) the term "trade secret" means all forms and types of financial,
> business, scientific, technical, economic, or engineering information,
> including patterns, plans, compilations, program devices, formulas, designs,
> prototypes, methods, techniques, processes, procedures, programs, or codes,
> whether tangible or intangible, and whether or how stored, compiled, or
> memorialized physically, electronically, graphically, photographically, or in
> writing if --
>
> (A) the owner thereof has taken reasonable measures to keep such information secret; and
>
> (B) the information derives independent economic value, actual or potential,
> from not being generally known to, and not being readily ascertainable through
> proper means by, the public; and
>
> You'll have a hard time convincing a jury not on the reservation that publishing
> something as open source is at all a "reasonable measure to keep it secret".
>
> In fact, you're going to have a hard time - if you're not a sovereign nation,
> then 18 USC 1839 will trump your law. And if you *are* a sovereign nation,
> you better get some lobbyists that can read and understand the implications
> of 19 USC 2242(a)(1)(A) and/or 19 USC 2242(b)(1).....
hello all
sorry about this question but i didn't understand something in all this
"trade secret" situation...
first: Is there any impact in GNU GPL?
second: does this US law means that everything could be a "trade
secret"? even something like the GUI? or a process bar? and in case
that someone will register them what is going to happens?
third: this under US law, is it applied in EU etc????
thanks for your time
Christos
next prev parent reply other threads:[~2005-01-12 7:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 18:04 Cherokee Nation Posts Open Source Legisation - Invites comments from Community Members root
2005-01-06 18:36 ` Valdis.Kletnieks
2005-01-06 18:37 ` root
2005-01-06 19:35 ` Valdis.Kletnieks
2005-01-06 20:31 ` OT Re: Cherokee Nation Posts Open Source Legisation Stephen Pollei
2005-01-06 21:32 ` root
2005-01-06 21:55 ` Måns Rullgård
2005-01-06 22:27 ` Valdis.Kletnieks
2005-01-06 23:16 ` Bernd Petrovitsch
2005-01-06 22:27 ` Valdis.Kletnieks
2005-01-07 2:16 ` root
2005-01-07 13:03 ` Helge Hafting
2005-01-07 18:00 ` root
2005-01-08 14:17 ` Helge Hafting
2005-01-12 7:03 ` christos gentsis [this message]
2005-01-12 8:49 ` Cherokee Nation Posts Open Source Legisation - Invites comments from Community Members Valdis.Kletnieks
2005-01-12 17:18 ` root
2005-01-12 20:17 ` Stephen Pollei
2005-01-12 21:05 ` jmerkey
2005-01-13 8:21 ` Daniel Egger
2005-01-12 18:19 ` Bernd Petrovitsch
2005-01-16 16:13 ` Rik van Riel
2005-01-16 20:25 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 18:26 root
2005-01-06 19:44 Stephen Warren
2005-01-06 20:19 ` linux-os
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=41E4CBC3.4070302@yahoo.co.uk \
--to=christos_gentsis@yahoo.co.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mail.gadugi.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 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.