<?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 Themes Are GPL Code</title>
	<atom:link href="http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/</link>
	<description>WP Plugins and Widgets For Wordpress 2.1+</description>
	<lastBuildDate>Wed, 10 Mar 2010 13:21:18 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Angelo</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-25053</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Mon, 23 Mar 2009 23:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-25053</guid>
		<description>Some people seem confused here.  Defintely and absolutely if you make a call to something like wp_head() in your theme, you ARE subject to the GPL.  End of story.  There is no way, without an explicit statement from WordPress, that you can get out of that.  But then again, that is WordPress&#039; duty to enforce.</description>
		<content:encoded><![CDATA[<p>Some people seem confused here.  Defintely and absolutely if you make a call to something like wp_head() in your theme, you ARE subject to the GPL.  End of story.  There is no way, without an explicit statement from WordPress, that you can get out of that.  But then again, that is WordPress&#8217; duty to enforce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Premium Wordpress Theme? &#124; eliwagar</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-24499</link>
		<dc:creator>Premium Wordpress Theme? &#124; eliwagar</dc:creator>
		<pubDate>Tue, 24 Feb 2009 13:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-24499</guid>
		<description>[...] was darunter zu verstehen ist. N&#228;mlich alles, was die Wordpress API nutzt (siehe hierzu Wordpress Themes are GPL Code). Und das tun Themes nun einmal&#8230;denn was tun Themes anderes, als Wordpress-spezifische Module [...]</description>
		<content:encoded><![CDATA[<p>[...] was darunter zu verstehen ist. N&#228;mlich alles, was die Wordpress API nutzt (siehe hierzu Wordpress Themes are GPL Code). Und das tun Themes nun einmal&#8230;denn was tun Themes anderes, als Wordpress-spezifische Module [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Bailey</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-21850</link>
		<dc:creator>Kris Bailey</dc:creator>
		<pubDate>Thu, 20 Nov 2008 21:59:03 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-21850</guid>
		<description>So far as I can tell this is all about the ability of something to run with/without wordpress, and whether you distribute it with/without wordpress.  So, if you were to sell someone the theme and sell them the service of installing it, you could install wordpress and the theme at the same time and be fine with a non-gpl theme.  But, if you were to sell the theme on your site, the download of the theme file couldn&#039;t be a modified wordpress archive with the theme already in it.  That addresses the distribution issues.

As far as the ability to work independantly, or with another piece of non-gpl software instead of wordpress, it would be trivial to create a simple theme framework that provided the basics of the wordpress theme environment.  I could make one that had stubs with dummy content for all of the important methods in wp in about 4 hours, and then bsd license the thing.  The funny part of that is that it would actually be able to run a website with static content were you to just adjust a few things in the stub file... example: 
&lt;code&gt;
function the_post(){
return &#039;content here.&#039;;
}
&lt;/code&gt;

With these things taken care of there wouldn&#039;t be the gpl requirement onus on your themes.  The same would hold true for plugins.

Any for you guys arguing the gpl viralness applying to css, you are completely wrong.  Read this article:
http://www.linuxdevices.com/articles/AT5041108431.html

Pay attention to the part pertaining to binary modules not being infected by the gpl when using standard unix interfaces.  css uses standard interfaces for things, and as mikec has noted, wordpress doesn&#039;t own the rights to the selectors used in the css file.  Also, at the worst, the problem would be license incompatibility, not gpl viralness.  The license for the theme wouldn&#039;t be compatible with wordpress and it would be against the gpl license for the person USING wordpress to use the theme with it.  It would have no effects on the theme creator.</description>
		<content:encoded><![CDATA[<p>So far as I can tell this is all about the ability of something to run with/without wordpress, and whether you distribute it with/without wordpress.  So, if you were to sell someone the theme and sell them the service of installing it, you could install wordpress and the theme at the same time and be fine with a non-gpl theme.  But, if you were to sell the theme on your site, the download of the theme file couldn&#8217;t be a modified wordpress archive with the theme already in it.  That addresses the distribution issues.</p>
<p>As far as the ability to work independantly, or with another piece of non-gpl software instead of wordpress, it would be trivial to create a simple theme framework that provided the basics of the wordpress theme environment.  I could make one that had stubs with dummy content for all of the important methods in wp in about 4 hours, and then bsd license the thing.  The funny part of that is that it would actually be able to run a website with static content were you to just adjust a few things in the stub file&#8230; example:<br />
<code><br />
function the_post(){<br />
return 'content here.';<br />
}<br />
</code></p>
<p>With these things taken care of there wouldn&#8217;t be the gpl requirement onus on your themes.  The same would hold true for plugins.</p>
<p>Any for you guys arguing the gpl viralness applying to css, you are completely wrong.  Read this article:<br />
<a href="http://www.linuxdevices.com/articles/AT5041108431.html" rel="nofollow">http://www.linuxdevices.com/articles/AT5041108431.html</a></p>
<p>Pay attention to the part pertaining to binary modules not being infected by the gpl when using standard unix interfaces.  css uses standard interfaces for things, and as mikec has noted, wordpress doesn&#8217;t own the rights to the selectors used in the css file.  Also, at the worst, the problem would be license incompatibility, not gpl viralness.  The license for the theme wouldn&#8217;t be compatible with wordpress and it would be against the gpl license for the person USING wordpress to use the theme with it.  It would have no effects on the theme creator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: law updates</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-21804</link>
		<dc:creator>law updates</dc:creator>
		<pubDate>Wed, 19 Nov 2008 06:39:52 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-21804</guid>
		<description>I think many people worship at the feet of Matt a bit too much on this. Obviously he is going to insist that designs are under the GPL but last time I checked there is not a single piece of PHP code in a style sheet and Matt didn’t invent stylesheets or CSS . Its Matt’s software that calls for the CSS not the other way around and no court in the land is about to give him or Wordpress the rights to CSS files just because his software calls for it. Will Matt also claim that if a company employs a graphic designer to make icons, headers and a logo for their wordpress site that the graphics then are GPL also?</description>
		<content:encoded><![CDATA[<p>I think many people worship at the feet of Matt a bit too much on this. Obviously he is going to insist that designs are under the GPL but last time I checked there is not a single piece of PHP code in a style sheet and Matt didn’t invent stylesheets or CSS . Its Matt’s software that calls for the CSS not the other way around and no court in the land is about to give him or Wordpress the rights to CSS files just because his software calls for it. Will Matt also claim that if a company employs a graphic designer to make icons, headers and a logo for their wordpress site that the graphics then are GPL also?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul William Tenny</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-19532</link>
		<dc:creator>Paul William Tenny</dc:creator>
		<pubDate>Sun, 14 Sep 2008 18:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-19532</guid>
		<description>&lt;blockquote&gt;Removing the link (not paid for) is the same as breaking the law and action can be taken against you.&lt;/blockquote&gt;

Umm, no. Violating any law is a criminal offense that results in jail time, this would be a civil offense that results of monetary fines, and probably not a very large one.

Not even close to the same thing.</description>
		<content:encoded><![CDATA[<blockquote><p>Removing the link (not paid for) is the same as breaking the law and action can be taken against you.</p></blockquote>
<p>Umm, no. Violating any law is a criminal offense that results in jail time, this would be a civil offense that results of monetary fines, and probably not a very large one.</p>
<p>Not even close to the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One Way in which Habari Absolutely Slaughters WordPress - Asymptomatic</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-19390</link>
		<dc:creator>One Way in which Habari Absolutely Slaughters WordPress - Asymptomatic</dc:creator>
		<pubDate>Tue, 09 Sep 2008 01:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-19390</guid>
		<description>[...] and done something radically better. This is one example that stands out firmly in my mind.I am not the only person who has noticed that WordPress is released under the GNU General Public License. In the license, it [...]</description>
		<content:encoded><![CDATA[<p>[...] and done something radically better. This is one example that stands out firmly in my mind.I am not the only person who has noticed that WordPress is released under the GNU General Public License. In the license, it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Coveney</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-11865</link>
		<dc:creator>David Coveney</dc:creator>
		<pubDate>Wed, 07 May 2008 17:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-11865</guid>
		<description>I&#039;m glad Mike&#039;s fighting the same rights corner as myself.

As we&#039;re soon to be making money from premium themes (both WordPress.com and through our own system) we&#039;ve taken a long hard look at this and come up with this precaution, just in case:

Our themes come with separate styles, which are essentially a configuration file, images and so on.  The styles can and will be distributed separately from the themes as they&#039;re independent entities.  They need WordPress to run, but that doesn&#039;t make them into GPL.  Just like an image only viewable in GIMP doesn&#039;t become GPL either.

Professional coders, paid a living, can and do contribute hugely to open source projects.  But the money has to come from somewhere - being able to do some added effort work to complement our GPL work makes this possible.

At least WordPress accept that theme builders need to earn a living if they&#039;re to get the best themes possible - hence the marketplace giving 50% of proceeds to the developers.  That may not sound generous, but with GPL they could cheerfully pick up themes for free and then sell them at a profit.  So here&#039;s a woo for WordPress.com :-)  I just hope they get on and finish that damn marketplace before I retire!</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad Mike&#8217;s fighting the same rights corner as myself.</p>
<p>As we&#8217;re soon to be making money from premium themes (both <a href="http://WordPress.com" title="http://WordPress.com" target="_blank">WordPress.com</a> and through our own system) we&#8217;ve taken a long hard look at this and come up with this precaution, just in case:</p>
<p>Our themes come with separate styles, which are essentially a configuration file, images and so on.  The styles can and will be distributed separately from the themes as they&#8217;re independent entities.  They need WordPress to run, but that doesn&#8217;t make them into GPL.  Just like an image only viewable in GIMP doesn&#8217;t become GPL either.</p>
<p>Professional coders, paid a living, can and do contribute hugely to open source projects.  But the money has to come from somewhere &#8211; being able to do some added effort work to complement our GPL work makes this possible.</p>
<p>At least WordPress accept that theme builders need to earn a living if they&#8217;re to get the best themes possible &#8211; hence the marketplace giving 50% of proceeds to the developers.  That may not sound generous, but with GPL they could cheerfully pick up themes for free and then sell them at a profit.  So here&#8217;s a woo for <a href="http://WordPress.com" title="http://WordPress.com" target="_blank">WordPress.com</a> <img src='http://wordpress-plugins.feifei.us/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />   I just hope they get on and finish that damn marketplace before I retire!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-11586</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Fri, 02 May 2008 14:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-11586</guid>
		<description>Mike, I don&#039;t believe your theme is solely a CSS file, it needs php files to work with WordPress. I do concede that there may be harm if Matt were to state explicitly that all WordPress themes are GPL.</description>
		<content:encoded><![CDATA[<p>Mike, I don&#8217;t believe your theme is solely a CSS file, it needs php files to work with WordPress. I do concede that there may be harm if Matt were to state explicitly that all WordPress themes are GPL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeC</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-10181</link>
		<dc:creator>MikeC</dc:creator>
		<pubDate>Mon, 14 Apr 2008 22:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-10181</guid>
		<description>Often times in open source community there is this blind short sighted  commitment to everything being open and monetarily free even if the logical conclusion of that would be the detriment of the community&#039;s real needs.  People don&#039;t really take the time to think things through and fail to see the differences between software and artistic design.  

Software is made for replication. 

The more people using a piece of software makes it stronger in the marketplace. Replication meets the goal of software to present a solution to a wide need. 
Design is entirely different.  A million people using the same exact Wordpress release empowers the commmunity - a million people using the same  exact design  would hinder the community and make it look like the software wasn&#039;t capable of much creativity.

No matter how dishonest we may wish to be in a debate like this the facts are almost all of us want a site that looks as unique as we are able to achieve given our resources of time and capital. 

Wordpress is a presentation piece of software and we don&#039;t mind that. What we don&#039;t want is for the presentation itself - our sites - to look exactly like a thousand other sites. 

In other words what every web designer worthy of the title already knows is that the central need of the web site owner is not replication but creative uniqueness otherwise known in the business word as branding.

By very definition the only way to protect uniqueness is to limit its distribution.  Like it or not it meets a core need of the community.

The second error people make is that they tend to define the open source community in a way that excludes a large part of the community in favor of frankly people looking for a free ride and little else.  There is a HUGE portion of the wordpress community that is attempting to use wordpress for financial gain. I can&#039;t remember the last time I have gone to a wordpress blog and not seen an ad of some sort - even you have a link to a site where you are soliciting  paid work.

So although there are those that will froth at the mouth at the truth of it - a huge part and in fact the majority of the community is engaged in using wordpress in &quot;money grubbing business&quot;. No, that should not automatically argue that people should pay for designs but rather that being involved in business of some sort the wordpress community has a an additional business need to have unique looking sites and premium themes allows them a measure of that uniqueness for those who can&#039;t afford totally custom jobs.

What many on your side argue for is a situation where only the relatively affluent could achieve basic web site goals using wordpress. 

No offense but I often find that those championing against premium themes are those who do custom wordpres work without batting an eye.  They intend to share their designs and programming with no one but the paying client and then bristle that theme designers share their work with more of the community than their custom job ever will.

By any rational logic sharing a design with only one person is less helpful to a community that sharing it with 7 or 8 people.  I submit  that those arguing against premium themes should take a less hypocritical stance and also take a stand against closed custom jobs. Share it ALL with the community.

However should we even be able to go that route it would still violate the central need of a website to have a unique site for itself.

I guess the bright side is that I would have a great bit of eye candy that I could jack the css for with no qualms since it  would be GPL and clearly electronically distributed.</description>
		<content:encoded><![CDATA[<p>Often times in open source community there is this blind short sighted  commitment to everything being open and monetarily free even if the logical conclusion of that would be the detriment of the community&#8217;s real needs.  People don&#8217;t really take the time to think things through and fail to see the differences between software and artistic design.  </p>
<p>Software is made for replication. </p>
<p>The more people using a piece of software makes it stronger in the marketplace. Replication meets the goal of software to present a solution to a wide need.<br />
Design is entirely different.  A million people using the same exact Wordpress release empowers the commmunity &#8211; a million people using the same  exact design  would hinder the community and make it look like the software wasn&#8217;t capable of much creativity.</p>
<p>No matter how dishonest we may wish to be in a debate like this the facts are almost all of us want a site that looks as unique as we are able to achieve given our resources of time and capital. </p>
<p>Wordpress is a presentation piece of software and we don&#8217;t mind that. What we don&#8217;t want is for the presentation itself &#8211; our sites &#8211; to look exactly like a thousand other sites. </p>
<p>In other words what every web designer worthy of the title already knows is that the central need of the web site owner is not replication but creative uniqueness otherwise known in the business word as branding.</p>
<p>By very definition the only way to protect uniqueness is to limit its distribution.  Like it or not it meets a core need of the community.</p>
<p>The second error people make is that they tend to define the open source community in a way that excludes a large part of the community in favor of frankly people looking for a free ride and little else.  There is a HUGE portion of the wordpress community that is attempting to use wordpress for financial gain. I can&#8217;t remember the last time I have gone to a wordpress blog and not seen an ad of some sort &#8211; even you have a link to a site where you are soliciting  paid work.</p>
<p>So although there are those that will froth at the mouth at the truth of it &#8211; a huge part and in fact the majority of the community is engaged in using wordpress in &#8220;money grubbing business&#8221;. No, that should not automatically argue that people should pay for designs but rather that being involved in business of some sort the wordpress community has a an additional business need to have unique looking sites and premium themes allows them a measure of that uniqueness for those who can&#8217;t afford totally custom jobs.</p>
<p>What many on your side argue for is a situation where only the relatively affluent could achieve basic web site goals using wordpress. </p>
<p>No offense but I often find that those championing against premium themes are those who do custom wordpres work without batting an eye.  They intend to share their designs and programming with no one but the paying client and then bristle that theme designers share their work with more of the community than their custom job ever will.</p>
<p>By any rational logic sharing a design with only one person is less helpful to a community that sharing it with 7 or 8 people.  I submit  that those arguing against premium themes should take a less hypocritical stance and also take a stand against closed custom jobs. Share it ALL with the community.</p>
<p>However should we even be able to go that route it would still violate the central need of a website to have a unique site for itself.</p>
<p>I guess the bright side is that I would have a great bit of eye candy that I could jack the css for with no qualms since it  would be GPL and clearly electronically distributed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeC</title>
		<link>http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code/comment-page-1/#comment-10174</link>
		<dc:creator>MikeC</dc:creator>
		<pubDate>Mon, 14 Apr 2008 20:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress-plugins.feifei.us/10/wordpress-themes-are-gpl-code#comment-10174</guid>
		<description>Well you can be stubborn about it if you wish. Your privilege.  However your conceding a point or not isn&#039;t material. We don&#039;t get a vote in legal matters and your legal argument is flat. Nothing you have presented makes for a solid legal argument whereas the issues regarding copyright have been laid out pretty clearly through the years. The expression of a copyrighted design through a medium does not make the medium inventors copyright owners of the design.   If its my design when I sketch it then its my design when it is implemented.  

Incidentally if you think the design process is over with the sketch or PSD then you really don&#039;t understand web design  and the art of css and shouldn&#039;t be arguing for unfettered access to a process you don&#039;t understand.

Look, its really quite easy. If Matt and his supporters on this ever do try to push this idea it will blow up in their faces.  Remember what you said about companies and corporation using Wordpress and being free not to distribute their site design? Its false.

 If you argue that the CSS is part of the GPL then there is no site in which the design is not being distributed. The CSS is linked to it for full electronic access.  I could go to ANY site using Wordpress and access its linked CSS file and rip it to my hearts content (but remember by your argument it isn&#039;t ripping its me accessing a legitimately GPL design). Within a few months there would not be one unique designed wordpress design on the web.

I&#039;d give it a few years for most serious businesses to abandon wordpress as a viable business communication tool. Most that I know take a dim view of being unable to protect their unique look in the marketplace.

There is one more issue I&#039;d address before closing out this exchange if you don&#039;t mind and thats why designers aren&#039;t voiolating any community concepts by retaining their copyright to a design.</description>
		<content:encoded><![CDATA[<p>Well you can be stubborn about it if you wish. Your privilege.  However your conceding a point or not isn&#8217;t material. We don&#8217;t get a vote in legal matters and your legal argument is flat. Nothing you have presented makes for a solid legal argument whereas the issues regarding copyright have been laid out pretty clearly through the years. The expression of a copyrighted design through a medium does not make the medium inventors copyright owners of the design.   If its my design when I sketch it then its my design when it is implemented.  </p>
<p>Incidentally if you think the design process is over with the sketch or PSD then you really don&#8217;t understand web design  and the art of css and shouldn&#8217;t be arguing for unfettered access to a process you don&#8217;t understand.</p>
<p>Look, its really quite easy. If Matt and his supporters on this ever do try to push this idea it will blow up in their faces.  Remember what you said about companies and corporation using Wordpress and being free not to distribute their site design? Its false.</p>
<p> If you argue that the CSS is part of the GPL then there is no site in which the design is not being distributed. The CSS is linked to it for full electronic access.  I could go to ANY site using Wordpress and access its linked CSS file and rip it to my hearts content (but remember by your argument it isn&#8217;t ripping its me accessing a legitimately GPL design). Within a few months there would not be one unique designed wordpress design on the web.</p>
<p>I&#8217;d give it a few years for most serious businesses to abandon wordpress as a viable business communication tool. Most that I know take a dim view of being unable to protect their unique look in the marketplace.</p>
<p>There is one more issue I&#8217;d address before closing out this exchange if you don&#8217;t mind and thats why designers aren&#8217;t voiolating any community concepts by retaining their copyright to a design.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
