<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: GPL Considered Harmful?</title>
	<atom:link href="http://blog.sidneidasilva.com/2005/11/21/gpl-considered-harmful/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sidneidasilva.com/2005/11/21/gpl-considered-harmful/</link>
	<description></description>
	<lastBuildDate>Mon, 14 Feb 2011 05:53:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Rob Tillotson</title>
		<link>http://blog.sidneidasilva.com/2005/11/21/gpl-considered-harmful/#comment-138</link>
		<dc:creator><![CDATA[Rob Tillotson]]></dc:creator>
		<pubDate>Mon, 13 Mar 2006 01:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://omsg.wordpress.com/2005/11/21/gpl-considered-harmful/#comment-138</guid>
		<description><![CDATA[&lt;strong&gt; Python and the GPL &lt;/strong&gt; 
You seem to be under the misconception that Python is GPLed:

&gt;&gt; &quot;If you modify the Python interpreter, you can sell the modified interpreter, you can sell it but you just can&#039;t deny your customers the right to redistribute it.&quot;

You can, in fact, do exactly that, since Python does not use the GPL but rather its own license which allows use in closed-source applications, as long as you include the appropriate copyright notices and a &quot;brief summary of the changes made&quot;.  See http://www.python.org/2.4/license.html and specifically see footnote #1 in the explanation of Python&#039;s licensing history.

&gt;&gt; &quot;I don&#039;t think it&#039;s difficult to understand why the Python community doesn&#039;t appreciate your suggestion. If most of our software was licensed this way, there wouldn&#039;t BE a Python community.&quot;

Much Python related software IS licensed that way.  Check the licenses on third party Python modules, and see how many have a license that allows closed-source modification -- &quot;most&quot; is probably not an understatement.]]></description>
		<content:encoded><![CDATA[<p><strong> Python and the GPL </strong><br />
You seem to be under the misconception that Python is GPLed:</p>
<p>&gt;&gt; &quot;If you modify the Python interpreter, you can sell the modified interpreter, you can sell it but you just can&#8217;t deny your customers the right to redistribute it.&quot;</p>
<p>You can, in fact, do exactly that, since Python does not use the GPL but rather its own license which allows use in closed-source applications, as long as you include the appropriate copyright notices and a &quot;brief summary of the changes made&quot;.  See <a href="http://www.python.org/2.4/license.html" rel="nofollow">http://www.python.org/2.4/license.html</a> and specifically see footnote #1 in the explanation of Python&#8217;s licensing history.</p>
<p>&gt;&gt; &quot;I don&#8217;t think it&#8217;s difficult to understand why the Python community doesn&#8217;t appreciate your suggestion. If most of our software was licensed this way, there wouldn&#8217;t BE a Python community.&quot;</p>
<p>Much Python related software IS licensed that way.  Check the licenses on third party Python modules, and see how many have a license that allows closed-source modification &#8212; &quot;most&quot; is probably not an understatement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayson Vantuyl</title>
		<link>http://blog.sidneidasilva.com/2005/11/21/gpl-considered-harmful/#comment-137</link>
		<dc:creator><![CDATA[Jayson Vantuyl]]></dc:creator>
		<pubDate>Fri, 25 Nov 2005 08:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://omsg.wordpress.com/2005/11/21/gpl-considered-harmful/#comment-137</guid>
		<description><![CDATA[&lt;strong&gt; FUD &lt;/strong&gt; 
You can use GPL&#039;d code for commercial and for-profit purposes, I charge money for GPL&#039;d software.  This is explicitly blessed by the FSF as legal under the license.

The GPL v3 hasn&#039;t been released yet so I think that you are jumping the gun a little on your insinuations of poisoning and such.

The GPL v2 and planned v3 do not apply to content.  Your comment is FUD.

If you modify the Python interpreter, you can sell the modified interpreter, you can sell it but you just can&#039;t deny your customers the right to redistribute it.  If you create a module (for example), you can sell it independently of Python under any license you choose.

I find it ironic that people complain about being limited by the GPL but not by every other proprietary license.  The fact is the GPL prevents ANYONE from limiting your use of that software any more.  You want to be able to limit everyone&#039;s use of your code, but can&#039;t stomach being limited the same way.

I don&#039;t think it&#039;s difficult to understand why the Python community doesn&#039;t appreciate your suggestion.  If most of our software was licensed this way, there  wouldn&#039;t BE a Python community.

Look at the case of GPL&#039;d code in the recent Sony rootkit.  Look at the rebranding of PearPC as CherryOS.  These situations are why the GPL exists.  Without it, there would be no recourse for the authors of those software packages.]]></description>
		<content:encoded><![CDATA[<p><strong> FUD </strong><br />
You can use GPL&#8217;d code for commercial and for-profit purposes, I charge money for GPL&#8217;d software.  This is explicitly blessed by the FSF as legal under the license.</p>
<p>The GPL v3 hasn&#8217;t been released yet so I think that you are jumping the gun a little on your insinuations of poisoning and such.</p>
<p>The GPL v2 and planned v3 do not apply to content.  Your comment is FUD.</p>
<p>If you modify the Python interpreter, you can sell the modified interpreter, you can sell it but you just can&#8217;t deny your customers the right to redistribute it.  If you create a module (for example), you can sell it independently of Python under any license you choose.</p>
<p>I find it ironic that people complain about being limited by the GPL but not by every other proprietary license.  The fact is the GPL prevents ANYONE from limiting your use of that software any more.  You want to be able to limit everyone&#8217;s use of your code, but can&#8217;t stomach being limited the same way.</p>
<p>I don&#8217;t think it&#8217;s difficult to understand why the Python community doesn&#8217;t appreciate your suggestion.  If most of our software was licensed this way, there  wouldn&#8217;t BE a Python community.</p>
<p>Look at the case of GPL&#8217;d code in the recent Sony rootkit.  Look at the rebranding of PearPC as CherryOS.  These situations are why the GPL exists.  Without it, there would be no recourse for the authors of those software packages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steffen</title>
		<link>http://blog.sidneidasilva.com/2005/11/21/gpl-considered-harmful/#comment-136</link>
		<dc:creator><![CDATA[steffen]]></dc:creator>
		<pubDate>Wed, 23 Nov 2005 09:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://omsg.wordpress.com/2005/11/21/gpl-considered-harmful/#comment-136</guid>
		<description><![CDATA[&lt;strong&gt; Python license for Zope &amp; Plone? &lt;/strong&gt; 
    The GPL (esp. GPL v3) is poison.  It 
isn&#039;t at all clear that anything posted to a 
plone site doesn&#039;t fall under GPL v3 provisions.  
It sure would be nice for python, zope and plone to 
converge on a single, python-like license.  
     This way, the world could use 
python/zope/CMF/plone stack for whatever 
purposes ... including commercial/for-profit 
purposes.]]></description>
		<content:encoded><![CDATA[<p><strong> Python license for Zope &amp; Plone? </strong><br />
    The GPL (esp. GPL v3) is poison.  It<br />
isn&#8217;t at all clear that anything posted to a<br />
plone site doesn&#8217;t fall under GPL v3 provisions.<br />
It sure would be nice for python, zope and plone to<br />
converge on a single, python-like license.<br />
     This way, the world could use<br />
python/zope/CMF/plone stack for whatever<br />
purposes &#8230; including commercial/for-profit<br />
purposes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

