<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Tivoization still possible with GPLv3 (draft4)?</title>
	<link>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/</link>
	<description>Just another GNOME Blogs weblog</description>
	<pubDate>Thu, 28 Aug 2008 12:17:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: raphael</title>
		<link>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-14</link>
		<dc:creator>raphael</dc:creator>
		<pubDate>Fri, 29 Jun 2007 14:29:34 +0000</pubDate>
		<guid>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-14</guid>
		<description>The reason why I reported it as a problem is that according to way the text of the license is written, the source code must be "the preferred form of the work for making modifications to it" but it is allowed to remove some files from the source code if they can be regenerated automatically. So this implies that the license allows distribution of a form of the work that it not the preferred form for making modifications to it (because the preferred form includes the files that have been removed).

That would be fine if there was also a requirement to make it easy to regenerate the files because then it would be trivial to go back to the "preferred form of the work for making modifications to it". But this requirement is missing, so it could be exploited by people or companies who want to prevent others from compiling and using some GPLed code.</description>
		<content:encoded><![CDATA[<p>The reason why I reported it as a problem is that according to way the text of the license is written, the source code must be &#8220;the preferred form of the work for making modifications to it&#8221; but it is allowed to remove some files from the source code if they can be regenerated automatically. So this implies that the license allows distribution of a form of the work that it not the preferred form for making modifications to it (because the preferred form includes the files that have been removed).</p>
<p>That would be fine if there was also a requirement to make it easy to regenerate the files because then it would be trivial to go back to the &#8220;preferred form of the work for making modifications to it&#8221;. But this requirement is missing, so it could be exploited by people or companies who want to prevent others from compiling and using some GPLed code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Flaschen</title>
		<link>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-13</link>
		<dc:creator>Matthew Flaschen</dc:creator>
		<pubDate>Fri, 29 Jun 2007 05:54:26 +0000</pubDate>
		<guid>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-13</guid>
		<description>The product instead of the factors (to use your example) would clearly not be the preferred form for modification.  So I don't think this loophole will work.</description>
		<content:encoded><![CDATA[<p>The product instead of the factors (to use your example) would clearly not be the preferred form for modification.  So I don&#8217;t think this loophole will work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RG3</title>
		<link>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-12</link>
		<dc:creator>RG3</dc:creator>
		<pubDate>Tue, 26 Jun 2007 13:08:49 +0000</pubDate>
		<guid>http://blogs.gnome.org/raphael/2007/06/20/tivoization-still-possible-with-gplv3-draft4/#comment-12</guid>
		<description>Well, it should be noted that courts tend to take a common-sense approach to such language.

Anyway, the fact that it says "regenerate" implies that it was generated in the first place.  So anything computationally infeasible would be out, since the distributor could not have generated the file using that method in the first place.</description>
		<content:encoded><![CDATA[<p>Well, it should be noted that courts tend to take a common-sense approach to such language.</p>
<p>Anyway, the fact that it says &#8220;regenerate&#8221; implies that it was generated in the first place.  So anything computationally infeasible would be out, since the distributor could not have generated the file using that method in the first place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
