<?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: WordPress Plugin Directory Jumps the Shark?</title>
	<atom:link href="http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/</link>
	<description>Jack Born&#039;s website for website marketing tutorials and tools</description>
	<lastBuildDate>Sun, 08 Aug 2010 04:54:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jack</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-5203</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Thu, 13 Mar 2008 18:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-5203</guid>
		<description>Steve,
This post is pretty old.  I think at the time I was just upset that a plugin I had created would be excluded unless I GPL licensed it, and frankly, these days it doesn&#039;t matter very much to me.

But to answer your question more directly, I was referring to the discussion over the specific wording of the GPL license... not the WordPress directory.

Neither one has a huge impact on my business at all, but I could argue that at the time I made this post, the directory had &lt;em&gt;some&lt;/em&gt; effect.</description>
		<content:encoded><![CDATA[<p>Steve,<br />
This post is pretty old.  I think at the time I was just upset that a plugin I had created would be excluded unless I GPL licensed it, and frankly, these days it doesn&#8217;t matter very much to me.</p>
<p>But to answer your question more directly, I was referring to the discussion over the specific wording of the GPL license&#8230; not the WordPress directory.</p>
<p>Neither one has a huge impact on my business at all, but I could argue that at the time I made this post, the directory had <em>some</em> effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-5199</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Thu, 13 Mar 2008 18:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-5199</guid>
		<description>Jack if the new directory has no impact on your business why make a post on it?</description>
		<content:encoded><![CDATA[<p>Jack if the new directory has no impact on your business why make a post on it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-4444</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Thu, 28 Feb 2008 19:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-4444</guid>
		<description>Otto,
You&#039;ve made your point and we will have to agree to disagree.

I&#039;m not going to get into a pissing match with you over something that has no impact on my business.</description>
		<content:encoded><![CDATA[<p>Otto,<br />
You&#8217;ve made your point and we will have to agree to disagree.</p>
<p>I&#8217;m not going to get into a pissing match with you over something that has no impact on my business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-4442</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Thu, 28 Feb 2008 18:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-4442</guid>
		<description>Then you&#039;re wrong. Read it closer.

&quot;If identifiable sections of that work are not derived from the Program...&quot;

Anything making a call on a WordPress hook is derived from WordPress. If you call any WordPress function, if you use any of the WordPress internal structures, then you are deriving from WordPress.

If your plugin consists of nothing more than a collection of independent functions, has no configuration screen, and does not call any WordPress function or variable, then sure, you could make a non-GPL&#039;d WordPress plugin without violating the GPL. But I&#039;d bet that you&#039;d be hard pressed to find a plugin that does all that.</description>
		<content:encoded><![CDATA[<p>Then you&#8217;re wrong. Read it closer.</p>
<p>&#8220;If identifiable sections of that work are not derived from the Program&#8230;&#8221;</p>
<p>Anything making a call on a WordPress hook is derived from WordPress. If you call any WordPress function, if you use any of the WordPress internal structures, then you are deriving from WordPress.</p>
<p>If your plugin consists of nothing more than a collection of independent functions, has no configuration screen, and does not call any WordPress function or variable, then sure, you could make a non-GPL&#8217;d WordPress plugin without violating the GPL. But I&#8217;d bet that you&#8217;d be hard pressed to find a plugin that does all that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-4340</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Tue, 26 Feb 2008 17:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-4340</guid>
		<description>Otto,
Thanks for your comment, but I disagree with your interpretation of the GPL license.

&lt;blockquote&gt;
If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Otto,<br />
Thanks for your comment, but I disagree with your interpretation of the GPL license.</p>
<blockquote><p>
If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://www.jackborn.com/wordpress/wordpress-directory-jumps-the-shark/comment-page-1/#comment-4339</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Tue, 26 Feb 2008 17:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackborn.com/word-press/wordpress-directory-jumps-the-shark/#comment-4339</guid>
		<description>It would be extremely difficult to write a WordPress plugin without actually making it GPL licensed and still be legal. I suspect that 99% of the &quot;commercial&quot; plugins are violating the GPL.

WordPress is GPL licensed. Any plugin that uses any of WordPress&#039;s internal structures or functions is a derivative and it must also be GPL licensed. Period. 

The only reason for the &quot;compatible&quot; part is to allow for plugins that are considered to be public domain code and such, as well as to allow for plugins that use other libraries of free code and which integrate to WordPress in a compatible fashion.</description>
		<content:encoded><![CDATA[<p>It would be extremely difficult to write a WordPress plugin without actually making it GPL licensed and still be legal. I suspect that 99% of the &#8220;commercial&#8221; plugins are violating the GPL.</p>
<p>WordPress is GPL licensed. Any plugin that uses any of WordPress&#8217;s internal structures or functions is a derivative and it must also be GPL licensed. Period. </p>
<p>The only reason for the &#8220;compatible&#8221; part is to allow for plugins that are considered to be public domain code and such, as well as to allow for plugins that use other libraries of free code and which integrate to WordPress in a compatible fashion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
