<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Roundtrip to Shanghai via Tokyo &#187; gpl</title>
	<atom:link href="http://kohei.us/tag/gpl/feed/" rel="self" type="application/rss+xml" />
	<link>http://kohei.us</link>
	<description>Kohei Yoshida&#039;s Webspace</description>
	<lastBuildDate>Wed, 14 Dec 2011 04:17:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>GPL Compatibility</title>
		<link>http://kohei.us/2006/04/27/gpl-compatibility/</link>
		<comments>http://kohei.us/2006/04/27/gpl-compatibility/#comments</comments>
		<pubDate>Thu, 27 Apr 2006 05:23:59 +0000</pubDate>
		<dc:creator>Kohei Yoshida</dc:creator>
				<category><![CDATA[]]></category>
		<category><![CDATA[gpl]]></category>
		<category><![CDATA[license]]></category>

		<guid isPermaLink="false">http://blog.kohei.us/2006/04/27/gpl-compatibility/</guid>
		<description><![CDATA[I&#8217;ve just come across this nice piece by David Wheeler on open source licensing and what it means to be GPL-compatible. Anybody who needs to deal with this kind of stuff (myself certainly included) should take a good look at &#8230; <a href="http://kohei.us/2006/04/27/gpl-compatibility/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve just come across <a href="http://www.dwheeler.com/essays/gpl-compatible.html">this nice piece</a> by David Wheeler on open source licensing and what it means to be GPL-compatible.  Anybody who needs to deal with this kind of stuff (myself certainly included) should take a good look at this article.  Unfortunately, licensing is only just one piece of the whole puzzle: there is also copyright assignment side of things that one must deal with when managing or contributing to a multi-licensed open source project, adding more confusion to the already complex, legal aspect of open source.</p>
<p>One common scenario one may encounter:</p>
<p><strong>Bob the contributor:</strong> hey, thanks for your work.  I&#8217;ve made some neat change to your software.  Here is my patch.  It&#8217;s GPL, so feel free to commit it to your source.</p>
<p><strong>John the maintainer:</strong> Thanks.  But I can&#8217;t accept your patch without first having you sign this copyright assignment, which you must fax to this number, wait for a few weeks to have our laywer go over it, and &#8230;</p>
<p><strong>Bob:</strong> Why!?  I thought your software was GPL&#8217;ed.  Why do I need to go though all that trouble just for one patch!?  Just take it.</p>
<p><strong>John:</strong> Yes, but&#8230;(John&#8217;s software is dual-licensed with GPL and a commercial license for his own company.)</p>
<p>Things get more complicated when Bob&#8217;s patch was derived from another GPL&#8217;ed software that someone else wrote&#8230;  Go figure.</p>
]]></content:encoded>
			<wfw:commentRss>http://kohei.us/2006/04/27/gpl-compatibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

