<?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"
	>
<channel>
	<title>Comments on: Gimmie vs Big Board</title>
	<atom:link href="http://blogs.gnome.org/rodrigo/2007/04/06/gimmie-vs-big-board/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/rodrigo/2007/04/06/gimmie-vs-big-board/</link>
	<description>From lost to the river</description>
	<pubDate>Tue, 07 Oct 2008 22:04:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Mathias Hasselmann</title>
		<link>http://blogs.gnome.org/rodrigo/2007/04/06/gimmie-vs-big-board/#comment-466</link>
		<dc:creator>Mathias Hasselmann</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2007/04/06/gimmie-vs-big-board/#comment-466</guid>
		<description>I doubt those community reactions are based on paranoia. In my opinion they are based on the fact, that secret in-house development greatly violates the open development process of the free software community. One key feature of free software development is, that everyone interested has the chance to influence future developments. But developing in house and agressively pushing those huge chunks of code _by purpose_ circumvents this essential piece of our community for the stupid goal of saving some time in the initial development steps. I consider that decision stupid as you pay for the initial savement by big efforts and endless discussions when pushing those in-house chunks upstream. Guess those initial kick-off weeks of public discussion quickly pay back when arranging with the community from the start.</description>
		<content:encoded><![CDATA[<p>I doubt those community reactions are based on paranoia. In my opinion they are based on the fact, that secret in-house development greatly violates the open development process of the free software community. One key feature of free software development is, that everyone interested has the chance to influence future developments. But developing in house and agressively pushing those huge chunks of code _by purpose_ circumvents this essential piece of our community for the stupid goal of saving some time in the initial development steps. I consider that decision stupid as you pay for the initial savement by big efforts and endless discussions when pushing those in-house chunks upstream. Guess those initial kick-off weeks of public discussion quickly pay back when arranging with the community from the start.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
