<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Know Your Licence</title>
	<link>http://menza.org/2006/12/know-your-licence</link>
	<description>^_^</description>
	<pubDate>Mon, 13 Oct 2008 20:12:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Gustaf</title>
		<link>http://menza.org/2006/12/know-your-licence#comment-6847</link>
		<dc:creator>Gustaf</dc:creator>
		<pubDate>Mon, 25 Dec 2006 00:47:42 +0000</pubDate>
		<guid>http://menza.org/2006/12/know-your-licence#comment-6847</guid>
		<description>While WP has every legal right to port it (as long as they act in accordance to the GPL), it might not have been the most morally sound decision. Especially not if  the "real author" explicitly asked that the theme would not be ported before the new drupal release.

I do however agree with -- what I read as -- the consensus of the post: you should never release something under a license that you do not know the ins and outs of.

And now to something completely different: The textarea is way too small :)</description>
		<content:encoded><![CDATA[<p>While WP has every legal right to port it (as long as they act in accordance to the GPL), it might not have been the most morally sound decision. Especially not if  the &#8220;real author&#8221; explicitly asked that the theme would not be ported before the new drupal release.</p>
<p>I do however agree with &#8212; what I read as &#8212; the consensus of the post: you should never release something under a license that you do not know the ins and outs of.</p>
<p>And now to something completely different: The textarea is way too small :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://menza.org/2006/12/know-your-licence#comment-6263</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 16 Dec 2006 03:00:27 +0000</pubDate>
		<guid>http://menza.org/2006/12/know-your-licence#comment-6263</guid>
		<description>"But a developer has every right to be notified if his work is going to be included in another work."

No they don't. People use WP code all the time and don't notify anyone.

"In summary I beleive that the WP.com developers showed no respect for the drupal developers by copying look and feel."

Actually it's a big compliment that we considered something in Drupal cool enough to want to use it. Most theme authors are thrilled when we put their theme on WP.com.

"Matt even claims credit for the theme in the wp.com dashboard."

Why on earth would I want to take credit for it? Over time what we've started doing is putting the link to the person who ported it as the author, because otherwise the original designer gets support questions about the WP theme which they didn't want. Anyone who uses the theme has names and links to the original designers very clearly in their footer. So our current policy (in core too) is to put person-doing-theme-updates in the style.css Author field and credit the designers in the notes and footer.

If I had said "Designed by Matt" and linked to my site, I could see your objection.</description>
		<content:encoded><![CDATA[<p>&#8220;But a developer has every right to be notified if his work is going to be included in another work.&#8221;</p>
<p>No they don&#8217;t. People use WP code all the time and don&#8217;t notify anyone.</p>
<p>&#8220;In summary I beleive that the WP.com developers showed no respect for the drupal developers by copying look and feel.&#8221;</p>
<p>Actually it&#8217;s a big compliment that we considered something in Drupal cool enough to want to use it. Most theme authors are thrilled when we put their theme on WP.com.</p>
<p>&#8220;Matt even claims credit for the theme in the wp.com dashboard.&#8221;</p>
<p>Why on earth would I want to take credit for it? Over time what we&#8217;ve started doing is putting the link to the person who ported it as the author, because otherwise the original designer gets support questions about the WP theme which they didn&#8217;t want. Anyone who uses the theme has names and links to the original designers very clearly in their footer. So our current policy (in core too) is to put person-doing-theme-updates in the style.css Author field and credit the designers in the notes and footer.</p>
<p>If I had said &#8220;Designed by Matt&#8221; and linked to my site, I could see your objection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: that girl again</title>
		<link>http://menza.org/2006/12/know-your-licence#comment-6260</link>
		<dc:creator>that girl again</dc:creator>
		<pubDate>Sat, 16 Dec 2006 01:15:42 +0000</pubDate>
		<guid>http://menza.org/2006/12/know-your-licence#comment-6260</guid>
		<description>The original designer was emailed by Automattic, asking for permission to port his theme to WP.

He asked them to hold off until Drupal 5 was released.

They went ahead and did it anyway. Matt even claims credit for the theme in the wp.com dashboard.

OK, so the GPL pretty much deprives you of any rights over the distribution and crediting of your work, but just because something's legal doesn't mean it's right. You have to be a pretty rabid fanboy to defend that behaviour, but fortunately for wordpress it has a lot of rabid fanboys who 'don't see the issue'.</description>
		<content:encoded><![CDATA[<p>The original designer was emailed by Automattic, asking for permission to port his theme to WP.</p>
<p>He asked them to hold off until Drupal 5 was released.</p>
<p>They went ahead and did it anyway. Matt even claims credit for the theme in the wp.com dashboard.</p>
<p>OK, so the GPL pretty much deprives you of any rights over the distribution and crediting of your work, but just because something&#8217;s legal doesn&#8217;t mean it&#8217;s right. You have to be a pretty rabid fanboy to defend that behaviour, but fortunately for wordpress it has a lot of rabid fanboys who &#8216;don&#8217;t see the issue&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lasse Havelund</title>
		<link>http://menza.org/2006/12/know-your-licence#comment-6239</link>
		<dc:creator>Lasse Havelund</dc:creator>
		<pubDate>Fri, 15 Dec 2006 19:45:04 +0000</pubDate>
		<guid>http://menza.org/2006/12/know-your-licence#comment-6239</guid>
		<description>It was most definitely public, as Matt notified wp-hackers before the theme was ever ported.
And the default theme of WordPress has been ported to a ton of other platforms.
Why would this be any different?

&lt;b&gt;Edit:&lt;/b&gt; &lt;a href=\"http://comox.textdrive.com/pipermail/wp-hackers/2006-December/009981.html\" rel=\"nofollow\" rel="nofollow"&gt;It seems&lt;/a&gt;, that Matt has already apologised, and the theme is disabled until Drupal 5 is released.
Nonetheless, I still don\'t see the issue.

&lt;b&gt;Edit 2:&lt;/b&gt; ...or not.</description>
		<content:encoded><![CDATA[<p>It was most definitely public, as Matt notified wp-hackers before the theme was ever ported.<br />
And the default theme of WordPress has been ported to a ton of other platforms.<br />
Why would this be any different?</p>
<p><b>Edit:</b> <a href=\"http://comox.textdrive.com/pipermail/wp-hackers/2006-December/009981.html\" rel=\"nofollow\" rel="nofollow">It seems</a>, that Matt has already apologised, and the theme is disabled until Drupal 5 is released.<br />
Nonetheless, I still don\&#8217;t see the issue.</p>
<p><b>Edit 2:</b> &#8230;or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: themak</title>
		<link>http://menza.org/2006/12/know-your-licence#comment-6238</link>
		<dc:creator>themak</dc:creator>
		<pubDate>Fri, 15 Dec 2006 19:19:24 +0000</pubDate>
		<guid>http://menza.org/2006/12/know-your-licence#comment-6238</guid>
		<description>Pretty much no.

Technically he has every right to port the theme to wp. But a developer has every right to be notified if his work is going to be included in another work.  

Also this theme was supposed to be a suprise, so there is a good chance that it wasn't in a public SVN and thus might not be GPL. 

In summary I beleive that the WP.com developers showed no respect for the drupal developers by copying look and feel. In a world where people encourage there ip to be used to foster creativity it paramount to respect certain aspects of creativity and timing.</description>
		<content:encoded><![CDATA[<p>Pretty much no.</p>
<p>Technically he has every right to port the theme to wp. But a developer has every right to be notified if his work is going to be included in another work.  </p>
<p>Also this theme was supposed to be a suprise, so there is a good chance that it wasn&#8217;t in a public SVN and thus might not be GPL. </p>
<p>In summary I beleive that the WP.com developers showed no respect for the drupal developers by copying look and feel. In a world where people encourage there ip to be used to foster creativity it paramount to respect certain aspects of creativity and timing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
