<?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 problem with dual licensing</title>
	<atom:link href="http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/</link>
	<description>A blog for the enterprise open source community</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: 451 CAOS Theory &#187; On open source business strategies (again)</title>
		<link>http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/comment-page-1/#comment-371954</link>
		<dc:creator>451 CAOS Theory &#187; On open source business strategies (again)</dc:creator>
		<pubDate>Wed, 25 Feb 2009 09:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/?p=988#comment-371954</guid>
		<description>[...] I do believe that the Open-Core vendors have the best intentions, and the model does effectively separate community users from commercial customers enabling vendors to focus on the needs of each. However, it also brings its own problems, such as balancing what functionality will be available in the enterprise or community versions, and means that the vendor does not enjoy the full benefit of open source lower development and sales costs. And it can be confusing. [...]</description>
		<content:encoded><![CDATA[<p>[...] I do believe that the Open-Core vendors have the best intentions, and the model does effectively separate community users from commercial customers enabling vendors to focus on the needs of each. However, it also brings its own problems, such as balancing what functionality will be available in the enterprise or community versions, and means that the vendor does not enjoy the full benefit of open source lower development and sales costs. And it can be confusing. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 451 CAOS Theory &#187; Commercial open source business strategies in 2009 and beyond</title>
		<link>http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/comment-page-1/#comment-346297</link>
		<dc:creator>451 CAOS Theory &#187; Commercial open source business strategies in 2009 and beyond</dc:creator>
		<pubDate>Tue, 06 Jan 2009 14:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/?p=988#comment-346297</guid>
		<description>[...] costs and wider testing enabled by open source development while Open-Core is also potentially confusing to both the vendor and its [...]</description>
		<content:encoded><![CDATA[<p>[...] costs and wider testing enabled by open source development while Open-Core is also potentially confusing to both the vendor and its [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Schestowitz</title>
		<link>http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/comment-page-1/#comment-325849</link>
		<dc:creator>Roy Schestowitz</dc:creator>
		<pubDate>Wed, 26 Nov 2008 01:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/?p=988#comment-325849</guid>
		<description>I think it&#039;s &#039;diluting&#039; the things too much. I talked to MySQL&#039;s CEO about this at the time because it&#039;s calling for characterization of F/OSS as &quot;freeware&quot; or &quot;trial-version-ware.&quot; it&#039;s not good for anyone.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s &#8216;diluting&#8217; the things too much. I talked to MySQL&#8217;s CEO about this at the time because it&#8217;s calling for characterization of F/OSS as &#8220;freeware&#8221; or &#8220;trial-version-ware.&#8221; it&#8217;s not good for anyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Asay</title>
		<link>http://blogs.the451group.com/opensource/2008/11/24/the-problem-with-dual-licensing/comment-page-1/#comment-324518</link>
		<dc:creator>Matt Asay</dc:creator>
		<pubDate>Mon, 24 Nov 2008 17:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/?p=988#comment-324518</guid>
		<description>Thanks for the thoughtful write-up, Matt.  I agree 100%.  I&#039;m increasingly concerned that in our attempt to keep to the &quot;100% open source&quot; faith, we&#039;ve ended up muddying the water.  I really am starting to believe that adding proprietary components is the best, cleanest way to preserve open source for our customers and other community members.  Jerico&#039;s comments only highlight the implicit problems that dual licensing creates, as you also point out.</description>
		<content:encoded><![CDATA[<p>Thanks for the thoughtful write-up, Matt.  I agree 100%.  I&#8217;m increasingly concerned that in our attempt to keep to the &#8220;100% open source&#8221; faith, we&#8217;ve ended up muddying the water.  I really am starting to believe that adding proprietary components is the best, cleanest way to preserve open source for our customers and other community members.  Jerico&#8217;s comments only highlight the implicit problems that dual licensing creates, as you also point out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

