<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Free software licenses</title>
	<atom:link href="http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/</link>
	<description>Exploring free licenses and their practical uses</description>
	<lastBuildDate>Thu, 06 Mar 2008 19:21:15 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: keito</title>
		<link>http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/comment-page-1/#comment-4</link>
		<dc:creator>keito</dc:creator>
		<pubDate>Thu, 10 Jan 2008 21:26:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/#comment-4</guid>
		<description>achates, thank you for the corrections. You&#039;re right about both -- the first, the GPL specifically mentions even in the preamble (&quot;...we have made it clear that any patent must be licensed for everyone&#039;s free use or not licensed at all.&quot;). The second, the GPL also clearly states (&quot;You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.&quot;) This is what many companies already do, with GPL-licensed products like the GIMP and Linux itself. (Although what they are usually selling are support or extra features or refinements to the original software.)</description>
		<content:encoded><![CDATA[<p>achates, thank you for the corrections. You&#8217;re right about both &#8212; the first, the GPL specifically mentions even in the preamble (&#8221;&#8230;we have made it clear that any patent must be licensed for everyone&#8217;s free use or not licensed at all.&#8221;). The second, the GPL also clearly states (&#8221;You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.&#8221;) This is what many companies already do, with GPL-licensed products like the GIMP and Linux itself. (Although what they are usually selling are support or extra features or refinements to the original software.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: achates</title>
		<link>http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/comment-page-1/#comment-3</link>
		<dc:creator>achates</dc:creator>
		<pubDate>Thu, 10 Jan 2008 21:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/#comment-3</guid>
		<description>The statement of the patent restrictions is incorrect. You can patent GPLed software, but you have to grant a license to all users of the software.

Also, the statement that &quot;all licensed copies cannot be sold for profit&quot; is incorrect, there is no restriction on selling GPLed software for a profit, so long as the license restrictions are met. In practical terms, this makes it hard to make a profit on direct sales (since any downstream licensee can compete at any price it likes), but the license permits you to try.</description>
		<content:encoded><![CDATA[<p>The statement of the patent restrictions is incorrect. You can patent GPLed software, but you have to grant a license to all users of the software.</p>
<p>Also, the statement that &#8220;all licensed copies cannot be sold for profit&#8221; is incorrect, there is no restriction on selling GPLed software for a profit, so long as the license restrictions are met. In practical terms, this makes it hard to make a profit on direct sales (since any downstream licensee can compete at any price it likes), but the license permits you to try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FreeSoftNews &#187; Blog Archive &#187; Free software licenses</title>
		<link>http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/comment-page-1/#comment-2</link>
		<dc:creator>FreeSoftNews &#187; Blog Archive &#187; Free software licenses</dc:creator>
		<pubDate>Wed, 09 Jan 2008 17:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/keito/2008/01/07/free-software-licenses/#comment-2</guid>
		<description>[...] Read more &#8230;. [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more &#8230;. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
