<?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: Community analysis as risk management</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2009/05/18/community-analysis-as-risk-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2009/05/18/community-analysis-as-risk-management/</link>
	<description>Dave Neary's view of the world</description>
	<lastBuildDate>Mon, 23 Nov 2009 14:50:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Donnie Berkholz</title>
		<link>http://blogs.gnome.org/bolsh/2009/05/18/community-analysis-as-risk-management/comment-page-1/#comment-2122</link>
		<dc:creator>Donnie Berkholz</dc:creator>
		<pubDate>Fri, 22 May 2009 00:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=921#comment-2122</guid>
		<description>To add onto that, you can then decide how much risk you want to take by just dropping the lowest-probability events off your list till you&#039;ve dropped the bottom 1%, 5%, or however much you want to assume won&#039;t happen. Since low-probability events are often also high-cost, this is one way of deciding how much money to save.</description>
		<content:encoded><![CDATA[<p>To add onto that, you can then decide how much risk you want to take by just dropping the lowest-probability events off your list till you&#8217;ve dropped the bottom 1%, 5%, or however much you want to assume won&#8217;t happen. Since low-probability events are often also high-cost, this is one way of deciding how much money to save.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donnie Berkholz</title>
		<link>http://blogs.gnome.org/bolsh/2009/05/18/community-analysis-as-risk-management/comment-page-1/#comment-2121</link>
		<dc:creator>Donnie Berkholz</dc:creator>
		<pubDate>Fri, 22 May 2009 00:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=921#comment-2121</guid>
		<description>Looking at the worst case is the wrong approach, you should be looking at the expectation value. Sum( (Chance of thing happening)*(Cost of thing happening) ) across all things. Same technique you can use to figure out how much money you lose by buying a lottery ticket.</description>
		<content:encoded><![CDATA[<p>Looking at the worst case is the wrong approach, you should be looking at the expectation value. Sum( (Chance of thing happening)*(Cost of thing happening) ) across all things. Same technique you can use to figure out how much money you lose by buying a lottery ticket.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stormy</title>
		<link>http://blogs.gnome.org/bolsh/2009/05/18/community-analysis-as-risk-management/comment-page-1/#comment-2114</link>
		<dc:creator>stormy</dc:creator>
		<pubDate>Mon, 18 May 2009 23:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=921#comment-2114</guid>
		<description>I totally agree that companies are very concerned with measuring the risk of open source. I know one company that has done a study of how much it would cost them if they got sued for open source (win or lose) and keeps that much money around, just in case.

OpenLogic has an open source evaluation process that includes measuring community. They measure number of members, number of open bugs, how long bugs are open, # of mails on the mailing list, etc.</description>
		<content:encoded><![CDATA[<p>I totally agree that companies are very concerned with measuring the risk of open source. I know one company that has done a study of how much it would cost them if they got sued for open source (win or lose) and keeps that much money around, just in case.</p>
<p>OpenLogic has an open source evaluation process that includes measuring community. They measure number of members, number of open bugs, how long bugs are open, # of mails on the mailing list, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
