<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: What Microsoft can and cannot do</title>
	<atom:link href="http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/</link>
	<description>A blog for the enterprise open source community</description>
	<pubDate>Tue, 07 Oct 2008 16:31:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: tomb</title>
		<link>http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73518</link>
		<dc:creator>tomb</dc:creator>
		<pubDate>Fri, 31 Aug 2007 01:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73518</guid>
		<description>As a matter of fact, the issue of Microsoft and GPL3 will appear in court, but not through any action of the FSF. Should Microsoft decide to sue anyone over patent violations, as they have foolishly threatened, then the whole GPL3 argument becomes part of the defense and/or counterclaims. Call it the Mutually Assured Destruction option.
So, bottom line is that Microsoft stands a chance of being hurt by this only if they pull the trigger first, and that's the only way it'll happen.</description>
		<content:encoded><![CDATA[<p>As a matter of fact, the issue of Microsoft and GPL3 will appear in court, but not through any action of the FSF. Should Microsoft decide to sue anyone over patent violations, as they have foolishly threatened, then the whole GPL3 argument becomes part of the defense and/or counterclaims. Call it the Mutually Assured Destruction option.<br />
So, bottom line is that Microsoft stands a chance of being hurt by this only if they pull the trigger first, and that&#8217;s the only way it&#8217;ll happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Lyman</title>
		<link>http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73273</link>
		<dc:creator>Jay Lyman</dc:creator>
		<pubDate>Thu, 30 Aug 2007 18:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73273</guid>
		<description>Thanks for the comment, Savio. You're right that MS can and HAS declared it won't have anything to do with GPLv3, and I agree the issue, like Microsoft's patent threats, will not get to court. My point is that this has repercussions for Microsoft. If it wants a fair shake on its open source software partnerships and initiatives, it cannot seek special treatment on GPLv3 or any other license. Well, it should not, but the title 'What Microsoft can and should not do' doesn't sound as good ;).</description>
		<content:encoded><![CDATA[<p>Thanks for the comment, Savio. You&#8217;re right that MS can and HAS declared it won&#8217;t have anything to do with GPLv3, and I agree the issue, like Microsoft&#8217;s patent threats, will not get to court. My point is that this has repercussions for Microsoft. If it wants a fair shake on its open source software partnerships and initiatives, it cannot seek special treatment on GPLv3 or any other license. Well, it should not, but the title &#8216;What Microsoft can and should not do&#8217; doesn&#8217;t sound as good ;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Savio Rodrigues</title>
		<link>http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73237</link>
		<dc:creator>Savio Rodrigues</dc:creator>
		<pubDate>Thu, 30 Aug 2007 17:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/2007/08/29/what-microsoft-can-and-cannot-do/#comment-73237</guid>
		<description>Jay,

&#62;Microsoft can’t come out and declare that it won’t need to have anything to do with GPLv3 because it says so. 

Actually, Microsoft can do that.  It's now up to the FSF/SFLC/??? to take MS to court if these bodies believe Microsoft has violated terms of the GPLv3.  

My bets are against this happening.  First there is the issue of legal costs.  Second the issue of setting legal precedent (but IANAL).

Savio</description>
		<content:encoded><![CDATA[<p>Jay,</p>
<p>&gt;Microsoft can’t come out and declare that it won’t need to have anything to do with GPLv3 because it says so. </p>
<p>Actually, Microsoft can do that.  It&#8217;s now up to the FSF/SFLC/??? to take MS to court if these bodies believe Microsoft has violated terms of the GPLv3.  </p>
<p>My bets are against this happening.  First there is the issue of legal costs.  Second the issue of setting legal precedent (but IANAL).</p>
<p>Savio</p>
]]></content:encoded>
	</item>
</channel>
</rss>
