From: Larry McVoy <lm@bitmover.com>
To: Leandro Guimar?es Faria Corsetti Dutra <lgcdutra@terra.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Switching to the OSL License, in a dual way.
Date: Thu, 24 Jul 2003 14:57:44 -0700 [thread overview]
Message-ID: <20030724215744.GA7777@work.bitmover.com> (raw)
In-Reply-To: <pan.2003.07.24.21.05.40.969654@terra.com.br>
On Thu, Jul 24, 2003 at 11:05:40PM +0200, Leandro Guimar?es Faria Corsetti Dutra wrote:
> > For those who can not (will not) read, clearly the suggestion for somebody
> > to take up the cause to develop a "Bitkeeper" clone. Know the details of
> > the license it was issued to the community to use.
>
> I can't quite see your point... what's the problem with a
> clone? It certainly isn't immoral or illegal.
A clone is illegal because you'd have to reverse engineer to do the clone
and reverse engineering is allowed for the purpose of interoperability,
not for the purpose of making a clone. I suspect that the reverse
engineering exceptions were put in place to make sure that vendors
couldn't lockin their customers with no recourse for the customers.
In other words, your data is your data no matter where you store it.
Perfectly reasonable sentiment.
BK already provides more than enough in the way of interoperability,
both on the way in and on the way out. It's trivial to get your
data out of BK as well as your metadata. It's a small perl script
to get all the info out and plop it into some other system, we're
much better about that than any free or commercial system.
In other words, reverse engineering is ok if the product doesn't
provide access to your data, we do that already, poof, no reverse
engineering allowed. So it's illegal to reverse engineer BK.
Given that, you can see why some people are disgusted that RMS would
suggest it is OK to clone BK. At that point, it becomes a statement of
"it's OK to do illegal stuff if you are making GPLed software".
Hardly the sort of thing you want on record in a public forum from a
free software leader when people are starting to question whether or
not the free software they have is actually legal.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-07-24 21:42 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 [this message]
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
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=20030724215744.GA7777@work.bitmover.com \
--to=lm@bitmover.com \
--cc=lgcdutra@terra.com.br \
--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