<?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: Commercial re-use or not?</title>
	<atom:link href="http://osswatch.jiscinvolve.org/wp/2007/10/24/commercial-re-use-or-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://osswatch.jiscinvolve.org/wp/2007/10/24/commercial-re-use-or-not/</link>
	<description>open source software innovation support centre</description>
	<lastBuildDate>Fri, 03 Feb 2012 15:30:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ross Gardler</title>
		<link>http://osswatch.jiscinvolve.org/wp/2007/10/24/commercial-re-use-or-not/comment-page-1/#comment-132</link>
		<dc:creator>Ross Gardler</dc:creator>
		<pubDate>Wed, 24 Oct 2007 22:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2007/10/24/commercial-re-use-or-not/#comment-132</guid>
		<description>Thanks for your comments Steve.

I&#039;ve never really thought of enforcement of the GPL as being &quot;a little step along the road of proprietary paranoia&quot;, it is certainly an interesting take. One does need to pick which battles to fight when enforcing a licence and the GPL with its &quot;viral&quot; stipulation does increase the number of potential battles you may need to fight.

Of course, the fundamental believe of the FSF that all software must be Free is key to the GPL and that is why the FSF are willing to assist with &lt;a href=&quot;http://www.fsf.org/licensing/compliance&quot; rel=&quot;nofollow&quot;&gt;enforcing the GPL&lt;/a&gt;.

I also agree that there are problems with the language used in the rather complex GPL licence. All legal documents are open to many different interpretations. I agree that the simpler a licence can be the less likely it is to be misinterpreted, this is why many people, who are not concerned with enforcing software freedom through the licence, prefer the simpler &quot;permissive&quot; licences.

Your point about using a permissive licence to get stuff like assistive technologies into the wider environment is a very important one. For the same reasons, many people claim that permissive licences for reference implementations of open standards help ensure that that standard is more widely adopted.

I guess your first point is a new one, to translate it to the open content question that this post addresses I guess content authors need to consider whether they are ever likely to pursue commercial use of their content. I&#039;d guess that unless someone were making considerable money from your content you probably wouldn&#039;t bother. So the question then becomes, &quot;just how much is my content really worth?&quot; (very few people get rich from selling books for example).</description>
		<content:encoded><![CDATA[<p>Thanks for your comments Steve.</p>
<p>I&#8217;ve never really thought of enforcement of the GPL as being &#8220;a little step along the road of proprietary paranoia&#8221;, it is certainly an interesting take. One does need to pick which battles to fight when enforcing a licence and the GPL with its &#8220;viral&#8221; stipulation does increase the number of potential battles you may need to fight.</p>
<p>Of course, the fundamental believe of the FSF that all software must be Free is key to the GPL and that is why the FSF are willing to assist with <a href="http://www.fsf.org/licensing/compliance" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.fsf.org');">enforcing the GPL</a>.</p>
<p>I also agree that there are problems with the language used in the rather complex GPL licence. All legal documents are open to many different interpretations. I agree that the simpler a licence can be the less likely it is to be misinterpreted, this is why many people, who are not concerned with enforcing software freedom through the licence, prefer the simpler &#8220;permissive&#8221; licences.</p>
<p>Your point about using a permissive licence to get stuff like assistive technologies into the wider environment is a very important one. For the same reasons, many people claim that permissive licences for reference implementations of open standards help ensure that that standard is more widely adopted.</p>
<p>I guess your first point is a new one, to translate it to the open content question that this post addresses I guess content authors need to consider whether they are ever likely to pursue commercial use of their content. I&#8217;d guess that unless someone were making considerable money from your content you probably wouldn&#8217;t bother. So the question then becomes, &#8220;just how much is my content really worth?&#8221; (very few people get rich from selling books for example).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Lee</title>
		<link>http://osswatch.jiscinvolve.org/wp/2007/10/24/commercial-re-use-or-not/comment-page-1/#comment-131</link>
		<dc:creator>Steve Lee</dc:creator>
		<pubDate>Wed, 24 Oct 2007 13:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2007/10/24/commercial-re-use-or-not/#comment-131</guid>
		<description>Well I&#039;ve decided in favour of permissive licenses like BSD for my software project &lt;a href=&#039;http://www.oatsoft.org/trac/jambu&#039; rel=&quot;nofollow&quot;&gt;Jambu&lt;/a&gt;. My decision process included the thoughts you mention plus a couple more.

1) GPL like licences make the decision about whether to use Free software non-trivial. For example what exactly does &#039;link&#039; in the viral clause mean? Plus GPL rights protection starts to take energy in worrying about enforcement and that is a little step along the road of proprietary paranoia.

2) Jambu is assistive technology and the real value add is that people with disabilities get a better deal. So if someone takes it as the basis for a commercial proprietary product I&#039;m happy as long as in the big picture that causes a better deal for users. Hopefully they will feed back to me anyway, either explicitly or implicitly by raising expectations.

OK so there is a danger of proprietary &#039;stealing&#039; or hijacking but I think that is minimal.</description>
		<content:encoded><![CDATA[<p>Well I&#8217;ve decided in favour of permissive licenses like BSD for my software project <a href='http://www.oatsoft.org/trac/jambu' rel="nofollow">Jambu</a>. My decision process included the thoughts you mention plus a couple more.</p>
<p>1) GPL like licences make the decision about whether to use Free software non-trivial. For example what exactly does &#8216;link&#8217; in the viral clause mean? Plus GPL rights protection starts to take energy in worrying about enforcement and that is a little step along the road of proprietary paranoia.</p>
<p>2) Jambu is assistive technology and the real value add is that people with disabilities get a better deal. So if someone takes it as the basis for a commercial proprietary product I&#8217;m happy as long as in the big picture that causes a better deal for users. Hopefully they will feed back to me anyway, either explicitly or implicitly by raising expectations.</p>
<p>OK so there is a danger of proprietary &#8217;stealing&#8217; or hijacking but I think that is minimal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

