<?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>A Fool's Wisdom &#187; Theme Licensing</title>
	<atom:link href="http://foolswisdom.com/tag/theme-licensing/feed/" rel="self" type="application/rss+xml" />
	<link>http://foolswisdom.com</link>
	<description>A fool and his blog are soon parted.</description>
	<lastBuildDate>Mon, 12 Dec 2011 22:39:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Commercial WordPress Themes&#8217;s PHP Code is GPL 2 Too</title>
		<link>http://foolswisdom.com/commercial-wordpress-themes-gpl2/</link>
		<comments>http://foolswisdom.com/commercial-wordpress-themes-gpl2/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 23:28:16 +0000</pubDate>
		<dc:creator>Lloyd</dc:creator>
				<category><![CDATA[GPL]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[GPL v2]]></category>
		<category><![CDATA[licensing]]></category>
		<category><![CDATA[Theme Licensing]]></category>
		<category><![CDATA[WordPress Themes]]></category>

		<guid isPermaLink="false">http://foolswisdom.com/?p=1983</guid>
		<description><![CDATA[I&#8217;m hoping that my boss Matt Mullenweg sharing the legal opinion on &#8220;Themes are GPL, too&#8221; will put the issue to rest for the majority of the community (emphasis mime): &#8220;PHP in WordPress themes must be GPL, artwork and CSS &#8230; <a href="http://foolswisdom.com/commercial-wordpress-themes-gpl2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m hoping that my boss <a href="http://ma.tt/">Matt Mullenweg</a> sharing the legal opinion on &#8220;<a href="http://wordpress.org/development/2009/07/themes-are-gpl-too/">Themes are GPL, too</a>&#8221; will put the issue to rest for the majority of the community (emphasis mime):</p>
<blockquote><p>&#8220;<strong>PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.</strong><br />
&#8230;<br />
Even though graphics and CSS aren’t <em>required</em> to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or JavaScript? So as before, we will only promote and host things on WordPress.org that are 100% GPL <a href="http://en.wikipedia.org/wiki/License_compatibility">or compatible</a>. To celebrate a few folks creating 100% GPL themes and providing support and other services around them, <a href="http://wordpress.org/extend/themes/commercial/">we have a new page listing GPL commercially supported themes</a>.&#8221;</p></blockquote>
<p>The legal opinion was provided by <a href="http://en.wikipedia.org/wiki/Software_Freedom_Law_Center">Software Freedom Law Center</a>. <a href="http://www.softwarefreedom.org/about/team/#vasile">Council</a> <a href="http://hackervisions.org/">James Vasile</a> provided the findings and blogs at <a href="http://hackervisions.org/">hackervisions.org</a> . James also has posted about this on his own blog in the article &#8220;<a title="Permalink to CMS Themes and the GPL" rel="bookmark" href="http://hackervisions.org/?p=419">CMS Themes and the GPL</a>&#8220;. As I commented there, my fear is:</p>
<blockquote><p>&#8220;people read what they want to get out of it, and case law is the only thing that moves them.&#8221;</p></blockquote>
<p>The legal finding and unchanged policy  are consistent with the <strong>intentions</strong> of the WordPress developer community and what has been promoted for the four years I&#8217;ve been involved.</p>
<p>Talking about licensing really is <a href="http://foolswisdom.com/licensing-is-the-suck/">the suck</a>. Matt&#8217;s article became necessary lately as some commercial theme developers have been very aggressive to WordPress community members, who have shared theme code as allowed by WordPress&#8217;s viral GPL v2 license.</p>
<p>It frustrates me when I read commercial theme developers complaining about people &#8220;stealing&#8221; their themes after the thousands of hours they have worked. They make no mention of the hundreds of thousands of hours others have worked on <a href="http://wordpress.org/">WordPress</a> (counting on the <a href="http://creativecommons.org/licenses/GPL/2.0/"> GPL protecting their freedoms </a>).</p>
<p>The incredibly exciting news is seeing the various <strong>commercially developed and supported themes</strong> embrace the GPL in the last 9 months. Theme collections like <a href="http://themeshaper.com/">ThemeShaper</a> (Thematic FrameWork), <a href="http://www.studiopress.com/">StudioPress</a> (previously Revolution 2),  and <a href="http://www.woothemes.com/">WooThemes</a> are all 100% GPL &#8212; those are just the ones I&#8217;m familar with, be sure to check out the theme offerings of the other <a href="http://wordpress.org/extend/themes/commercial/">commercially supported GPL themes</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://foolswisdom.com/commercial-wordpress-themes-gpl2/feed/</wfw:commentRss>
		<slash:comments>29</slash:comments>
		</item>
	</channel>
</rss>

