Linux, Linus, BitKeepr and zealotry…

โ€”

by

in

“So I think open source tends to become technically better over time (but it does take time), but I don’t think it’s a moral imperative. I do open source because it’s fun, and because I think it makes sense in the long run.

For some reason that is hard for a lot of free software people to accept. Too many people see things as a war of “free software” against “proprietary evil”. This is, btw, the real difference between the “open source” crowd and the “free software” crowd, as far as I’m concerned.” – Linus (quote in context)

The Open Source Zealot (OSZ) crowd (more specifically the GNU zealot crowd or GNUZ) are doing all they can, apparently, to make sure the GPL and those who support it are kept far, far away from important data. At this point, I am not sure that I could advocate any company basing a strategic tool or product on GPL’d software or technology in any way that might possibly taint it… which means in just about any way.

The Message is clear: No matter what it is, no matter how you try and help… many in the “open source community” will try and steal, taint or clone your work.

The thing is, many of those in the GPL camp are simply anti-business and anti-corporation. They not only want to control the code they write, but to control the intellectual property of others… dictating what you can and cannot do with the product of your own thought and work. Unlike the folks who use the BSD license, those who follow the GPL are actively looking for ways to “infect” your IP rights with their own. Hell, in some cases even using a GPL’d font seems to imply that your entire document is now under the GPL. Did you ever print out your screenplay using a GPL’ed tool? If so, you might no longer be able to enforce any control over who copies your script.

When they can’t infect you, they are more than willing to attack you and outright steal your work (see how many support the pirating of music and movies) or simply copy your work. The vast majority of the OSS projects I see are simply a bunch of people who get together to more or less effectively copy a commercial product.

In recent weeks, this has come to a head. When Linus needed a tool to manage development of the Linux Kernel he selected BitKeeper, an excellent and innovative tool from BitMover because there simply was no open source alternative. They in turn provided a free version of their tool to all those who were working on Open Source projects… the sole exception was that they did not want their tool used to aid in the creation of a competing tool. It was beneficial to everyone.

“”Would I prefer to use a tool that didn’t have any restrictions on it for kernel maintenance? Yes. But since no such tool exists, and since I’m personally not very interested in writing one, _and_ since I don’t have any hangups about using the right tool for the job, I use BitKeeper. – Linus

The zealots howled and frothed. They screamed and groaned, the whined and cried. They did everything, in fact, but the one thing that would have been useful – create a open source tool that could match BitKeeper in terms of functionality. For years they groused and groaned… and still created nothing competitive that was ready to use. Then, someone turned to doing what it seems the zealots do best – piggy backing on the work of a commercial entity and copying their work in the name of “freedom”. Hell, they are now attacking Linus himself for not being a zealot.

“”Big boo-hoo, bitkeeper is evil, and Linus doesn’t manually do any more what BK plus a few scripts does better for us automatically. – Linus

Someone named “Tridge” started working on a tool that had almost no value except making it impossible for Linus to keep using BitKeeper. He deliberately set out to make the situation intolerable – and succeeded. By monitoring the traffic to and from a BitKeeper server (violating the BK license in the process) he started writing a client tool to work with a BK server. By violating the license, he created a breaking point problem. Even after being asked to stop work at least temporarily by Linus and their employer he kept on keeping on.

  • Did Tridge break a law? Doubtful.
  • Did he break the license? Yeah, but it might be unenforceable.
  • Was he a dick? Yes.
  • Does this server as a warning to any company that might think open source can be their friend? Yes.

In the end, Linus did the right thing ethically and is moving away from BitKeeper since it is clear those around him will continue to abuse the relationship and continue to try and destroy BitKeeper at any opportunity. Having Bk available for the Linux Kernel was giving them an edge to do that.

The whole sordid story can be found online, just go through the links below.

History:

Misc related information:


Comments

2 responses to “Linux, Linus, BitKeepr and zealotry…”

  1. Whistler

    “Did you ever print out your screenplay using a GPLโ€™ed tool? If so, you might no longer be able to enforce any control over who copies your script.”

    Have you ever read the GPL carefully?! And I highly doubt you even know what “free software” and “open source” really mean.

    btw please do NOT spread FUD. Thanks.

  2. Soulhuntre

    Have you ever read the GPL carefully?!

    Yes, in fact I have… and the problem of using GPL’d font is a clear and real one as an example. I am not the only person with grave concerns over the infectious nature of the license.

    When I want “free” and “open source” it seems clear to me the BDSM licence is better at delivering both.