From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>
Subject: Re: Switching to the OSL License, in a dual way.
Date: Fri, 25 Jul 2003 20:18:32 -0700 [thread overview]
Message-ID: <20030726031832.GE14606@work.bitmover.com> (raw)
In-Reply-To: <20030726025246.GA30151@merlin.emma.line.org>
I've looked into this and I think if you dig into you'll find that this
stuff is all claused in "if they don't provide the API's to interoperate".
It's a moot point anyway because by the time anyone has come anywhere near
to reverse engineering what we do today we'll be years beyond that. In
some ways, that's fine, either we keep moving or die. I can live with that.
On the other hand, I'm not about to hand our IP out on a silver platter.
Be legal or be in court...
On Sat, Jul 26, 2003 at 04:52:46AM +0200, Matthias Andree wrote:
> On Fri, 25 Jul 2003, Larry McVoy wrote:
>
> > > This is exactly the same. As long as there is a data format or a
> > > protocol involved, European laws allow users to reverse engineer it,
> > > to be able to create another program using the same format and
> > > protocols.
> >
> > Really? Show me that law please.
>
> IANAL, but check the "German Gesetz ?ber Urheberrecht und verwandte
> Schutzrechte" (Urheberrechtsgesetz/UrhG for short), ?? 69c, 69d, 69e.
> http://bundesrecht.juris.de/bundesrecht/urhg/index.html
>
> It concerns itself with "interoperability" of independently developed
> programs with an existing one that you may use, (not with clones though,
> the law formulates this differently); decompilation is allowed, unless
> information needed to obtain interoperability is available, and there
> are other restrictions. License or contract clauses that attempt to run
> counter to ?69d 2,3 (backup copies to ensure future use) or ?69e
> (decompilation) are void.
>
> Anyone interested should check out the exact words of the law though,
> and in particular he should not rely on my translation.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-07-26 3:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 8:40 Switching to the OSL License, in a dual way Dean McEwan
2003-07-24 8:58 ` Miles Bader
2003-07-24 9:46 ` Andre Hedrick
2003-07-24 18:06 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 20:02 ` Andre Hedrick
2003-07-24 21:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 21:57 ` Larry McVoy
2003-07-24 22:24 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25 9:56 ` Gaël Le Mignot
2003-07-25 14:39 ` Larry McVoy
2003-07-26 2:52 ` Matthias Andree
2003-07-26 3:18 ` Larry McVoy [this message]
2003-07-25 13:17 ` Jesse Pollard
2003-07-25 14:55 ` Larry McVoy
2003-07-25 15:15 ` Gaël Le Mignot
2003-07-25 15:33 ` Richard B. Johnson
2003-07-26 19:10 ` Rik van Riel
2003-07-26 19:23 ` Larry McVoy
2003-07-26 19:46 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-26 20:01 ` Larry McVoy
2003-07-26 21:08 ` Mr. James W. Laferriere
2003-07-26 20:21 ` Bernd Eckenfels
2003-07-24 9:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-27 9:21 ` Kai Henningsen
2003-07-24 11:30 ` viro
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 10:35 Samium Gromoff
2003-07-24 11:51 Dean McEwan
2003-07-24 22:25 ` Stefan Reinauer
2003-07-25 9:34 Samium Gromoff
2003-07-25 13:27 ` Gaël Le Mignot
2003-07-25 15:33 John Bradford
2003-07-25 15:36 ` Valdis.Kletnieks
2003-07-26 19:46 Hank Leininger
2003-07-26 20:20 John Bradford
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=20030726031832.GE14606@work.bitmover.com \
--to=lm@bitmover.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox