<?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: Rotten to the (Open) Core?</title>
	<atom:link href="http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/</link>
	<description>Free software community consultancy</description>
	<lastBuildDate>Fri, 18 Mar 2011 03:33:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.2</generator>
	<item>
		<title>By: Henrik Ingo</title>
		<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-125</link>
		<dc:creator>Henrik Ingo</dc:creator>
		<pubDate>Fri, 23 Jul 2010 20:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-125</guid>
		<description>Ok, reading these comments and your followup post, I think I may understand what you&#039;re getting at.

In your view, someone putting out open source software which is incomplete, crippled and only a demo, will make open source look bad and this is something to detest. This is of course true to some extent. But what about someone that publishes bad open source software just because he is a bad developer, without having an open core business model?

Or to look at your argument another way, if someone publishes software you can use without paying and you find it useful, then this is nice and ok, but if someone witholds features you&#039;d like to get for free, then that&#039;s not nice? 

Btw, what do you think about something like Red Hat Enterprise Linux? You don&#039;t get it for free, but it is 100% open source, no open core there.

My point is that open core is bad because the proponents try to assert that it is okay to add in a little proprietary code and still pretend you&#039;re open source. Which part of the software is or isn&#039;t useful, or how independent it is architecturally, is a completely different discussion and open core is not defined like that. The harm done to open source is that people are trying to include as &quot;open source&quot; something which doesn&#039;t meet the open source definition.

And the motivation for that argument mostly lies in the belief that open source has tremendous value in itself. Even crappy software released as open source has the potential of becoming better (like Linux v0.2), and in any case you have total freedom to control your destiny with it. With proprietary software you don&#039;t have that, and this is irrespective of how many nice and useful features a company gives you for free.

