<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Tragedy of the Commons in Cloud standards</title>
	<atom:link href="http://stage.vambenepe.com/archives/1549/feed" rel="self" type="application/rss+xml" />
	<link>http://stage.vambenepe.com/archives/1549</link>
	<description>William Vambenepe&#039;s stage</description>
	<lastBuildDate>Tue, 07 Feb 2012 23:33:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mike Leach</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-939</link>
		<dc:creator>Mike Leach</dc:creator>
		<pubDate>Mon, 26 Jul 2010 20:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-939</guid>
		<description>If there is the potential for a &quot;tragedy of the commons&quot; in the cloud, it would be that large cloud companies are building on open source (taking) and technically are not violating the GPL when not giving back their enhancements because &quot;redistribution&quot; doesn&#039;t extend to a server hosting context.

Fortunately, Google and other companies have built sufficient goodwill by giving back to the open source community in many different ways, so few developers want to force the issue (Most OS project leads are even hired to work at these companies). But still, many forks are being held close to the chest.

http://www.infoworld.com/t/applications/gpl-author-google-must-share-code-288</description>
		<content:encoded><![CDATA[<p>If there is the potential for a &#8220;tragedy of the commons&#8221; in the cloud, it would be that large cloud companies are building on open source (taking) and technically are not violating the GPL when not giving back their enhancements because &#8220;redistribution&#8221; doesn&#8217;t extend to a server hosting context.</p>
<p>Fortunately, Google and other companies have built sufficient goodwill by giving back to the open source community in many different ways, so few developers want to force the issue (Most OS project leads are even hired to work at these companies). But still, many forks are being held close to the chest.</p>
<p><a href="http://www.infoworld.com/t/applications/gpl-author-google-must-share-code-288" rel="nofollow">http://www.infoworld.com/t/applications/gpl-author-google-must-share-code-288</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neill Turner</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-938</link>
		<dc:creator>Neill Turner</dc:creator>
		<pubDate>Mon, 26 Jul 2010 13:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-938</guid>
		<description>Well I don&#039;t really care about these low-level Cloud Standards. They will just become commodities. In fact the faster we can commoditize the Infrastructure as as Service (IaaS) layer the better. The real standards benefit will be in the Platform as a Service (PaaS) layer that will be built on top of the IaaS layer.
 -Think SQL database services that auto scale etc etc all you do is drop in your SQL.
 -Programming services where similarly you just drop in your code and it all runs. 
 -lots more.   
 These services will appear once the IaaS layer is commoditized and will have alot of business benefit. Currently there is too much variety in the IaaS clouds to build these. I expect a lot of effort going on in the IaaS layer will just go up the river when commoditization happens. I think Amazon understand this. They just create commodities as cheap, reliable, secure and scalable as possible. Everything else is irrelevant for Infrastructure as a Service.</description>
		<content:encoded><![CDATA[<p>Well I don&#8217;t really care about these low-level Cloud Standards. They will just become commodities. In fact the faster we can commoditize the Infrastructure as as Service (IaaS) layer the better. The real standards benefit will be in the Platform as a Service (PaaS) layer that will be built on top of the IaaS layer.<br />
 -Think SQL database services that auto scale etc etc all you do is drop in your SQL.<br />
 -Programming services where similarly you just drop in your code and it all runs.<br />
 -lots more.<br />
 These services will appear once the IaaS layer is commoditized and will have alot of business benefit. Currently there is too much variety in the IaaS clouds to build these. I expect a lot of effort going on in the IaaS layer will just go up the river when commoditization happens. I think Amazon understand this. They just create commodities as cheap, reliable, secure and scalable as possible. Everything else is irrelevant for Infrastructure as a Service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William (@vambenepe on Twitter)</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-937</link>
		<dc:creator>William (@vambenepe on Twitter)</dc:creator>
		<pubDate>Mon, 26 Jul 2010 07:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-937</guid>
		<description>Andrew, I think there is a good argument to be made that this is indeed a &quot;prisoner&#039;s dilemma&quot; type of situation if we assume that preventing premature standardization increases the size of the &quot;Cloud market&quot; pie, which I can easily believe.

The &quot;duel&quot; suggestion makes me realize that it may be for the better that we failed to find a mutually convenient time and place to meet when you were in town a week ago...</description>
		<content:encoded><![CDATA[<p>Andrew, I think there is a good argument to be made that this is indeed a &#8220;prisoner&#8217;s dilemma&#8221; type of situation if we assume that preventing premature standardization increases the size of the &#8220;Cloud market&#8221; pie, which I can easily believe.</p>
<p>The &#8220;duel&#8221; suggestion makes me realize that it may be for the better that we failed to find a mutually convenient time and place to meet when you were in town a week ago&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Clay Shafer</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-936</link>
		<dc:creator>Andrew Clay Shafer</dc:creator>
		<pubDate>Mon, 26 Jul 2010 06:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-936</guid>
		<description>I thought about this more, and I don&#039;t want to belabor the point too much, but I still think the standards situation is more appropriately labeled an nxn prisoners dilemma.

My rationale is that a &#039;tragedy of the commons&#039; is typified by the depletion of a shared common resource while the &#039;prisoners dilemma&#039; is typified by the choices made changing the dynamics and consequences of the choices of others.

Your standards for choosing metaphors is clearly flawed.

I&#039;m suggest we settle this the gentlemanly way all standards debates should be... a duel with pistols.</description>
		<content:encoded><![CDATA[<p>I thought about this more, and I don&#8217;t want to belabor the point too much, but I still think the standards situation is more appropriately labeled an nxn prisoners dilemma.</p>
<p>My rationale is that a &#8216;tragedy of the commons&#8217; is typified by the depletion of a shared common resource while the &#8216;prisoners dilemma&#8217; is typified by the choices made changing the dynamics and consequences of the choices of others.</p>
<p>Your standards for choosing metaphors is clearly flawed.</p>
<p>I&#8217;m suggest we settle this the gentlemanly way all standards debates should be&#8230; a duel with pistols.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayadeep Purushothaman</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-935</link>
		<dc:creator>Jayadeep Purushothaman</dc:creator>
		<pubDate>Mon, 26 Jul 2010 03:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-935</guid>
		<description>If you look at the Unix standardization efforts where every unix vendor was involved, the ultimate winner was Microsoft! And finally a de-facto standard evolved in the form of Linux! So I am not so sure about your thoughts here.</description>
		<content:encoded><![CDATA[<p>If you look at the Unix standardization efforts where every unix vendor was involved, the ultimate winner was Microsoft! And finally a de-facto standard evolved in the form of Linux! So I am not so sure about your thoughts here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Leach</title>
		<link>http://stage.vambenepe.com/archives/1549#comment-934</link>
		<dc:creator>Mike Leach</dc:creator>
		<pubDate>Mon, 26 Jul 2010 02:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/?p=1549#comment-934</guid>
		<description>If we use Nicholas Carr&#039;s metaphor that the cloud will evolve like electric utilities, then we only need the 120V at 60Hz equivalent as a standard.

I would argue we already have that with TCP/IP running on x86. Anything else built on top of that is fair game in the cloud.</description>
		<content:encoded><![CDATA[<p>If we use Nicholas Carr&#8217;s metaphor that the cloud will evolve like electric utilities, then we only need the 120V at 60Hz equivalent as a standard.</p>
<p>I would argue we already have that with TCP/IP running on x86. Anything else built on top of that is fair game in the cloud.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

