<?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: Links</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2007/04/14/links/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2007/04/14/links/</link>
	<description>Dave Neary's view of the world</description>
	<lastBuildDate>Sun, 11 Dec 2011 14:17:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ron Fredericks</title>
		<link>http://blogs.gnome.org/bolsh/2007/04/14/links/comment-page-1/#comment-585</link>
		<dc:creator>Ron Fredericks</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/04/14/links/#comment-585</guid>
		<description>I can understand Ari&#039;s comments. But I think there is room for many types of open-source communities:&lt;p/&gt;1) Harvest existing open-source software like Linux, where a few key individuals previously set in motion a great product and a great project model for the rest of us to use – and maybe use a corporate web site to manage the “harvesting” process,&lt;p/&gt;2) Contribute more open-source software to an already great product, like Linux, that only gets better as more contribute - thanks to the founding individuals, their project management methods, and the accepted web portals that act as their “watering holes”,&lt;p/&gt;3) Or be the new visionary with open-source project management methods that the rest of us can follow while delivering an entirely new open-source solution...&lt;p/&gt;Recently I discovered one of the early (first?) open-source community projects from 1981 that was successfully deployed on top of a closed operating system for a mobile embedded device. Perhaps your readers would be interested in learning about the similarities and differences demonstrated by these 100 engineers during their 3 year open-source community development project:&lt;br/&gt;&lt;a href=&quot;http://www.embeddedcomponents.com/blogs/2007/04/community-software-development-for-embedded-devices/&quot;&gt;http://www.embeddedcomponents.com/blogs/2007/04/community-software-development-for-embedded-devices/&lt;/a&gt;&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>I can understand Ari&#8217;s comments. But I think there is room for many types of open-source communities:
<p />1) Harvest existing open-source software like Linux, where a few key individuals previously set in motion a great product and a great project model for the rest of us to use – and maybe use a corporate web site to manage the “harvesting” process,
<p />2) Contribute more open-source software to an already great product, like Linux, that only gets better as more contribute &#8211; thanks to the founding individuals, their project management methods, and the accepted web portals that act as their “watering holes”,
<p />3) Or be the new visionary with open-source project management methods that the rest of us can follow while delivering an entirely new open-source solution&#8230;
<p />Recently I discovered one of the early (first?) open-source community projects from 1981 that was successfully deployed on top of a closed operating system for a mobile embedded device. Perhaps your readers would be interested in learning about the similarities and differences demonstrated by these 100 engineers during their 3 year open-source community development project:<br /><a href="http://www.embeddedcomponents.com/blogs/2007/04/community-software-development-for-embedded-devices/">http://www.embeddedcomponents.com/blogs/2007/04/community-software-development-for-embedded-devices/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/bolsh/2007/04/14/links/feed/ ) in 1.19177 seconds, on Feb 10th, 2012 at 3:45 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 10th, 2012 at 4:45 pm UTC -->
