BitKeeper: No holds barred open source infighting

BitKeeper: No holds barred open source infighting

Summary: There's a pitched battle raging between various factions of the open source community over whether proprietary software should be avoided at all costs


Open source enthusiasts are by definition a passionate bunch, with no quarter given or expected in the numerous chat rooms devoted to community-developed software. But even the most furious flaming evoked in the past pales in comparison to the fuss surrounding the latest open source hot potato: BitKeeper.

The fact that this particular scuffle involves two of the community's biggest names, Linux founder Linus Torvalds and Samba co-founder Andrew 'Tridge' Tridgell, goes some way to explaining why chat rooms are blazing at the moment.

At the centre of the row is a proprietary source-control application, BitKeeper, which has been used in kernel development since 2002. Some free software advocates argue that proprietary applications should not be used, on principle, in the development of free and open source software. The more pragmatic elements of the community, Torvalds included, claim that BitKeeper is the best tool available and should be used if it makes kernel development easier.

BitMover, the US-based company behind BitKeeper, agreed to make the tool available free of charge to open source developers, on the condition that developers using BitKeeper would not create a competing product. But now it seems that some open source developers haven't kept up their end of the bargain. Bitmover recently announced that it will be phasing out its free BitKeeper product to allow it to focus on its commercial version.

BitKeeper's main author Larry McVoy claims his company made the move to kill off the free tool as a direct response to Samba developer Tridgell's decision to reverse-engineering Bitkeeper. The resulting clone would violate BitMover's intellectual property — something McVoy wasn't going to sit back and watch happen.

Torvalds has joined McVoy in criticising Tridgell's actions. In a posting on the Real World Technologies Web site he states that Tridgell should have written a control application from scratch rather than attempting to clone Bitkeeper.

"Tridge could have done something constructive: he could have written the best damn SCM [source control management application] on the planet, and believed that open source generates better things, and competed against BitKeeper that way," says Torvalds in the posting.

"But that's not what Tridge did… He didn't create something new and impressive. He just tore down something new (and impressive) because he could, and rather than helping others, he screwed people over. And you expect me to respect that kind of behaviour?" wrote Torvalds

