<?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: Should commercial open source vendors &#8220;own&#8221; an open source community?</title>
	<atom:link href="http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/</link>
	<description>Open Source Governance, Scanning, Support, and Cloud</description>
	<lastBuildDate>Wed, 01 Feb 2012 20:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Could Too Much Commercial Control over Open Source Projects Backfire? &#124; OpenLogic Blogs</title>
		<link>http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/comment-page-1/#comment-139714</link>
		<dc:creator>Could Too Much Commercial Control over Open Source Projects Backfire? &#124; OpenLogic Blogs</dc:creator>
		<pubDate>Wed, 24 Dec 2008 18:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/#comment-139714</guid>
		<description>[...] the sometimes negative impact that commercial vendors can have on open source projects.&#160; (See Should commercial open source vendors &quot;own&quot; an open source community?)&#160; Some business models and business practices of open source vendors&#160;(trying to control [...]</description>
		<content:encoded><![CDATA[<p>[...] the sometimes negative impact that commercial vendors can have on open source projects.&nbsp; (See Should commercial open source vendors &quot;own&quot; an open source community?)&nbsp; Some business models and business practices of open source vendors&nbsp;(trying to control [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Repenning</title>
		<link>http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/comment-page-1/#comment-121761</link>
		<dc:creator>Jack Repenning</dc:creator>
		<pubDate>Thu, 11 Sep 2008 23:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.openlogic.com/blogs/2008/09/should-commercial-open-source-vendors-own-an-open-source-community/#comment-121761</guid>
		<description>Don&#039;t think I, personally, have encountered quite that. I&#039;ve seen some other nuances, some more, some less evil:

I&#039;ve seen companies who harvest their communities, perhaps providing money, machines, free or meeting space, but taking the product, commercializing it ... and then giving back Absolutely. Nothing. At. All. This is a quick and certain way to the very deepest circle of the hacker inferno, in case anyone was looking for a short cut.

I&#039;ve seen companies that sponsor a community (to some extent or other), including a lot of good citizenship with fixes and what-not, and then also add significant features only available to paying customers. This seems like a harder call: most people will acknowledge a company&#039;s right to find some way or other to make a buck, that being not only the whole point of a company, but also the primary source of the &quot;support&quot; they&#039;re giving the community. But if the reserved feature is too central to the product, like an unusual save format or a fancy print dialog, it&#039;s still a bit unsavory.

And then, I&#039;ve seen companies that sponsor a community with full and commendable citizenship, supporting in all the ways mentioned above, contributing back time and patches and even major features, building the strongest product the open-source community could wish, and also building related but independent larger, commercial products on top. Underlying licenses permitting, this all seems to me entirely reasonable.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t think I, personally, have encountered quite that. I&#8217;ve seen some other nuances, some more, some less evil:</p>
<p>I&#8217;ve seen companies who harvest their communities, perhaps providing money, machines, free or meeting space, but taking the product, commercializing it &#8230; and then giving back Absolutely. Nothing. At. All. This is a quick and certain way to the very deepest circle of the hacker inferno, in case anyone was looking for a short cut.</p>
<p>I&#8217;ve seen companies that sponsor a community (to some extent or other), including a lot of good citizenship with fixes and what-not, and then also add significant features only available to paying customers. This seems like a harder call: most people will acknowledge a company&#8217;s right to find some way or other to make a buck, that being not only the whole point of a company, but also the primary source of the &#8220;support&#8221; they&#8217;re giving the community. But if the reserved feature is too central to the product, like an unusual save format or a fancy print dialog, it&#8217;s still a bit unsavory.</p>
<p>And then, I&#8217;ve seen companies that sponsor a community with full and commendable citizenship, supporting in all the ways mentioned above, contributing back time and patches and even major features, building the strongest product the open-source community could wish, and also building related but independent larger, commercial products on top. Underlying licenses permitting, this all seems to me entirely reasonable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

