mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@drgw.net>
To: Dana Lacoste <dana.lacoste@peregrine.com>,
	"'Larry McVoy'" <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: BK scales, Bitmover doesn't [was Re: BK stuff ]
Date: Thu, 27 Dec 2001 17:09:42 -0600	[thread overview]
Message-ID: <20011227170941.I25200@altus.drgw.net> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A3B@ottonexc1.ottawa.loran.com> <20011227133951.M25698@work.bitmover.com> <20011227155956.G25200@altus.drgw.net> <20011227142359.O25698@work.bitmover.com>
In-Reply-To: <20011227142359.O25698@work.bitmover.com>; from lm@bitmover.com on Thu, Dec 27, 2001 at 02:23:59PM -0800

On Thu, Dec 27, 2001 at 02:23:59PM -0800, Larry McVoy wrote:
> On Thu, Dec 27, 2001 at 03:59:56PM -0600, Troy Benjegerdes wrote:
> > (I'm quite sure this is off-topic, but oh well :-/ )
> 
> Seems like your outgoing mail filter needs some work if you know it's
> off topic and you post anyway, but what the hey, it's Christmas.
> 
> > However, the real problem I see is that althought Bitkeeper (the product)  
> > scales very well, Bitmover (the company) does NOT. Bitmover needs income 
> > to scale, and I'm worried that if BK takes off for kernel development, 
> > the demands on Bitmover from kernel developers will far outstrip the 
> > increase in income they get from 'commercial' developers. If this happens, 
> > it's only going to end in everyone getting pissed off. 
> 
> This is way off topic.  I could make similar claims about people using
> what your company, Monta Vista, does but you don't see me posting in the
> kernel list about their layoffs, business practices, etc.  I certainly
> could, but it shows no class (not that I've been accused of having lots
> of class, but FUD seems too tasteless for me).

<disclaimer>I am NOT trying to represent MontaVista here in any way.. I'd
have these same issues if I was working for them or not. I really didn't
want to bring MontaVista into this due to previous incidents.</disclaimer>

I suppose you could make similiar claims. However, there is a very
important and subtle difference.  MontaVista is NOT in any position to
tell developers using 'MontaVista' kernels that they must STOP using our
kernel, since it is GPL'ed.

Bitmover, however, is VERY MUCH in a position to tell developers to STOP 
using Bitkeeper. As a matter of fact, it's in your license.

> Regardless, to put minds at ease, we're fine.  While we would welcome
> more revenue (who wouldn't?), we've never had a layoff in our 4 year
> history and aren't planning any.  In addition, we've managed to support
> you and the PPC team for almost 2 years without it being a problem,
> I'm not sure why it should become a problem now.  Oh yeah, tack on MySQL
> as well, that's been under BK for longer than Linux/PPC.  Of course, if
> you are worried about it, since Monta Vista has gotten so much benefit
> out of BK, they could help ensure the continued development by buying
> a support contract.  Hint, hint.
> 
> What if we do go out of business?  What's wrong with that?  If we go
> under, BK reverts to a pure GPL license.  That can't be a problem,
> right?

But potentially not for 6 months, during which time the use of bitkeeper 
is legally dubious, and probably not possible without altering the binary 
(i.e., if openlogging.org goes down), opening up another mess.

> Seems to me it's a win/win.  We either stick around and support it because
> the business model is sound, or we go under and you get it like any other
> open source product.  Yeah, it's better if we stick around because BK
> is pretty complex, but if the open source crowd can handle the kernel,
> gcc, X, etc, they can handle the BK source base, so I really don't see
> the problem here.  What am I missing?

If you don't stick around, OR get unhappy with us using BK, we have a 
problem. Yes, you have some very nice fallbacks, which I thank you for, 
but the fallbacks are still going to cause a great deal of pain.

The real problem is what if you have 300 kernel developers that suddenly 
start costing you support costs of $5,000 a month?

According to the license, that's only 4 months before the 'group of 
licensees' using BK for the kernel cost you $20,000, at which point the 
BKL allows you to cut them off.

If Bitmover ever has to tell someone to quit using BK under the BKL, that, 
IMHO, is a lose/lose situation, for everyone.

-- 
Troy Benjegerdes | master of mispeeling | 'da hozer' |  hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's 
why I draw cartoons. It's my life." -- Charles Schulz

  reply	other threads:[~2001-12-27 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 21:24 The direction linux is taking Dana Lacoste
2001-12-27 21:39 ` BK stuff [was Re: The direction linux is taking] Larry McVoy
2001-12-27 21:59   ` BK scales, Bitmover doesn't [was Re: BK stuff ] Troy Benjegerdes
2001-12-27 22:23     ` Larry McVoy
2001-12-27 23:09       ` Troy Benjegerdes [this message]
2001-12-27 23:40         ` Larry McVoy

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=20011227170941.I25200@altus.drgw.net \
    --to=hozer@drgw.net \
    --cc=dana.lacoste@peregrine.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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®