This wasn't a member of Linus's "team", but Andrew Trigell, the creator of Samba and rsync (who is also currently employed by OSDL, as is Linus, but AFAIK they don't actually work together).

That's why I put the "|" between "decided" and "was forced". IMO it is debatable how wrong it was of Tridge to try and access the BK data without going through the BK format. After all, the approach he used was exactly the same he used for creating Samba, and not too many people call him an unreasonable open-source zealot for that. There was no disassembly or illegal looking at forbidden data going on here, he was simply trying out stuff with telnet. Should reverse-engineering a network protocol be considered wrong? I don't think you'd get any court conviction on that and neither do I think it's morally wrong.

The Bitkeeper "free" license at the time also contained a number of questionable clauses, like basically forbidding anybody who used BK to even think about working on any other SCM. That's just ludicrous IMO. Regardless of that, Tridge wasn't bound by the license because he was not using BK in his reverse engineering, but I think it shows another example of what's wrong with Larry McVoy's mental model of the world.

So I think the fiasco was caused more by McVoy's attitude[1] than by any actions of Tridge's. The issue isn't clear-cut however, hence the "or" sign :-). I tried to make my reply short[2] because it's OT to this forum, and therefore I necessarily left details out. The same thing that applies to tilly's comment also applies here though: exactly why the situation blew up is irrelevant to the danger closed formats represent. McVoy's company could have gone out of business, or he could have been ousted and the new board decided to stop giving free lunches to the open source hippies, and the result would have been exactly the same.

[1] And before someone gets a wrong impression I'd also like to say that in contrast to this affair Larry McVoy has done more for free software than most people in the world (and certainly more than me), he's a fine software engineer and IMO noone should hold a grudge against him for all this. I just think he was wrong on a lot of points here and wish he had a good public-relations person to talk to before sending emails to some people.

[2] Since there does seem to be some interest in a fair and/or more detailed account of the story I'd be happy to write it down more extensively, please /msg me if you feel this would be of value either on PM or off.

Update:I've just realised that the stricken-out part is not true.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re^2: Linux kernel Bitkeeper mess (OT) by tirwhan
in thread Learning How to Use CVS for Personal Perl Coding Practices by neversaint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.