08.02.07
With Novell’s Deal, Microsoft is Already Bound by GPLv3
Microsoft insists that it has no involvement with GPLv3, but not everyone agrees. The following discussions, for example, contradict a previous analysis from a seemingly-isolated party.
According to the GPLv3 lawyers, they’re [Microsoft] “procuring the distribution of” GPL’d software, and that requires permission from the copyright holder. So Microsoft are either distributing under the permissions which the GPL grants them, or they are violating copyright.
As always, the media only covers the arguments which defend Microsoft’s side. Why is this not surprising? The following new article separates GPLv3 lies from facts.
In an email to me last month, Linus Torvalds, who has been portrayed in the media as GPLv3’s main opponent, describes the language that he and other use on the Linux kernel mailing list as “blunt, to the point, and not very polite.” When journalists quote pieces of it, he notes, often “the context of that language is then lost entirely” — and he adds that “it’s not just the text of the thread itself that is the context; the context is also how technical people discussing things amongst each other is in itself a very different context than a trade magazine article.”
Highlight: Novell was the first to acknowledge that Microsoft FUD tactics had substance. Novell then used anti-Linux FUD to market itself. 
Highlight: Xandros let Microsoft make patent claims and brag about (paid-for) OOXML support. 
Highlight: Linspire's CEO not only fell into Microsoft arms, but he also assisted the company's attack on GNU/Linux. 
Highlight: Microsoft craves pseudo (proprietary) standards and gets its way using proxies and influence which it buys. 
Highlight: The invasion into the open source world is intended to leave Linux companies neglected, due to financial incentives from Microsoft. 
Analysis: Xen, an open source hypervisor, possibly fell victim to Microsoft's aggressive (and stealthy) acquisition-by-proxy strategy.
MattD said,
August 3, 2007 at 11:02 am
Well… I hope that Torvald’s has learned a valuable lesson here about being used as a pawn. He isn’t 20 years old anymore and shooting off at the mouth hasn’t helped the Linux community.
There is a big picture here (as this site clearly demonstrates). From what I recall, he was asked to participate in helping to go over details of gpl 3. This request, I gather, was to keep disagreements between high-level Linux leaders closed doors and to help form some basis of solidarity. Instead he chose to attack the gpl 3 while the option to remain gpl 2 (for the kernel) was always open to his team.
The politics involved in this entire process effects millions and has entered news outlets and the political process itself. Money… which is a key motivator for many, is in the billions. MS, the real enemy here, has already (libelously and maliciously) attacked the work of the kernel development team labeling them as nothing more than pirates and crackers of Microsoft Technologies. If MS is right, the kernel development team (and Torvalds) will be fined millions and be closed down for good!
I would certainly love to see Torvalds use the same fire and passion against MS as he so willingly does against the FSF. Oddly… this hasn’t happened…
Although Torvalds doesn’t see himself as a leader, he is exactly that to many in the Linux camp. If he doesn’t understand the business and political forces at work here - he should educate himself before spouting off with so many knee-jerk reactions.
fyi… GPL 2.0 vs GPL 3.0 - chart at Groklaw:
http://tinyurl.com/2fc6md
Roy Schestowitz said,
August 3, 2007 at 11:24 am
Linus has been avoiding the Big Novell Question since the very beginning (November 2006). That was a smart move. He avoided frication and division (unlike Stuart Cohen). Ironically, he went loose and vented his anger at the wrong people.
At risk of regretting what I say, I agree with you wholeheartedly and I have criticised Linus many time before (in other forums). I respect him enormously, but his strong language and total disregard for his roots makes some people want to look away sometimes. I spoke to CK (briefly) and it seems apparent that the attitude of the core team (kernel developers) drove him away about a month ago.