To put it another way, there are proprietary software companies like Microsoft and Oracle and Apple that produce really nice and useful proprietary software, a lot of which you can even use for free. This can be considered nice in many ways, it is not crippleware in many cases (Internet Explorer), etc. It just isn&#039;t open source. (And they are not claiming it to be.)</description>
		<content:encoded><![CDATA[<p>Ok, reading these comments and your followup post, I think I may understand what you&#8217;re getting at.</p>
<p>In your view, someone putting out open source software which is incomplete, crippled and only a demo, will make open source look bad and this is something to detest. This is of course true to some extent. But what about someone that publishes bad open source software just because he is a bad developer, without having an open core business model?</p>
<p>Or to look at your argument another way, if someone publishes software you can use without paying and you find it useful, then this is nice and ok, but if someone witholds features you&#8217;d like to get for free, then that&#8217;s not nice? </p>
<p>Btw, what do you think about something like Red Hat Enterprise Linux? You don&#8217;t get it for free, but it is 100% open source, no open core there.</p>
<p>My point is that open core is bad because the proponents try to assert that it is okay to add in a little proprietary code and still pretend you&#8217;re open source. Which part of the software is or isn&#8217;t useful, or how independent it is architecturally, is a completely different discussion and open core is not defined like that. The harm done to open source is that people are trying to include as &#8220;open source&#8221; something which doesn&#8217;t meet the open source definition.</p>
<p>And the motivation for that argument mostly lies in the belief that open source has tremendous value in itself. Even crappy software released as open source has the potential of becoming better (like Linux v0.2), and in any case you have total freedom to control your destiny with it. With proprietary software you don&#8217;t have that, and this is irrespective of how many nice and useful features a company gives you for free.</p>
<p>To put it another way, there are proprietary software companies like Microsoft and Oracle and Apple that produce really nice and useful proprietary software, a lot of which you can even use for free. This can be considered nice in many ways, it is not crippleware in many cases (Internet Explorer), etc. It just isn&#8217;t open source. (And they are not claiming it to be.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moved by Freedom &#8211; Powered by Standards &#187; Links for the end of July</title>
		<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-121</link>
		<dc:creator>Moved by Freedom &#8211; Powered by Standards &#187; Links for the end of July</dc:creator>
		<pubDate>Thu, 22 Jul 2010 15:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-121</guid>
		<description>[...] &#8220;Rotten to the Open Core&#8221;: a great post by Dave Neary setting the record straight on this insipid debate. And for what it&#8217;s worth, let&#8217;s remember Free Software means something and is not just nice and fancy brand to be used by everyone. [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Rotten to the Open Core&#8221;: a great post by Dave Neary setting the record straight on this insipid debate. And for what it&#8217;s worth, let&#8217;s remember Free Software means something and is not just nice and fancy brand to be used by everyone. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neary Consulting &#187; Open Core is a bad word</title>
		<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-120</link>
		<dc:creator>Neary Consulting &#187; Open Core is a bad word</dc:creator>
		<pubDate>Thu, 22 Jul 2010 09:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-120</guid>
		<description>[...] Rotten to the (Open) Core? [...]</description>
		<content:encoded><![CDATA[<p>[...] Rotten to the (Open) Core? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-116</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 20 Jul 2010 06:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-116</guid>
		<description>Looks like I need to do a small revision... &quot;my idea that extensions lead to lock-in&quot; is exactly the opposite of my idea. I am arguing that standalone utilities or plug-ins which are available commercially does not constitute &quot;Open Core&quot;, but a substandard free project which is used just as a &quot;teaser&quot; for the fully-featured commercial project *is* &quot;Open Core&quot;. It&#039;s &quot;Open Source Shareware&quot;.

And I don&#039;t make any value judgement on whether this is good or bad. As someone said to me: &quot;Priority one: Ensure you&#039;re giving value&quot; - and I agree with that. This is not a customer value argument, it is a fight over the value of the Open Source brand (which *is* damaged when people start to associate &quot;Open Source&quot; with &quot;substandard shareware&quot;.

Dave.</description>
		<content:encoded><![CDATA[<p>Looks like I need to do a small revision&#8230; &#8220;my idea that extensions lead to lock-in&#8221; is exactly the opposite of my idea. I am arguing that standalone utilities or plug-ins which are available commercially does not constitute &#8220;Open Core&#8221;, but a substandard free project which is used just as a &#8220;teaser&#8221; for the fully-featured commercial project *is* &#8220;Open Core&#8221;. It&#8217;s &#8220;Open Source Shareware&#8221;.</p>
<p>And I don&#8217;t make any value judgement on whether this is good or bad. As someone said to me: &#8220;Priority one: Ensure you&#8217;re giving value&#8221; &#8211; and I agree with that. This is not a customer value argument, it is a fight over the value of the Open Source brand (which *is* damaged when people start to associate &#8220;Open Source&#8221; with &#8220;substandard shareware&#8221;.</p>
<p>Dave.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jrep</title>
		<link>http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-115</link>
		<dc:creator>jrep</dc:creator>
		<pubDate>Mon, 19 Jul 2010 19:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.neary-consulting.com/index.php/2010/07/19/rotten-to-the-open-core/#comment-115</guid>
		<description>I don&#039;t think everyone takes the term &quot;open core&quot; to necessarily imply that the commercial version has proprietary extensions. In particular, your idea that extensions lead to lock-in seems a bit at odds with your acknowledgement that the open part is a full, useful product.

If the open stuff is insufficient, that would be another matter. Particularly vile, we&#039;ve seen situations where the open stuff was crippled and limping, and not really useful to anyone, yet the commercial stuff had proprietary solutions, fixes, and extensions to make it really useful. That, I think, is totally &quot;faux-pen.&quot; Where a company harvests whatever contributions the community can manage, without giving back what they create to complete, this is &quot;faux.&quot; Poetically, it generally kills the community as well, so we have at least the revenge that the harvest dries up (geese and golden eggs might be the better metaphor).</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think everyone takes the term &#8220;open core&#8221; to necessarily imply that the commercial version has proprietary extensions. In particular, your idea that extensions lead to lock-in seems a bit at odds with your acknowledgement that the open part is a full, useful product.</p>
<p>If the open stuff is insufficient, that would be another matter. Particularly vile, we&#8217;ve seen situations where the open stuff was crippled and limping, and not really useful to anyone, yet the commercial stuff had proprietary solutions, fixes, and extensions to make it really useful. That, I think, is totally &#8220;faux-pen.&#8221; Where a company harvests whatever contributions the community can manage, without giving back what they create to complete, this is &#8220;faux.&#8221; Poetically, it generally kills the community as well, so we have at least the revenge that the harvest dries up (geese and golden eggs might be the better metaphor).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

