public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@hist.no>
To: root <root@mail.gadugi.org>
Cc: Stephen Pollei <stephen_pollei@comcast.net>,
	Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: OT Re: Cherokee Nation Posts Open Source Legisation
Date: Fri, 07 Jan 2005 14:03:30 +0100	[thread overview]
Message-ID: <41DE88A2.6050004@hist.no> (raw)
In-Reply-To: <20050106213221.GA12866@mail.gadugi.org>

root wrote:

>>>proper means by, the public; and
>>>      
>>>
>>Seems word-for-word the same. And I would think that an Free or Open
>>source licensed work that is published would be "generally known to" and
>>"readily ascertainable".
>>    
>>
>>>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".
>>>
>>>      
>>>
>
>If the license says the receipient of a piece of code must acknowledge 
>and protect the trade secrets it contains, then it's enforceable.  
>
Sure, but if there is a secret that must be protected, then it
isn't open source! 

By definition: open source is something I can give to absolutely anybody
with no reservations.  I.e. no need to protect anything. 

So your law means you can give someone code with the restriction that
they protect the trade secret within, but such code is not open source.
It may be less restrictive than many other commercial/proprietary licences,
(i.e. you can give it away for free, for example) but it is not _open_
with such restrictions. 

The linux source for example, can be given to anybody with no
reservations other than that the GPL is respected.  (The GPL does not
limit redistribution though.) 

Helge Hafting

  parent reply	other threads:[~2005-01-07 12:55 UTC|newest]

Thread overview: 23+ 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 [this message]
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
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

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=41DE88A2.6050004@hist.no \
    --to=helge.hafting@hist.no \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@mail.gadugi.org \
    --cc=stephen_pollei@comcast.net \
    /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