<?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: Free Software, Private Property</title>
	<atom:link href="http://www.the-source.com/2010/02/free-software-private-property/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.the-source.com/2010/02/free-software-private-property/</link>
	<description>Free and Open Source Software News and Opinion</description>
	<lastBuildDate>Tue, 22 Nov 2011 12:44:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Joshua</title>
		<link>http://www.the-source.com/2010/02/free-software-private-property/comment-page-1/#comment-291</link>
		<dc:creator>Joshua</dc:creator>
		<pubDate>Fri, 26 Feb 2010 14:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.the-source.com/?p=503#comment-291</guid>
		<description>The funny thing about your first example, an open source project where contributions from &quot;outside the fold&quot; are rejected has a couple of really good real world examples.

One is the historical example of Richard Stallmans own emacs. Another is the wine project (which is notoriously proprietary about stuff making it into the official tree).

In both of these cases the result was forking. The Linux kernel is forked ALL THE TIME by folks with a specific interest that doesn&#039;t coincide with the interests of the powers that be for that project.

This phenomenon is not unique to open source.

The beauty is that with proprietary projects the &quot;fork&quot; must either start from scratch, reverse engineer the original, or steal it (not legal, but not uncommon).  Open source makes it easy and legal to do the same things, but conversely amplifies the positive effects of cooperating, and NOT forking.

And every once in a while, the folks behind the fork really do have a better idea how to proceed.  See the example of Sodipodi -&gt; Inkscape.</description>
		<content:encoded><![CDATA[<p>The funny thing about your first example, an open source project where contributions from &#8220;outside the fold&#8221; are rejected has a couple of really good real world examples.</p>
<p>One is the historical example of Richard Stallmans own emacs. Another is the wine project (which is notoriously proprietary about stuff making it into the official tree).</p>
<p>In both of these cases the result was forking. The Linux kernel is forked ALL THE TIME by folks with a specific interest that doesn&#8217;t coincide with the interests of the powers that be for that project.</p>
<p>This phenomenon is not unique to open source.</p>
<p>The beauty is that with proprietary projects the &#8220;fork&#8221; must either start from scratch, reverse engineer the original, or steal it (not legal, but not uncommon).  Open source makes it easy and legal to do the same things, but conversely amplifies the positive effects of cooperating, and NOT forking.</p>
<p>And every once in a while, the folks behind the fork really do have a better idea how to proceed.  See the example of Sodipodi -&gt; Inkscape.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