Topics: Apps, Software Development

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Actually, what the article writes is not true.

    First of all, the free BitKeeper license does not state that you cannot use BitKeeper (BK) to help develop a competing product; it states that you cannot help develop a competing product *at all*.

    Second, Mr Tridgell has never actually used BitKeeper under its free license, so he is not bound by any of the terms set forth therein; the statement that "some open source developers haven't kept up their end of the bargain" is thus simply not true.

    Third, it's important to note that the "bargain" mentioned has actually gradually shifted over time; the "you are not allowed to work on a competing product" clause was not in the license when BitKeeper was first adopted for the kernel development process, for example. Rather, the original bargain was - roughly - "the kernel developers get to use BitKeeper for free; BitMover gets to say that its product is good enough for even a very high-profile, high-visibility product like the Linux kernel" (i.e., BitMover essentially got free advertising).

    It seems, however, that now that BitMover has actually managed to establish itself, Mr McVoy does not need the Linux kernel anymore, and is instead only worried about protecting his company's revenue. Now, that is not morally wrong in itself; but if you look at the circumstances of the withdrawal of the free BitKeeper license, it is pretty obvious that Mr. Tridgell was merely a convenient straw-man for Mr. McVoy.
  • The register has an article on just how much "reverse engineering" was involved:

    For the impatient, or just in case the above URL gets swallowed by the form parser, the short summary is:

    1) telnet to the bitkeeper host on port 5000
    2) type "help"
    3) read the resulting instructions

  • Lies and misdirection from ZDNet? Why stop now.
    1. The open source community was begged to use the tool.
    2. Only a small percentage used it, and only a small percentage agreed to not reverse engineer it.,
  • Thanks for your comments, Karl. I have updated the article to take into account your first comment.

    Regarding your 2nd comment, I did not state that Andrew Tridgell hasn't kept up his end of the bargain.

    Andrew Tridgell's point of view is stated clearly in the first paragraph of the 2nd page: "He claims he did not use BitKeeper when developing his tool and was therefore not subject to the conditions in its licence."
  • This article would be far more insightful if the author actually attempted to get the facts rather then the hype generated around this.

    It would be impossible for Andrew Tridgell to violate anyone's end of the bargain considering that he never possessed or even used bitkeeper. McVoy clearly knows this otherwise he would have made a legal case against Tirdgell rather then spitefully attacking everyone.

    The real loser here will be McVoy. In one fell swoop he did three things:
    1. Made commercial developers wary of using a product that whose management has a proven record of pulling contracts based on actions of those beyond their control.
    2. Lost the free advertising of association with the Linux Kernel and Linus.
    3. Finally and most importantly gave hundreds of highly skilled developers a vested interest in creating a free competing product.

    In all it ends up being a rather foolish decision on the part of McVoy.
  • Ingrid,

    In response to your post:
  • "... has split the open source community down the middle."

    You use this word "middle". I do not think it means what you think it means.
  • Many people only read the first page, or even the first paragraph or two of an article, and this article gives a very anti-Tridge slant from the beginning. Comments supporting what he did don't appear until page two.

    On the first page, the reporter says "Some free software advocates argue that proprietary applications should not be used, on principle, in the development of free and open source software." I believe this is not the general feeling of free/open source developers. Rather it is closer to "Some free software advocates argue that using proprietary applications leaves you vunerable to the company changing licenses or abandonding the development of that application, leaving devoplers in a lurch."

    Also on the first page, the reporter stats as fact that "The resulting clone would violate BitMover's intellectual property". I do not believe this is true at all. This clam may have been made by Larry McVoy, but it is just a claim, not a fact as the reporter has stated.

    On subsequent pages, the report gives a lot of quotes from one "Gary Barnett", from "Ovum", a person and company that I have never heard of. Going to, I find that their website returns the error "An error occurred on the server when processing the URL. Please contact". I guess it is possible that ovum has simply ensured that non-microsoft browsers can't access his website. Either way, this does not speak well of Gary's technical knowledge or independance.
  • I struggle to find an accurate description of the extent to which this article misrepresents the facts in this situation. I will therefore fall back to a phrase local to my part of the world -

    damn lies.

    Tridge did not try to clone bitkeeper. He tried to come up with a way to access data stored inside of bitkeeper without having to buy bitkeeper (with actual cash or by submitting to unreasonable license agreements). The data in question is the programming code for the Linux kernel, which is SUPPOSED to be open to the community. All Tridge was trying to do was to restore access to software code that was supposed to be open in the first place.

    Furthermore, even if Tridge were trying to clone bitkeeper, he was never bound by its license. Ergo, he was never part of any deal for which he would need to keep up his end. He could have taken packet traces of its operation and set off to reverse engineer a complete working clone, and there would be nothing unreasonable or unethical about it. Every single large software company in existence has done the exact same thing.
  • First, Linus' response to Tridge's actions was uncalled for and over the top. He accused Tridge of "tearing down" Larry's work, which it has been established was NOTHING of the kind. This was obviously an intemperate comment on Linus's part due to his irritation over having to change his method of operation.

    Second, Linus was criticized early on for requiring people to use BitMover, a proprietary product, simply for his own preference. I suspect much of his irritation comes from being hoist with his own petard.

    Third, Ovum's spokesman claims that there is nothing wrong with using proprietary software and OSS together. Only a few OSS ideologues believe there is. The problem is when proprietary software is used to make OSS dependent on it. The result in this case demonstrates why this is not a good idea. This has nothing to do with being "childish" and everything to do with being pragmatic - something Linus obviously was not in this case, despite his claims to the contrary.

    In any event, the speed with which Linus has come up with an alternative - git (even though Linus calls it "stupid but fast") - demonstrates that there always an alternative to using proprietary software.

    Finally, the OSS community needs to drop the whole thing and get on with it - while remembering the consequences of trying to tie proprietary software to OSS projects.

    As Bruce Perens has said, "Linus needs to chill out."