<?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: Fluendo releases proprietary codecs</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/</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: thilo pfennig</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-519</link>
		<dc:creator>thilo pfennig</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-519</guid>
		<description>Well the thing is where we want to go? Sure nobody needs to use free codecs - and nobody needs to use free software. We can all use Windows if we want - but maybe we want to have different conditions. Wouldn&#039;t we rather like to have free content, free software and (patent)free codecs? Then what does that mean to our business? I would agree though that selling this is not more evil than just providing the reverse engineered codecs. What I am generally missing is more solidarity between different communities (free culture, free software and anti patent lobbies). Free culture for instance also propagates the use of proprietary OSes like the Mac - there is always a good reason for making an exception - but if we would work more with free alternatives this would make a whole lot more sense. This is not dogmatic - I think mixing the proprietary with the free world always makes things complicated and OTOH combined powers could move mountains. Instead every community thinks mostly about its own standing and does crossover with the proprietary world where it does not habe its focus. So newest Drupal has tutorial videos in MPEG4 and not Ogg Theora, although Drupal itself is GPL software.</description>
		<content:encoded><![CDATA[<p>Well the thing is where we want to go? Sure nobody needs to use free codecs &#8211; and nobody needs to use free software. We can all use Windows if we want &#8211; but maybe we want to have different conditions. Wouldn&#8217;t we rather like to have free content, free software and (patent)free codecs? Then what does that mean to our business? I would agree though that selling this is not more evil than just providing the reverse engineered codecs. What I am generally missing is more solidarity between different communities (free culture, free software and anti patent lobbies). Free culture for instance also propagates the use of proprietary OSes like the Mac &#8211; there is always a good reason for making an exception &#8211; but if we would work more with free alternatives this would make a whole lot more sense. This is not dogmatic &#8211; I think mixing the proprietary with the free world always makes things complicated and OTOH combined powers could move mountains. Instead every community thinks mostly about its own standing and does crossover with the proprietary world where it does not habe its focus. So newest Drupal has tutorial videos in MPEG4 and not Ogg Theora, although Drupal itself is GPL software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Buck</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-520</link>
		<dc:creator>Joe Buck</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-520</guid>
		<description>Most use of proprietary codecs does not violate the GPL in any way.  The codec itself is not a derivative work of any GPL work, so it is not covered; downloading it from the network to one&#039;s own machine cannot violate the GPL.  Causing that codec to be linked into a GPL&#039;ed application on a user&#039;s own system, using a generic interface, again is not a GPL violation, as the GPL only covers distribution, not use.  In fact, I can link arbitrary proprietary code with GPL code on my own system without violating the GPL as long as no distribution is involved (and no, this does not mean that distributors can use &quot;user does the link&quot; as a hole; if  Alice provides a mechanism that results in Bob winding up with an identical program in her computer&#039;s memory as the one in Alice&#039;s computer memory, distribution has taken place, regardless of any technical tricks).&lt;p/&gt;There is a case where there is a GPL violation: if a distributor puts together a system consisting of proprietary codecs and GPL software and distributes that, the distributor is violating the GPL, because s/he is distributing a system that links proprietary and GPL code in one program.  So some distributors, the Linspire types, might consider deals with Fluendo, and others might direct their customers to Fluendo.&lt;p/&gt;Now, if Fluendo manages to raise money by this program that helps support their work on free software, I have no problem.  But they should avoid creating false impressions and implying that people who aren&#039;t their customers are law-breakers.  Depending on the particular codec and its terms of use, some other software license might be violated, but the GPL is not violated by the most common uses of proprietary codecs.&lt;p/&gt;</description>
		<content:encoded><![CDATA[<p>Most use of proprietary codecs does not violate the GPL in any way.  The codec itself is not a derivative work of any GPL work, so it is not covered; downloading it from the network to one&#8217;s own machine cannot violate the GPL.  Causing that codec to be linked into a GPL&#8217;ed application on a user&#8217;s own system, using a generic interface, again is not a GPL violation, as the GPL only covers distribution, not use.  In fact, I can link arbitrary proprietary code with GPL code on my own system without violating the GPL as long as no distribution is involved (and no, this does not mean that distributors can use &#8220;user does the link&#8221; as a hole; if  Alice provides a mechanism that results in Bob winding up with an identical program in her computer&#8217;s memory as the one in Alice&#8217;s computer memory, distribution has taken place, regardless of any technical tricks).
<p />There is a case where there is a GPL violation: if a distributor puts together a system consisting of proprietary codecs and GPL software and distributes that, the distributor is violating the GPL, because s/he is distributing a system that links proprietary and GPL code in one program.  So some distributors, the Linspire types, might consider deals with Fluendo, and others might direct their customers to Fluendo.
<p />Now, if Fluendo manages to raise money by this program that helps support their work on free software, I have no problem.  But they should avoid creating false impressions and implying that people who aren&#8217;t their customers are law-breakers.  Depending on the particular codec and its terms of use, some other software license might be violated, but the GPL is not violated by the most common uses of proprietary codecs.
<p />
]]></content:encoded>
	</item>
	<item>
		<title>By: thebluesgnr</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-521</link>
		<dc:creator>thebluesgnr</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-521</guid>
		<description>What proprietary codecs do you mean?&lt;p/&gt;I find that I can play pretty much everything with gstreamer-plugins-ugly and gstreamer-ffmpeg. Of course these may not be legal in some countries, fortunately they&#039;re still legal where I live.&lt;p/&gt;If you mean the w32codecs, I believe copyright law makes them illegal in most countries.&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>What proprietary codecs do you mean?
<p />I find that I can play pretty much everything with gstreamer-plugins-ugly and gstreamer-ffmpeg. Of course these may not be legal in some countries, fortunately they&#8217;re still legal where I live.
<p />If you mean the w32codecs, I believe copyright law makes them illegal in most countries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Neary</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-522</link>
		<dc:creator>Dave Neary</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-522</guid>
		<description>I mean the Win32 codecs, of course.&lt;p/&gt;Dave.</description>
		<content:encoded><![CDATA[<p>I mean the Win32 codecs, of course.
<p />Dave.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jg</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-523</link>
		<dc:creator>jg</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-523</guid>
		<description>&quot;I mean the Win32 codecs, of course.&quot;&lt;p/&gt;They are utterly useless. WMV9 is now working with VLC, with an open source implementation. (not the proprietary code.)&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>&#8220;I mean the Win32 codecs, of course.&#8221;
<p />They are utterly useless. WMV9 is now working with VLC, with an open source implementation. (not the proprietary code.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zaheer Merali</title>
		<link>http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/comment-page-1/#comment-524</link>
		<dc:creator>Zaheer Merali</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/#comment-524</guid>
		<description>Joe Buck: I think you misrepresent Fluendo completely.  Fluendo are not implying that people that are not their customers are law breakers.  There are open source implementations of all the codecs that Fluendo are selling, but none are possible for companies to distribute across their desktops or for Linux distributors to distribute with or without buying patent licences.&lt;p/&gt;Fluendo&#039;s codec implementations however are, and that&#039;s what should make them attractive to companies with large Linux desktop rollouts or to Linux distributors.&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>Joe Buck: I think you misrepresent Fluendo completely.  Fluendo are not implying that people that are not their customers are law breakers.  There are open source implementations of all the codecs that Fluendo are selling, but none are possible for companies to distribute across their desktops or for Linux distributors to distribute with or without buying patent licences.
<p />Fluendo&#8217;s codec implementations however are, and that&#8217;s what should make them attractive to companies with large Linux desktop rollouts or to Linux distributors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/bolsh/2007/01/16/fluendo-releases-proprietary-codecs/feed/ ) in 1.18978 seconds, on Feb 11th, 2012 at 6:24 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 7:24 am UTC -->
