<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.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: The GPL and Principles</title>
	<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/</link>
	<description></description>
	<pubDate>Wed, 09 Jul 2008 12:02:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: ToddB</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17205</link>
		<dc:creator>ToddB</dc:creator>
		<pubDate>Thu, 08 May 2008 00:03:36 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17205</guid>
		<description>What do you think of companies that make their software GPL, and then sell a commercial version for use in closed source projects? Trolltech QT library, and bsddb under Oracle immediately spring to mind.</description>
		<content:encoded><![CDATA[<p>What do you think of companies that make their software GPL, and then sell a commercial version for use in closed source projects? Trolltech QT library, and bsddb under Oracle immediately spring to mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Straw</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17197</link>
		<dc:creator>Andrew Straw</dc:creator>
		<pubDate>Wed, 07 May 2008 17:27:15 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17197</guid>
		<description>Thanks for the interesting post. I would note that the scientific-computing-in-Python crowd has largely chosen the BSD license over the GPL, and one significant reason for this is the idea that it will encourage more development (see "John Hunter's License Pitch" at [the Scipy License Compatibility page](http://scipy.org/License_Compatibility "scipy.org") ). As I have seen a large and vibrant community grow around the basic Python, numpy, scipy, matplotlib software, all with a BSD or BSD-ish, license, I can't say that I see your point about "Projects that choose the GPL are more likely to engender a spirit of openness and sharing. [...] the difference [is] in the software that grows up around the project: extensions, complementary projects, documentation". 

Perhaps the choice of license is orthogonal to the success and openness of the scipy community -- the big competitors are closed source and anything open is incredibly attractive to many, and there aren't that many viable open source alternatives out there. The early developers chose the BSD license and the rest was history. Or, alternatively, perhaps the BSD license is causal to the success the community now enjoys. Big and small companies and organizations do pay people to work on this software, and the BSD license encourages them to do so without fear of being unable to release closed source apps.

It's difficult to distinguish between these alternatives conclusively, but my belief is that the BSD license is causal to the success of the scipy community. In particular, the company Enthought, which employs many key developers, needs a solid infrastructure for higher-level, closed-source apps they write and sell. I think their support has been quite significant, and even if the community has now reached a critical mass that could sustain continued growth, I think much of the early efforts benefitted directly from the choice of BSD license. (By the way, a founder of Enthought wrote [an interesting post](http://blog.enthought.com/?p=30 "blog.enthought.com") related to these issues.)</description>
		<content:encoded><![CDATA[<p>Thanks for the interesting post. I would note that the scientific-computing-in-Python crowd has largely chosen the BSD license over the GPL, and one significant reason for this is the idea that it will encourage more development (see &#8220;John Hunter&#8217;s License Pitch&#8221; at <a href="http://scipy.org/License_Compatibility" title="scipy.org">the Scipy License Compatibility page</a> ). As I have seen a large and vibrant community grow around the basic Python, numpy, scipy, matplotlib software, all with a BSD or BSD-ish, license, I can&#8217;t say that I see your point about &#8220;Projects that choose the GPL are more likely to engender a spirit of openness and sharing. [&#8230;] the difference [is] in the software that grows up around the project: extensions, complementary projects, documentation&#8221;. </p>

<p>Perhaps the choice of license is orthogonal to the success and openness of the scipy community &#8212; the big competitors are closed source and anything open is incredibly attractive to many, and there aren&#8217;t that many viable open source alternatives out there. The early developers chose the BSD license and the rest was history. Or, alternatively, perhaps the BSD license is causal to the success the community now enjoys. Big and small companies and organizations do pay people to work on this software, and the BSD license encourages them to do so without fear of being unable to release closed source apps.</p>

<p>It&#8217;s difficult to distinguish between these alternatives conclusively, but my belief is that the BSD license is causal to the success of the scipy community. In particular, the company Enthought, which employs many key developers, needs a solid infrastructure for higher-level, closed-source apps they write and sell. I think their support has been quite significant, and even if the community has now reached a critical mass that could sustain continued growth, I think much of the early efforts benefitted directly from the choice of BSD license. (By the way, a founder of Enthought wrote <a href="http://blog.enthought.com/?p=30" title="blog.enthought.com">an interesting post</a> related to these issues.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17195</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Wed, 07 May 2008 16:24:05 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17195</guid>
		<description>The "BSD is more free" arguments are all based on logic, which I think is an invalid way to discuss these issues.  Licenses are a social structure, not a logical structure.  The GPL is very explicit and open about its societal goals, and it is searching for societal freedom.  I find that people who believe in this mission share this sense of scope, though they don't always know how to articulate that.

And frankly the BSD-is-more-free argument is so obviously a logical trick that I find the argument intellectually dishonest.

(I wasn't sure if it was necessary to be tell people not to rant about the GPL in my last post, but that this post so quickly degenerated into this oft-repeated discussion of freedom makes it apparent that I was right to do so)</description>
		<content:encoded><![CDATA[<p>The &#8220;BSD is more free&#8221; arguments are all based on logic, which I think is an invalid way to discuss these issues.  Licenses are a social structure, not a logical structure.  The GPL is very explicit and open about its societal goals, and it is searching for societal freedom.  I find that people who believe in this mission share this sense of scope, though they don&#8217;t always know how to articulate that.</p>

<p>And frankly the BSD-is-more-free argument is so obviously a logical trick that I find the argument intellectually dishonest.</p>

<p>(I wasn&#8217;t sure if it was necessary to be tell people not to rant about the GPL in my last post, but that this post so quickly degenerated into this oft-repeated discussion of freedom makes it apparent that I was right to do so)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markus</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17190</link>
		<dc:creator>markus</dc:creator>
		<pubDate>Wed, 07 May 2008 14:39:47 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17190</guid>
		<description>&#62; This is much more freedom than the offers they’ll get for most other copyrighted works.

It is however less freedom than one gets with the BSD license, because you can opt to use under closed source, and BSD has less restrictions.

There are various shades of "freedom". The GPL is a very strict one. It does not necessarily have to be good or bad, but we all must acknowledge that it is stricter than the BSD.</description>
		<content:encoded><![CDATA[<p>&gt; This is much more freedom than the offers they’ll get for most other copyrighted works.</p>

<p>It is however less freedom than one gets with the BSD license, because you can opt to use under closed source, and BSD has less restrictions.</p>

<p>There are various shades of &#8220;freedom&#8221;. The GPL is a very strict one. It does not necessarily have to be good or bad, but we all must acknowledge that it is stricter than the BSD.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Finney</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17187</link>
		<dc:creator>Ben Finney</dc:creator>
		<pubDate>Wed, 07 May 2008 10:22:21 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17187</guid>
		<description>JonR: Note that no party is forced to release software under the GPL. They always have the option to keep their modifications private and not release them at all.

Copyright law reserves the right of redistribution of a work to the copyright holder. The GPL is *allowing* other parties this right, so long as they follow the conditions the copyright holder has chosen (through applying the GPL to the work).

If they don't like those conditions, nothing about the GPL is "forcing" them to release their modified work at all. That's a freedom they can always exercise if they choose, but only under the conditions of the license under which they received the work. This is much *more* freedom than the offers they'll get for most other copyrighted works.</description>
		<content:encoded><![CDATA[<p>JonR: Note that no party is forced to release software under the GPL. They always have the option to keep their modifications private and not release them at all.</p>

<p>Copyright law reserves the right of redistribution of a work to the copyright holder. The GPL is <em>allowing</em> other parties this right, so long as they follow the conditions the copyright holder has chosen (through applying the GPL to the work).</p>

<p>If they don&#8217;t like those conditions, nothing about the GPL is &#8220;forcing&#8221; them to release their modified work at all. That&#8217;s a freedom they can always exercise if they choose, but only under the conditions of the license under which they received the work. This is much <em>more</em> freedom than the offers they&#8217;ll get for most other copyrighted works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Finney</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17186</link>
		<dc:creator>Ben Finney</dc:creator>
		<pubDate>Wed, 07 May 2008 10:15:15 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17186</guid>
		<description>ToddB: Absolute freedom would have everyone allowed to do anything to anyone, with no societal restrictions on behaviour at all. To say that people in such a society are "free" is rather hollow, as it would be a paranoid, rule-of-the-ruthless world.

We don't live in that world, fortunately: we as a society restrict behaviour because we judge that behaviour more harmful than the corresponding reduction in freedom. One way I've heard this expressed is the phrase "Your freedom to swing your fist ends at the tip of my nose".

We are then faced with the choice of *which* freedoms are important for people to have in our society, and which are not desirable to preserve.

The GPL makes clear that "can impose restrictions on other people that were not imposed upon me" is not a freedom desirable to preserve. It does this through the condition that I may only redistribute the software under the same license terms as I received them.

IanB: thanks for a nice summary. I'm glad to see you expressing changed opinions as they come, whether from new information or further reflection.</description>
		<content:encoded><![CDATA[<p>ToddB: Absolute freedom would have everyone allowed to do anything to anyone, with no societal restrictions on behaviour at all. To say that people in such a society are &#8220;free&#8221; is rather hollow, as it would be a paranoid, rule-of-the-ruthless world.</p>

<p>We don&#8217;t live in that world, fortunately: we as a society restrict behaviour because we judge that behaviour more harmful than the corresponding reduction in freedom. One way I&#8217;ve heard this expressed is the phrase &#8220;Your freedom to swing your fist ends at the tip of my nose&#8221;.</p>

<p>We are then faced with the choice of <em>which</em> freedoms are important for people to have in our society, and which are not desirable to preserve.</p>

<p>The GPL makes clear that &#8220;can impose restrictions on other people that were not imposed upon me&#8221; is not a freedom desirable to preserve. It does this through the condition that I may only redistribute the software under the same license terms as I received them.</p>

<p>IanB: thanks for a nice summary. I&#8217;m glad to see you expressing changed opinions as they come, whether from new information or further reflection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon R</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17184</link>
		<dc:creator>Jon R</dc:creator>
		<pubDate>Wed, 07 May 2008 07:25:34 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17184</guid>
		<description>ToddB, you are misunderstanding the point. Open source is not the final goal; free software is the goal. Open source is a requirement of free software, but the reverse is not necessarily true. I can cite several cases where companies have attempted to appropriate open source code into non-free products (usually embedded firmware), but the GPL has forced them to make their products free.</description>
		<content:encoded><![CDATA[<p>ToddB, you are misunderstanding the point. Open source is not the final goal; free software is the goal. Open source is a requirement of free software, but the reverse is not necessarily true. I can cite several cases where companies have attempted to appropriate open source code into non-free products (usually embedded firmware), but the GPL has forced them to make their products free.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ToddB</title>
		<link>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17175</link>
		<dc:creator>ToddB</dc:creator>
		<pubDate>Tue, 06 May 2008 20:34:58 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/05/06/the-gpl-and-principles/#comment-17175</guid>
		<description>I don't think I will ever understand how putting restrictions on source codes use is beneficial if you are intending to open the source in the first place.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think I will ever understand how putting restrictions on source codes use is beneficial if you are intending to open the source in the first place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
