<?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: Guest post: 2010 &#8211; Threats to copyleft</title>
	<atom:link href="http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/feed/" rel="self" type="application/rss+xml" />
	<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/</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: Matt McCutchen</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-269</link>
		<dc:creator>Matt McCutchen</dc:creator>
		<pubDate>Wed, 24 Mar 2010 18:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-269</guid>
		<description>OK, the reference to the GPLv3 misled me about the point you were making.

Note that two nominally different licenses with identical terms are compatible; incompatibilities are a result of substantive differences between license terms.  To the extent that the differences reflect a community&#039;s intent not to allow its work to be used under the other terms, it would be wrong to just add a relicensing provision.  The differences should be discussed and their implications understood first.</description>
		<content:encoded><![CDATA[<p>OK, the reference to the GPLv3 misled me about the point you were making.</p>
<p>Note that two nominally different licenses with identical terms are compatible; incompatibilities are a result of substantive differences between license terms.  To the extent that the differences reflect a community&#8217;s intent not to allow its work to be used under the other terms, it would be wrong to just add a relicensing provision.  The differences should be discussed and their implications understood first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EUPL.it segnalato su OSS Watch Team Blog</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-268</link>
		<dc:creator>EUPL.it segnalato su OSS Watch Team Blog</dc:creator>
		<pubDate>Tue, 23 Mar 2010 18:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-268</guid>
		<description>[...] la Oxford University Computer Services, ha segnalato il sito &#8220;EUPL.IT&#8221; sull&#8217;OSS Watch Team Blog, all&#8217;interno di un post intitolato &#8220;Guest post:2010 &#8211; Threats to copyleft&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] la Oxford University Computer Services, ha segnalato il sito &#8220;EUPL.IT&#8221; sull&#8217;OSS Watch Team Blog, all&#8217;interno di un post intitolato &#8220;Guest post:2010 &#8211; Threats to copyleft&#8220;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P-E. Schmitz</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-267</link>
		<dc:creator>P-E. Schmitz</dc:creator>
		<pubDate>Mon, 22 Mar 2010 09:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-267</guid>
		<description>Well, Matt, I do not think so: If the primary license of a component in a combined work is AGPLv3, the purpose of interoperability provision (with the EUPL in my example) would be to enable licensing the whole combined work under EUPL (which is an “Affero” license) and under AGPLv3 (and not GPLv3 in this case). In general, interoperability should not modify the primary licence of a component.</description>
		<content:encoded><![CDATA[<p>Well, Matt, I do not think so: If the primary license of a component in a combined work is AGPLv3, the purpose of interoperability provision (with the EUPL in my example) would be to enable licensing the whole combined work under EUPL (which is an “Affero” license) and under AGPLv3 (and not GPLv3 in this case). In general, interoperability should not modify the primary licence of a component.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt McCutchen</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-266</link>
		<dc:creator>Matt McCutchen</dc:creator>
		<pubDate>Mon, 22 Mar 2010 04:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-266</guid>
		<description>GPLv3 and AGPLv3 material can be combined, but the combination is effectively under the AGPLv3 and is subject to the special requirement that source be available to users interacting with the program over a network.  Allowing the combined work to be relicensed as GPLv3, as suggested, would defeat the purpose of the AGPLv3.</description>
		<content:encoded><![CDATA[<p>GPLv3 and AGPLv3 material can be combined, but the combination is effectively under the AGPLv3 and is subject to the special requirement that source be available to users interacting with the program over a network.  Allowing the combined work to be relicensed as GPLv3, as suggested, would defeat the purpose of the AGPLv3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fr. Michael</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-265</link>
		<dc:creator>Fr. Michael</dc:creator>
		<pubDate>Wed, 17 Mar 2010 13:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-265</guid>
		<description>It seems indeed a pity that – due to licence incompatibility, strong copyleft software modules licensed under GPLv2 or v3 would be pushed out of combined works delivered to governments! Producing such collateral damage was certainly not the original purpose of copyleft (aimed to protect the free software community from their copyright appropriation). In such cases, – I mean the production of combined works, It would indeed be appropriate to extend interoperability between copyleft licenses. I fear that bringing even a small modification to licences like the GPLv3 would be a huge job. However, does the FSF care about what is happening in Europe?</description>
		<content:encoded><![CDATA[<p>It seems indeed a pity that – due to licence incompatibility, strong copyleft software modules licensed under GPLv2 or v3 would be pushed out of combined works delivered to governments! Producing such collateral damage was certainly not the original purpose of copyleft (aimed to protect the free software community from their copyright appropriation). In such cases, – I mean the production of combined works, It would indeed be appropriate to extend interoperability between copyleft licenses. I fear that bringing even a small modification to licences like the GPLv3 would be a huge job. However, does the FSF care about what is happening in Europe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neolex AB</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-263</link>
		<dc:creator>Neolex AB</dc:creator>
		<pubDate>Tue, 09 Mar 2010 08:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-263</guid>
		<description>The compatibility issue is indeed a significant problem. Our audits have shown that roughly one half of open source projects we audit suffer from some sort of licensing incompatibility issues, with about one fifth suffering from serious problems.

For a few examples, see the OSS IPR Database at http://oss-ipr-database.com/ (we started posting summaries of our audits there to help spread knowledge of the problem).</description>
		<content:encoded><![CDATA[<p>The compatibility issue is indeed a significant problem. Our audits have shown that roughly one half of open source projects we audit suffer from some sort of licensing incompatibility issues, with about one fifth suffering from serious problems.</p>
<p>For a few examples, see the OSS IPR Database at <a href="http://oss-ipr-database.com/" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/oss-ipr-database.com');">http://oss-ipr-database.com/</a> (we started posting summaries of our audits there to help spread knowledge of the problem).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mogh</title>
		<link>http://osswatch.jiscinvolve.org/wp/2010/03/05/guest-post-2010-threats-to-copyleft/comment-page-1/#comment-262</link>
		<dc:creator>Mogh</dc:creator>
		<pubDate>Mon, 08 Mar 2010 17:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://osswatch.jiscinvolve.org/2010/03/05/guest-post-2010-threats-to-copyleft/#comment-262</guid>
		<description>It&#039;s another example of software method patents, the threat is to everyone, developers and users. I believe they went for the patent(s) because the whole patent battle is a game won by those that get it first with the USPTO, as it is.</description>
		<content:encoded><![CDATA[<p>It&#8217;s another example of software method patents, the threat is to everyone, developers and users. I believe they went for the patent(s) because the whole patent battle is a game won by those that get it first with the USPTO, as it is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

