<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How Open Source Is Your Open Source?</title>
	<atom:link href="http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/</link>
	<description>It's Not Just About Llamas</description>
	<lastBuildDate>Tue, 24 Jan 2012 15:14:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Red Hat Magazine &#124; Twelve success metrics to improve open&#160;source-ness</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-593</link>
		<dc:creator><![CDATA[Red Hat Magazine &#124; Twelve success metrics to improve open&#160;source-ness]]></dc:creator>
		<pubDate>Thu, 02 Apr 2009 20:47:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-593</guid>
		<description><![CDATA[[...] his post How Open Source Is Your Open Source?, Michael DeHaan covers twelve components that are needed for a company to successfully start and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] his post How Open Source Is Your Open Source?, Michael DeHaan covers twelve components that are needed for a company to successfully start and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Truth Happens &#124; Care and feeding of an open source&#160;project</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-252</link>
		<dc:creator><![CDATA[Truth Happens &#124; Care and feeding of an open source&#160;project]]></dc:creator>
		<pubDate>Fri, 30 Jan 2009 14:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-252</guid>
		<description><![CDATA[[...] via michaeldehaan.net &#124; How Open Source Is Your Open Source?. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] via michaeldehaan.net | How Open Source Is Your Open Source?. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael.dehaan</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-253</link>
		<dc:creator><![CDATA[michael.dehaan]]></dc:creator>
		<pubDate>Sun, 25 Jan 2009 14:16:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-253</guid>
		<description><![CDATA[On, I don&#039;t believe I was ever suggesting a clear seperation, if anything I am suggesting those boundaries need to be broken down; things must be focused outward always.

For instance, lots of projects have a very narrow cabal working on them, and do not seek to gather the opinions of their users, or convert users into contributers.  This is the key to getting them to go to the next level.   To do so is not sufficiently Open.

Ultimately your users are your future developers; that seems pretty natural to me that we (as project leads and developers) listen to them and make things as inclusive as possible.  It ultimately depends on what you deem &quot;natural&quot; though, if this is what has already developed without your investment, I suppose that&#039;s ok -- but I think it&#039;s always better when developers are interested in the communities around their products.

To me, the code is never the most interesting thing.]]></description>
		<content:encoded><![CDATA[<p>On, I don&#8217;t believe I was ever suggesting a clear seperation, if anything I am suggesting those boundaries need to be broken down; things must be focused outward always.</p>
<p>For instance, lots of projects have a very narrow cabal working on them, and do not seek to gather the opinions of their users, or convert users into contributers.  This is the key to getting them to go to the next level.   To do so is not sufficiently Open.</p>
<p>Ultimately your users are your future developers; that seems pretty natural to me that we (as project leads and developers) listen to them and make things as inclusive as possible.  It ultimately depends on what you deem &#8220;natural&#8221; though, if this is what has already developed without your investment, I suppose that&#8217;s ok &#8212; but I think it&#8217;s always better when developers are interested in the communities around their products.</p>
<p>To me, the code is never the most interesting thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On Elpeleg</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-251</link>
		<dc:creator><![CDATA[On Elpeleg]]></dc:creator>
		<pubDate>Sun, 25 Jan 2009 11:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-251</guid>
		<description><![CDATA[Hi and thanks for the article.

As a developer in an open source, content management system, I fully agree that one needs to make a clear separation between open source developers and social communities.

However I for one think that the code developers community should be the main priority and that one should let the social community follow as natural as possible.

On Elpeleg
WebAPP, Open Source Perl CMS]]></description>
		<content:encoded><![CDATA[<p>Hi and thanks for the article.</p>
<p>As a developer in an open source, content management system, I fully agree that one needs to make a clear separation between open source developers and social communities.</p>
<p>However I for one think that the code developers community should be the main priority and that one should let the social community follow as natural as possible.</p>
<p>On Elpeleg<br />
WebAPP, Open Source Perl CMS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Hat Magazine &#124; Twelve success metrics to improve open source-ness</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-258</link>
		<dc:creator><![CDATA[Red Hat Magazine &#124; Twelve success metrics to improve open source-ness]]></dc:creator>
		<pubDate>Fri, 15 Aug 2008 15:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-258</guid>
		<description><![CDATA[[...] his post How Open Source Is Your Open Source?, Michael DeHaan covers twelve components that are needed for a company to successfully start and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] his post How Open Source Is Your Open Source?, Michael DeHaan covers twelve components that are needed for a company to successfully start and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Open Source Is Your Open Source? &#124; OSS Spyglass</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-257</link>
		<dc:creator><![CDATA[How Open Source Is Your Open Source? &#124; OSS Spyglass]]></dc:creator>
		<pubDate>Fri, 01 Aug 2008 19:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-257</guid>
		<description><![CDATA[[...] michaeldehaan.net &#124; How Open Source Is Your Open Source?  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] michaeldehaan.net | How Open Source Is Your Open Source?  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 451 CAOS Theory &#187; Judging open source business models</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-256</link>
		<dc:creator><![CDATA[451 CAOS Theory &#187; Judging open source business models]]></dc:creator>
		<pubDate>Fri, 01 Aug 2008 16:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-256</guid>
		<description><![CDATA[[...] was responding to this post from Michael DeHaan that defines a list of the principles he feels vendors should follow if they [...]]]></description>
		<content:encoded><![CDATA[<p>[...] was responding to this post from Michael DeHaan that defines a list of the principles he feels vendors should follow if they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew C. Oliver</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-255</link>
		<dc:creator><![CDATA[Andrew C. Oliver]]></dc:creator>
		<pubDate>Fri, 01 Aug 2008 04:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-255</guid>
		<description><![CDATA[Thanks for the great post!]]></description>
		<content:encoded><![CDATA[<p>Thanks for the great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Stahnke</title>
		<link>http://michaeldehaan.net/2008/07/29/how-open-source-is-your-open-source/#comment-254</link>
		<dc:creator><![CDATA[Michael Stahnke]]></dc:creator>
		<pubDate>Wed, 30 Jul 2008 03:11:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaeldehaan.net/?p=674#comment-254</guid>
		<description><![CDATA[You have some of the best blogging material on planet.  I really enjoy most of your stuff quite a lot.  It&#039;s posts like this that help show the thought and care you put into the community.  I really like this list and will be sharing it with my teams internally at work.  My first goal is to get separate teams within my company able to trust/share before even thinking of open sourcing, but still, it&#039;s a great post.]]></description>
		<content:encoded><![CDATA[<p>You have some of the best blogging material on planet.  I really enjoy most of your stuff quite a lot.  It&#8217;s posts like this that help show the thought and care you put into the community.  I really like this list and will be sharing it with my teams internally at work.  My first goal is to get separate teams within my company able to trust/share before even thinking of open sourcing, but still, it&#8217;s a great post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

