<?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: Organic vs. Non-Organic Open Source, Revisited</title>
	<atom:link href="http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/feed/" rel="self" type="application/rss+xml" />
	<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/</link>
	<description>Musings about Open Source, Linux, and Life by Theodore Tso</description>
	<lastBuildDate>Mon, 22 Feb 2010 22:39:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 451 CAOS Theory &#187; The last word (for now) on Open Core</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-1927</link>
		<dc:creator>451 CAOS Theory &#187; The last word (for now) on Open Core</dc:creator>
		<pubDate>Mon, 02 Mar 2009 17:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-1927</guid>
		<description>[...] last point takes us back to an old topic but one that I think will become integral this year and move beyond terminology to identifying how [...]</description>
		<content:encoded><![CDATA[<p>[...] last point takes us back to an old topic but one that I think will become integral this year and move beyond terminology to identifying how [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P2P Foundation &#187; Blog Archive &#187; Civil vs. corporate peer production</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-868</link>
		<dc:creator>P2P Foundation &#187; Blog Archive &#187; Civil vs. corporate peer production</dc:creator>
		<pubDate>Sat, 26 Jul 2008 04:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-868</guid>
		<description>[...] If we look at free software and open source as instances of peer production, I think we can conclude here that the most successful projects tend to become ‘corporatized’. This can happen in two different ways. The project can be supported by a wide variety of entities, or by just one. It would seem that in the former case, such as Linux, no single company dominates the process, and some commentators have called this ‘organic’ open source. [...]</description>
		<content:encoded><![CDATA[<p>[...] If we look at free software and open source as instances of peer production, I think we can conclude here that the most successful projects tend to become ‘corporatized’. This can happen in two different ways. The project can be supported by a wide variety of entities, or by just one. It would seem that in the former case, such as Linux, no single company dominates the process, and some commentators have called this ‘organic’ open source. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 451 CAOS Theory &#187; The vocabulary of open source development models</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-820</link>
		<dc:creator>451 CAOS Theory &#187; The vocabulary of open source development models</dc:creator>
		<pubDate>Thu, 26 Jun 2008 11:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-820</guid>
		<description>[...] For some background on it, and an explanation about why it matters, see Ted Ts&#8217;o&#8217;s post from [...]</description>
		<content:encoded><![CDATA[<p>[...] For some background on it, and an explanation about why it matters, see Ted Ts&#8217;o&#8217;s post from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cozminsky</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-758</link>
		<dc:creator>Cozminsky</dc:creator>
		<pubDate>Fri, 23 May 2008 01:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-758</guid>
		<description>I think I have an even more accurate description. How about dependent or independent?</description>
		<content:encoded><![CDATA[<p>I think I have an even more accurate description. How about dependent or independent?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Dixon</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-745</link>
		<dc:creator>James Dixon</dc:creator>
		<pubDate>Wed, 21 May 2008 20:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-745</guid>
		<description>I think the distinction being discussed here is of interest mainly to theorists. If a piece of open source software is useful to me I use it and contribute anything that comes from my usage of it. I don&#039;t care if it was created organically or not. Really why would I? Given a choice of two packages I&#039;ll take the one that best fits my needs. If they are identical in terms of functionality and fit for my purpose (a rare case) I&#039;ll probably go with the one that seems to treat its non-development contributors the best as that will probably be the experience I will have. Again I still don&#039;t care about the organic question. 

Some of the views above are heavily developer-centric. In my experience the contributions of the users are very important: use cases, finding bugs (often much harder than fixing them), platform testing, scalability testing, comparisons with alternatives, localizations etc. In fact these contributions outweigh (in terms of # of contributions) the contributions of the coders. The fact is you can do the coding behind closed doors (most small open source projects do it this way anyway) or in the open, but you CANNOT harden the software behind closed doors. You have to let the software out early and often to find out the functional and non-functional defects in the design and implementation. Sure there are a few high-profile examples where a distributed group of developers working to an existing spec (HTTP, Servlet or Unix kernel) have created things of great utility. If those developers were the only ones to ever use those creations open source would still be firmly in the hobby category.

I don&#039;t have much of an opinion on the terminology. When you look at many &#039;organic&#039; projects what you are dealing with in reality is a &#039;committee&#039; of core-developers or administrators that are the gatekeepers. This committee decides amongst itself what direction the project goes in, what contributions to accept, and how to prioritize the backlog of features. In some cases that committee does not pay attention to the needs of its community. 

Maybe &#039;Managed&#039; or &#039;Directed&#039; is a better term than &#039;Non-Organic&#039;. From the perspective of a CIO trying to manage their company&#039;s usage of open source &#039;organic&#039; is not necessarily a good thing, whereas &#039;managed&#039; maybe sounds a little more comforting. 

James Dixon</description>
		<content:encoded><![CDATA[<p>I think the distinction being discussed here is of interest mainly to theorists. If a piece of open source software is useful to me I use it and contribute anything that comes from my usage of it. I don&#8217;t care if it was created organically or not. Really why would I? Given a choice of two packages I&#8217;ll take the one that best fits my needs. If they are identical in terms of functionality and fit for my purpose (a rare case) I&#8217;ll probably go with the one that seems to treat its non-development contributors the best as that will probably be the experience I will have. Again I still don&#8217;t care about the organic question. </p>
<p>Some of the views above are heavily developer-centric. In my experience the contributions of the users are very important: use cases, finding bugs (often much harder than fixing them), platform testing, scalability testing, comparisons with alternatives, localizations etc. In fact these contributions outweigh (in terms of # of contributions) the contributions of the coders. The fact is you can do the coding behind closed doors (most small open source projects do it this way anyway) or in the open, but you CANNOT harden the software behind closed doors. You have to let the software out early and often to find out the functional and non-functional defects in the design and implementation. Sure there are a few high-profile examples where a distributed group of developers working to an existing spec (HTTP, Servlet or Unix kernel) have created things of great utility. If those developers were the only ones to ever use those creations open source would still be firmly in the hobby category.</p>
<p>I don&#8217;t have much of an opinion on the terminology. When you look at many &#8216;organic&#8217; projects what you are dealing with in reality is a &#8216;committee&#8217; of core-developers or administrators that are the gatekeepers. This committee decides amongst itself what direction the project goes in, what contributions to accept, and how to prioritize the backlog of features. In some cases that committee does not pay attention to the needs of its community. </p>
<p>Maybe &#8216;Managed&#8217; or &#8216;Directed&#8217; is a better term than &#8216;Non-Organic&#8217;. From the perspective of a CIO trying to manage their company&#8217;s usage of open source &#8216;organic&#8217; is not necessarily a good thing, whereas &#8216;managed&#8217; maybe sounds a little more comforting. </p>
<p>James Dixon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: (Commercial) Open Source Armageddon &#124; Boldly Open</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-737</link>
		<dc:creator>(Commercial) Open Source Armageddon &#124; Boldly Open</dc:creator>
		<pubDate>Tue, 20 May 2008 22:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-737</guid>
		<description>[...] just too much bait out there to shut up, so I urge you to have a look at the whole stir about organic Open Source, vendor openness, the role of communities and, generally speaking, Open Source sustainability as a [...]</description>
		<content:encoded><![CDATA[<p>[...] just too much bait out there to shut up, so I urge you to have a look at the whole stir about organic Open Source, vendor openness, the role of communities and, generally speaking, Open Source sustainability as a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Have you ever kissed a girl? &#187; Snoopy&#8217;s Home</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-522</link>
		<dc:creator>Have you ever kissed a girl? &#187; Snoopy&#8217;s Home</dc:creator>
		<pubDate>Sun, 04 May 2008 01:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-522</guid>
		<description>[...] have to admit that when I first saw this quote from Ted&#8217;s blog on Organic vs. Non-organic Open Source, I&#8217;m quite confused (another GRE reading comprehension?). So I follow the link and read the [...]</description>
		<content:encoded><![CDATA[<p>[...] have to admit that when I first saw this quote from Ted&#8217;s blog on Organic vs. Non-organic Open Source, I&#8217;m quite confused (another GRE reading comprehension?). So I follow the link and read the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Stansell</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-488</link>
		<dc:creator>James Stansell</dc:creator>
		<pubDate>Wed, 30 Apr 2008 16:22:48 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-488</guid>
		<description>How about &quot;Marketplace&quot; vs &quot;Castle&quot;, reminiscent of Eric Raymond&#039;s years-old essay?</description>
		<content:encoded><![CDATA[<p>How about &#8220;Marketplace&#8221; vs &#8220;Castle&#8221;, reminiscent of Eric Raymond&#8217;s years-old essay?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cozminsky</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-467</link>
		<dc:creator>Cozminsky</dc:creator>
		<pubDate>Mon, 28 Apr 2008 04:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-467</guid>
		<description>How about communal vs. centrist.</description>
		<content:encoded><![CDATA[<p>How about communal vs. centrist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Parker</title>
		<link>http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/comment-page-1/#comment-459</link>
		<dc:creator>Steve Parker</dc:creator>
		<pubDate>Sun, 27 Apr 2008 23:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://thunk.org/tytso/blog/2008/04/26/organic-vs-non-organic-open-source-revisited/#comment-459</guid>
		<description>Thanks for your detailed response on my blog, Ted. Good points, well made, of course.

Is it more appropriate, then, to see OpenSolaris as a fix to the previous closed-source situation? 

Although &quot;in truth, Sun had already made the Source Code for Solaris available for a nominal fee years before&quot;, the principle for the typical customer (or sysadmin) that I met, was that the code (and some of the relevant bug reports, etc) were hidden away as Sun&#039;s &quot;secret sauce&quot; and not for commoners to access.

If we plot a graph of open-source awareness, with Linux, *BSD towards the far left, and Microsoft, Oracle, etc on the far right, then are Sun, who started out quite far to the left and later moved towards the right, now moving back towards the left again?

Is that a more useful model to view the current climate, perhaps?</description>
		<content:encoded><![CDATA[<p>Thanks for your detailed response on my blog, Ted. Good points, well made, of course.</p>
<p>Is it more appropriate, then, to see OpenSolaris as a fix to the previous closed-source situation? </p>
<p>Although &#8220;in truth, Sun had already made the Source Code for Solaris available for a nominal fee years before&#8221;, the principle for the typical customer (or sysadmin) that I met, was that the code (and some of the relevant bug reports, etc) were hidden away as Sun&#8217;s &#8220;secret sauce&#8221; and not for commoners to access.</p>
<p>If we plot a graph of open-source awareness, with Linux, *BSD towards the far left, and Microsoft, Oracle, etc on the far right, then are Sun, who started out quite far to the left and later moved towards the right, now moving back towards the left again?</p>
<p>Is that a more useful model to view the current climate, perhaps?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
