BitKeeper Love Triangle: McVoy, Linus and Tridge
erktrek writes "NewsForge has given a brief interview to the parties involved in the (inevitable?) BitKeeper debacle." Here is some of our previous coverage.
← Back to Stories (view on slashdot.org)
Tridge offers his side
There is no doubt Tridge is being cast as the villain in this piece. Here's what he had to tell us when we asked him for his side of the tale:
I expect that in the future I will be able to give a more detailed response, but for now I can only tell you the following:
- In late February I wrote a tool that is interoperable with BitKeeper. The aim was to provide export to other source code management tools and provide a useful tool to the community.
- I did not use BitKeeper at all in writing this tool and thus was never subject to the BitKeeper license. I developed the tool in a completely ethical and legal manner.
Boy, I hate to say it, but whenever somebody "defers" on defending themself, it sure looks like they have something to hide. Why wait until some undefined "later" point to explain one's self, if one has nothing to hide?
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_ _ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __
g_______________________________________________g
o_/_____\_____________\____________/____\_______o
a|_______|_____________\__________|______|______a
t|_______`._____________|_________|_______:_____t
s`________|_____________|________\|_______|_____s
e_\_______|_/_______/__\\\___--___\\_______:____e
x__\______\/____--~~__________~--__|_\_____|____x
*___\______\_-~____________________~-_\____|____*
g____\______\_________.--------.______\|___|____g
o______\_____\______//_________(_(__>__\___|____o
a_______\___.__C____)_________(_(____>__|__/____a
t_______/\_|___C_____)/LINUX_\_(_____>__|_/_____t
s______/_/\|___C_____)_INSIDE|__(___>___/__\____s
e_____|___(____C_____)\_(TM)_/__//__/_/_____\___e
x_____|____\__|_____\\_________//_(__/_______|__x
*____|_\____\____)___`----___--'_____________|__*
g____|__\______________\_______/____________/_|_g
o___|______________/____|_____|__\____________|_o
a___|_____________|____/_______\__\___________|_a
t___|__________/_/____|_________|__\___________|t
s___|_________/_/______\__/\___/____|__________|s
e__|_________/_/________|____|_______|_________|e
x__|__________|_________|____|_______|_________|x
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Tridge has reverse engineered BK by pulling out code out of BK tree. Why? Because he feels so strongly that software should be free that he thinks it's OK to resort guerilla tactics like this to liberate it.
Free software fanatics like him make me sick.
Then again, Larry is partly to blame for exposing the source code in the first place.
Information wants to be free.
Just like convicted child-molesters want to be free.
I know that it's heresy to say this on slashdot, but it sounds like things were running pretty fine until rabid open-source zealotry reared its ugly head.
Although BK has always been a source of controversy among kernel developers, fans of BK were happy and productive using it, while anti-BKers were also happy and productive, using whatever other SCM software they wanted. So everything's kosher.
Then this 'Tridge' guy comes along, and is *so* opposed to BK that he is determined to fight against it using tactics that are legal, but not especially moral, ethical, or friendly. Then, while a temporary cease-fire is arranged so that the matter can be discussed and resolved maturely, he violates this truce.
So now that so much happiness and productivity has been ruined, are the license zealots happy? I hope so.
Slashdot: come for the pedantry, stay for the condescension.
But in this post, Linus says he was writing scripts to export data in an SCM-independent format. McVoy actually offered to support this directly in BitKeeper, but Tridge insisted on "being difficult about it" and gaining access directly to the binary data. Linus suggests he's bitter at Tridge for it, and now he can't use BitKeeper.
Larry McVoy is like a whiny little girl. He should know better that Linux-folks are just riding on every coat-tails they possibly can.
Even Linus is getting tired of all that OSS-crap. Nowdays his primary desktop is PowerMac G5 and he dualboots it all the time.
People flame RMS zealots because RMS zealots flame anyone who uses something that doesn't fit their narrow definition of "free." These zealots go on and on about a "free world" that they define and others must follow.
That is not freedom. Freedom is letting me use BitKeeper if I want to. Remember that it is one of these RMS zealots who wasn't satisfied with BitKeeper providing an SCM-independent export function (McVoy offered it directly to Linus) and just had to reverse-engineer the binary data itself to make it "free." I'm sorry, but you guys look bad in this. The extremism of fitting everything into your definition is hindering progress--now we get to wait while kernel development seeks an alternative SCM.
If you wanted a free SCM to compete with BitKeeper, why didn't you guys write a new one yourselves? Software freedom apparently means not just access to source code, but access to anything else you want just because you want it to be "free." That's not the OSS movement I signed up on.
If people want to use BitKeeper, let them! It's called freedom of choice.
There's nothing wrong with Tridge writing a program that can read Bitkeeper'd files ...
Yep, nothing wrong except his noble effort fucks up entire kernel development process for few months. Otherwise it's perfectly fine. Keep hacking, Tridge ! Way to go.
This has NOTHING to do with interoperability. There were clients available already for the platform, and it didn't produce closed-format output (a source checkout).
Tridge was license cracking. BK is charged per-client and he was attempting to get around that. Sure, his solution would have been OSS, but that wasn't the drive behind it.
Have none of you worked with licensed software before? I don't know a single vendor that would be happy for someone to make a client that did not respect their licensing. Perhaps BK's business model is to distribute the server and make money from per-seat cost (I don't know). This client would sink their business. They gotta eat.
MOD PARENT UP!!!
What the parent does not mention, however, is that this almost always happens. Commercial software companies almost always do something that causes problems for their users. They raise prices, declare premature death of their products (Microsoft has more than 100,000,000 Windows 98 users, but they say the product is dead.), or become adversarial in other ways.
FIX THE SLASHDOT MODERATION SYSTEM!!! Moderators can only moderate discussions in which they have no interest in contributing.
People like me, who have excellent karma, never get moderation points. Why? I don't know, and there is no way to learn.
The parent comment was at +3 when I began writing this comment. Now it is at -1. Did a Slashdot employee moderate it down? Was there a kind of censorship?
I dunno, that sounds to me a lot like justifying screwing someone's wife by saying something like, "hey she was passed out in my bedroom".
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
I fail to understand why Tridge had to do any development of his own. I remember from the very early days of linus deciding to use bk that Larry McVoy was VERY helpful, in fact, bending over backwards, to give the kernel developers any and all the help they could ask for and implementing new features to fit their needs. And all of this at no real cost to any of the kernel developers. I can't imagine what changed, or why Tridge would need to do any development that Larry was either unable or unwilling to implement in bk. It sounds to me like Larry was indeed amenable with any suggestions the kernel developers had and helped out in any way he could. To continue down another path of development just for the sake of development doesn't make any sense. However if Tridge did want to write another SCM, then Larry was right in his course of action.
On another note, if you really believe that ALL software should be free, you are living in a utopian reality. The world is imperfect. Different economic philosophies and realities exist. Some demand equality for all. Others demand strict adherence to a natural order. Neither is right all the time. And so free software and proprietary software MUST exist in our imperfect world, else somebody starves or somebody misses out on the opportunities of an evolving world. Don't allow yourself to be fooled by fools.
Here is a useful website in regards to the issues surrounding the BitKeeper product