All of lore.kernel.org
 help / color / mirror / Atom feed
From: root <root@mail.gadugi.org>
To: Valdis.Kletnieks@vt.edu
Cc: christos gentsis <christos_gentsis@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Cherokee Nation Posts Open Source Legisation - Invites comments from Community Members
Date: Wed, 12 Jan 2005 11:18:55 -0600	[thread overview]
Message-ID: <20050112171855.GA23106@mail.gadugi.org> (raw)
In-Reply-To: <200501120849.j0C8nkxI000704@turing-police.cc.vt.edu>



There is no impact on the GPL and any Linux code covered under the GPL
remains as such.  The Ga-du-gi OS is defined under the current FSF 
definitions as a "collective work" not a "derivative work".  So all the
folks sending mail to LKML and gadugi.org that implies otherwise
are out in the weeds.  

It just Linux with a new kernel underneath as an /arch port at present.
Over time, most of the GPL code will be replaced and at the option of
copyright holders, possibly converted to another license.  The advantage
to the latter is it will stop a lot of the SCO flak and the critics of 
open source.

The GPL does not specify anywhere that GPL code cannot be incorporated 
into a "collective work".  So this wrong-headed notion that using GPL
code mixed with non-GPL code renders a project a "derivative work" is
absurd and unenforceable.  



On Wed, Jan 12, 2005 at 03:49:45AM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 12 Jan 2005 07:03:31 GMT, christos gentsis said:
> 
> > sorry about this question but i didn't understand something in all this 
> > "trade secret" situation...
> > 
> > first: Is there any impact in GNU GPL?
> 
> I'm not a lawyer, just a sysadmin/programmer who follows this sort of stuff,
> but it's most likely that this will not impact GPL-licensed software, because
> it isn't attempting to restrict what things can be put into GPL software.
> 
> If anything, all this law *actually* does is get Cherokee law to match what
> current US law *already* says.
> 
> > 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?
> 
> It's not a US law - it's a proposed Cherokee law (In the US, there exist
> some Indian reservations that are somewhat autonomous and able to make their
> own laws).
> 
> The actual text of the law as proposed is posted at
> http://www.gadugi.org/article.php?story=2005010611364165
> 
> The Cherokee law would apparently *ban* publishing open source that
> contains a trade secret, as that would be a "Willful breach or willful
> inducement of a breach of a duty to maintain secrecy;" and therefor a no-no.
> 
> (Logic - (1)(d)(i) says it has to be a secret, (1)(d)(ii) says you have to
> apply reasonable efforts to *keep* it secret.  Therefore, *publishing* it
> would be an "improper" means under (1)(a)(iv), and thus (1)(b)(ii)(B) makes it
> "misappropriation"..)
> 
> The company can't even claim there is no "breach" or "improper means" because
> they intended to publish the source code as open source - because then it no
> longer meets the "subject of reasonable efforts to maintain secrecy"
> requirement.  If you're not even trying to keep it a secret, it's not a secret.
> 
> > third: this under US law, is it applied in EU etc????
> 
> It isn't even clear that this law would apply in the US, much less in the EU.
> 
> But that's OK, because there's no real danger here, unless you were hoping to
> use the Cherokee law to protect secrets in code you publish as open source....
> 



  reply	other threads:[~2005-01-12 17:21 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       ` Cherokee Nation Posts Open Source Legisation - Invites comments from Community Members christos gentsis
2005-01-12  8:49         ` Valdis.Kletnieks
2005-01-12 17:18           ` root [this message]
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=20050112171855.GA23106@mail.gadugi.org \
    --to=root@mail.gadugi.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=christos_gentsis@yahoo.co.uk \
    --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 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.