mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Alvord <jalvo@mbay.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Never ever use word BitKeeper if Larry does not like you
Date: Fri, 14 Mar 2003 16:49:37 -0800	[thread overview]
Message-ID: <fqt47vk89d2sq6v3tfm5fj5o0jsgebalg6@4ax.com> (raw)
In-Reply-To: <873clpbovs.fsf@deneb.enyo.de>

On Fri, 14 Mar 2003 22:48:55 +0100, Florian Weimer <fw@deneb.enyo.de>
wrote:

>Jeff Garzik <jgarzik@pobox.com> writes:
>
>> Thus, even to have an open source BK export tool requires that key
>> BK algorithms be open sourced.
>
>You can't "open source" algorithms.  Unpatented algorithms are always
>free to use.
>
>It's sufficient if somebody looks at the algorithms employed by BK and
>documents them in plain English at a very abstract level.  (Reading
>your properly licensed copy of the BK source code and writing down
>your thoughts can't be illegal, can it?)  Somebody else can go ahead
>and implement them, unencumbered by the BK copyright and BK license.
If I were in BitMover, I would treat such advances as trade secrets,
like the formula for coca-cola. Trade secrets are ideas/processes
which are held privately. From the discussion it feels to me like they
have made some real advances in "keeping objects up to date across a
hetrogenous collection of systems and with a varying time flow" and
publishing that advance would remove their advantage.

With patents you have to publish the advance which would provide key
direction to competitors. Copyright is OK but also implies publishing.
You can keep to formula to coca-cola pretty much forever as long as
people want to buy the product.

John Alvord

  reply	other threads:[~2003-03-15  0:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030314184009$1b0a@gated-at.bofh.it>
     [not found] ` <20030314184009$54f5@gated-at.bofh.it>
     [not found]   ` <20030314184009$6d9e@gated-at.bofh.it>
     [not found]     ` <20030314184009$548a@gated-at.bofh.it>
     [not found]       ` <20030314184009$69b1@gated-at.bofh.it>
2003-03-14 21:48         ` Florian Weimer
2003-03-15  0:49           ` John Alvord [this message]
2003-03-15  7:51             ` Florian Weimer
2003-03-15 14:32             ` Henning P. Schmiedehausen
2003-03-14 10:51 Pavel Machek
2003-03-14 11:19 ` Murray J. Root
2003-03-14 11:50 ` Lars Marowsky-Bree
2003-03-14 13:35   ` Richard B. Johnson
2003-03-14 14:43   ` Larry McVoy
2003-03-14 16:10     ` Alan Cox
2003-03-14 15:14       ` Larry McVoy
2003-03-14 16:11         ` Stephen C. Tweedie
2003-03-14 16:21           ` John Jasen
2003-03-14 16:28             ` Stephen C. Tweedie
2003-03-14 16:37               ` Larry McVoy
2003-03-14 17:09                 ` Davide Libenzi
2003-03-14 18:29                   ` Jeff Garzik
2003-03-14 18:48                     ` Davide Libenzi
2003-03-14 17:10                 ` Stephen C. Tweedie
2003-03-14 21:12                 ` Mike Galbraith
2003-03-15  0:59                 ` Stephen Satchell
2003-03-14 18:57           ` Wichert Akkerman
2003-03-14 20:49           ` Roger Luethi
2003-03-14 21:55             ` Eric Sandall
2003-03-15  0:56           ` Stephen Satchell
2003-03-15  3:36             ` Werner Almesberger
2003-03-15 12:20             ` Pavel Machek
2003-03-16  0:57               ` Alan Cox
2003-03-16  5:01                 ` Oliver Xymoron
2003-03-14 16:29         ` Alan Cox
2003-03-14 15:29           ` Larry McVoy
2003-03-14 16:43             ` Alan Cox
2003-03-14 16:43             ` Tom Sightler
2003-03-14 16:58               ` Larry McVoy
2003-03-14 17:56                 ` Tom Sightler
2003-03-14 18:34                   ` Valdis.Kletnieks
2003-03-14 17:44         ` Pavel Machek
2003-03-14 20:37         ` Teodor Iacob
2003-03-14 18:29     ` Brian McGroarty
2003-03-14 20:33   ` Teodor Iacob
2003-03-14 21:32     ` Brian McGroarty
2003-03-14 12:06 ` Matthias Andree
2003-03-14 15:38   ` Alan Cox
2003-03-14 16:00   ` Mark Mielke
2003-03-14 16:03     ` Larry McVoy
2003-03-14 16:30       ` Mark Mielke
2003-03-14 23:13   ` Daniel Phillips
2003-03-14 13:42 ` Tomas Szepe

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=fqt47vk89d2sq6v3tfm5fj5o0jsgebalg6@4ax.com \
    --to=jalvo@mbay.net \
    --cc=fw@deneb.enyo.de \
    --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

all inboxes | Powered by JetHome®