From: Larry McVoy <lm@bitmover.com>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: 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 14:23:59 -0800 [thread overview]
Message-ID: <20011227142359.O25698@work.bitmover.com> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A3B@ottonexc1.ottawa.loran.com> <20011227133951.M25698@work.bitmover.com> <20011227155956.G25200@altus.drgw.net>
In-Reply-To: <20011227155956.G25200@altus.drgw.net>; from hozer@drgw.net on Thu, Dec 27, 2001 at 03:59:56PM -0600
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).
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?
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?
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-12-27 22:24 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 [this message]
2001-12-27 23:09 ` Troy Benjegerdes
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=20011227142359.O25698@work.bitmover.com \
--to=lm@bitmover.com \
--cc=dana.lacoste@peregrine.com \
--cc=hozer@drgw.net \
--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