<?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: Working on the Crimson Workflow</title>
	<atom:link href="http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/</link>
	<description>A few words about non-linear editing, filmmaking and more ...</description>
	<lastBuildDate>Sat, 24 Sep 2011 15:48:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nye kameraer fra RED (og flere vitnerapporter) &#171; Rushblogg</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-8166</link>
		<dc:creator>Nye kameraer fra RED (og flere vitnerapporter) &#171; Rushblogg</dc:creator>
		<pubDate>Tue, 03 Mar 2009 17:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-8166</guid>
		<description>[...] Klipperen Scott Simmons har ogs&#229; de siste m&#229;nedene delt av sine erfaringer fra sitt f&#248;rste prosjekt med materiale fra et RED-kamera. Hans forskjellige artikler finnes her, her og her. [...]</description>
		<content:encoded><![CDATA[<p>[...] Klipperen Scott Simmons har ogs&aring; de siste m&aring;nedene delt av sine erfaringer fra sitt f&oslash;rste prosjekt med materiale fra et RED-kamera. Hans forskjellige artikler finnes her, her og her. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: All Things Red: Images/Video/Updates at FreshDV</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-7702</link>
		<dc:creator>All Things Red: Images/Video/Updates at FreshDV</dc:creator>
		<pubDate>Tue, 15 Jul 2008 02:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-7702</guid>
		<description>[...] put the Red One, Sony F23, and Sony EX1 next to each other in this informal test. *Scott Simmons on Crimson Workflow and 10-bit vs 8-bit workflow. *Scott Simmons has written a in-depth overview of the current RED [...]</description>
		<content:encoded><![CDATA[<p>[...] put the Red One, Sony F23, and Sony EX1 next to each other in this informal test. *Scott Simmons on Crimson Workflow and 10-bit vs 8-bit workflow. *Scott Simmons has written a in-depth overview of the current RED [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Monaghan</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-6842</link>
		<dc:creator>Bob Monaghan</dc:creator>
		<pubDate>Sat, 05 Apr 2008 17:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-6842</guid>
		<description>I think that people who suggest that a package should become &quot;open-source&quot; are selfish. The guy just put a lot of blood, sweat and tears into a product that solves a problem. And now people want him to give it away for free, source-code and all, because they are:
A) Too lazy to solve the problem themselves
and
B) Too cheap to support the development.

If this was an open source project from day 1, that would be a different story. But it isn&#039;t. They guy is asking to be compensated for his work. But to demand that a product be open-sourced after it has been proven to be useful, is pretty lame. Especially when people plan on using this product to make money for themselves.

bob.</description>
		<content:encoded><![CDATA[<p>I think that people who suggest that a package should become &#8220;open-source&#8221; are selfish. The guy just put a lot of blood, sweat and tears into a product that solves a problem. And now people want him to give it away for free, source-code and all, because they are:<br />
A) Too lazy to solve the problem themselves<br />
and<br />
B) Too cheap to support the development.</p>
<p>If this was an open source project from day 1, that would be a different story. But it isn&#8217;t. They guy is asking to be compensated for his work. But to demand that a product be open-sourced after it has been proven to be useful, is pretty lame. Especially when people plan on using this product to make money for themselves.</p>
<p>bob.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: editblog</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-6795</link>
		<dc:creator>editblog</dc:creator>
		<pubDate>Tue, 25 Mar 2008 17:01:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-6795</guid>
		<description>Oooooo .... matt..... you didn&#039;t go there!</description>
		<content:encoded><![CDATA[<p>Oooooo &#8230;. matt&#8230;.. you didn&#8217;t go there!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-6794</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Tue, 25 Mar 2008 15:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-6794</guid>
		<description>whenever i hear crimson and flow in the same sentence...</description>
		<content:encoded><![CDATA[<p>whenever i hear crimson and flow in the same sentence&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Williams</title>
		<link>http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/comment-page-1/#comment-6792</link>
		<dc:creator>Owen Williams</dc:creator>
		<pubDate>Tue, 25 Mar 2008 14:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2008/03/25/working-on-the-crimson-workflow/#comment-6792</guid>
		<description>As someone coming from the open source world, this is a pretty funny post to me.  Individual developer attention?  Where I come from, using open source software, that&#039;s the default mode of support.  After working a while in the production business I&#039;m getting more used to the mindset that every little utility and plugin costs money (even if it&#039;s something that should have worked in the first place), but it still doesn&#039;t feel right.

If Ian released the source code to his program, other developers could help him fix bugs, add features, make it easier to use, even translate it to other languages.  A community of developers, all able to hack on the code, will be more productive than one over-worked forum member.  For instance if he were to get a big project, development would languish and you&#039;d have to wait until he has some free time again before progress could resume.

Sure he wouldn&#039;t be making tons of money off the program, but it sounds like money is not really the motivating factor in the first place.  This sounds like one case where the benefits of openness outweigh the dollars he&#039;d be giving up.  (And he could always solicit donations, that works too.)</description>
		<content:encoded><![CDATA[<p>As someone coming from the open source world, this is a pretty funny post to me.  Individual developer attention?  Where I come from, using open source software, that&#8217;s the default mode of support.  After working a while in the production business I&#8217;m getting more used to the mindset that every little utility and plugin costs money (even if it&#8217;s something that should have worked in the first place), but it still doesn&#8217;t feel right.</p>
<p>If Ian released the source code to his program, other developers could help him fix bugs, add features, make it easier to use, even translate it to other languages.  A community of developers, all able to hack on the code, will be more productive than one over-worked forum member.  For instance if he were to get a big project, development would languish and you&#8217;d have to wait until he has some free time again before progress could resume.</p>
<p>Sure he wouldn&#8217;t be making tons of money off the program, but it sounds like money is not really the motivating factor in the first place.  This sounds like one case where the benefits of openness outweigh the dollars he&#8217;d be giving up.  (And he could always solicit donations, that works too.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

