<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Brilliant. Thank you
@Justin.<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:523CBF1E.20305@justintadlock.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="justin@justintadlock.com" photoname="Justin Tadlock"
src="cid:part1.08010205.02020801@danemorganmedia.com"
name="postbox-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:justin@justintadlock.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Justin Tadlock</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Friday, September
20, 2013 16:33</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div id="markdown-here-wrapper-89391" class="markdown-here-wrapper"
data-md-original="I think some of you are
misunderstanding what the GPL is about. It's about
licensing what you're allowed to do with the code, not about
licensing what happens when you actually run the code.
Here's a quick theme for
you:<br><br>`style.css`:<br><br>
/*<br> Theme Name:
Test<br> License: GPL
v2+<br>
*/<br><br>`index.php`:<br><br>
<?php wp_die( 'Your site broke!' );
?><br><br>That would restrict a user's ability
to use WordPress, but I licensed it under the GPL.
Therefore, it does not restrict the user's ability to use, copy,
modify, or distribute the code.<br><br>When we talk
about the ability to "use" the code, it's not about
whether the code works in a certain way for whatever
application. You have the ability to use it (the code)
how you see fit with no added restrictions.
<br><br>Just to make things a little clearer, make
sure you understand this particular line from the
[GPL](http://www.gnu.org/licenses/gpl-2.0.html):<br><br>>
"Activities other than copying, distribution and modification
are not covered by this License; they are outside its
scope."<br><br>Is Pagelines placing any
additional restrictions on those items listed from the
GPL?<br><br>The only things I'm concerned with were
stated in my previous email about policy on blocking features
within a theme that WordPress.org
hosts.<br><br><div
class="moz-cite-prefix">On 9/20/2013 4:01 PM, Ünsal
Korkmaz wrote:<br></div><blockquote
cite="mid:CABZBZDse1fQRzWTiF3ZLpyfCmF2NP5+5y30G+uPEr67ommkokg@mail.gmail.com"
type="cite"><div dir="ltr">I am not
expert on GPL but if i cant use a code in WordPress Multisite
because of a license or code restriction (not talking about
multisite compatible), its not GPL in my eyes.. even author can
say its gpl code.. <div>
<br></div><div><strong
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px">preserve,
protect and promote the freedom to use, study, copy, modify, and
redistribute computer software, and to defend the rights of Free
Software users. </strong><span
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px">from </span><a
moz-do-not-send="true"
href="http://www.gnu.org/">http://www.gnu.org/</a><br>
</div><div><br></div><div>And
yes, we cant use this theme/plugin/whatever in multisite if not
developer licensed: <a
moz-do-not-send="true"
href="http://www.pagelines.com/pricing/">http://www.pagelines.com/pricing/</a></div><div><strong
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px"><br>
</strong></div></div><div
class="gmail_extra"><br><br><div
class="gmail_quote">On Fri, Sep 20, 2013 at 11:49 PM,
Otto <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:otto@ottodestruct.com"
target="_blank">otto@ottodestruct.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div class="im">On
Fri, Sep 20, 2013 at 3:38 PM, Trent Lapinski <<a
moz-do-not-send="true"
href="mailto:trent@cyberchimps.com">trent@cyberchimps.com</a>>
wrote:<br>
>> If the copyright holder says that the terms are
GPL, then the terms<br>
>> are GPL. Period. No magic coding trickery can
make it "incompatible"<br>
>> with those terms.<br>
><br>
</div><div class="im">> Just because
you claim something is GPL does not make it true.<br>
<br>
</div>If you are the copyright holder, because you *wrote
the damn thing*,<br>
then it absolutely does make it true. Every single time, without
fail.<br>
<br>
Only the copyright holder has the power to license the work.
That's<br>
the whole point of copyright.<br>
<div class="im"><br>
<br>
> There are plenty of people who release code under the GPL
and violate the terms, and there have been several lawsuits on
this matter. <a moz-do-not-send="true"
href="http://www.gnu.org/licenses/gpl-violation.html"
target="_blank">http://www.gnu.org/licenses/gpl-violation.html</a><br>
><br>
>
The GPL is not the same as copyright, there is no inherent law
granting you the right. If you release something under the GPL
that is not GPL compatible, it is a GPL violation and you lose the
privilege to claim your code is GPL compatible.<br>
<br>
</div>This is so wrong that I honestly don't know where to
start.<br>
<br>
Time for quick copyright school lessons:<br>
- The creator of a work gets the copyright to that work. This
gives<br>
them all the rights to it. Nobody else has any rights to it at
all.<br>
- The copyright holder can give those rights to others. They can
do it<br>
freely, or make it subject to conditions. The conditions are
called<br>
the "license".<br>
- The GPL is a license like any other. It is the contract by which
the<br>
copyright holder gives you, the person with no rights, the ability
to<br>
exercise those rights from the copyright holder.<br>
- The copyright holder cannot violate their own license. The
very<br>
notion of this fundamentally misunderstands how licenses work.
The<br>
license applies to you and everybody else. Not to them.<br>
<div class="im"><br>
<br>
> If you look at the violations page, one of the questions
to determine if there is a violation is: "Is the available
source code complete, or is it designed for linking in other
non-free modules?"<br>
><br>
> This is exactly what we're discussing.<br>
<br>
</div>Violations can only occur to licensees. Not to the
licensor.<br>
<div class="im"><br>
<br>
<br>
> PageLines is releasing a supposedly GPL compatible theme
linking to a plugin that forces users to pay a subscription
validated through the use of a priority API to use supposedly GPL
compatible code. This is a violation of the GPL and renders both
the theme and plugin as non-compatible with the GPL, and WPORG
policy.<br>
<br>
</div>This has no bearing on the GPL in any way whatsoever.
The theme/plugin<br>
are licensed under the GPL because *their author says so*. That's
the<br>
end of it, really.<br>
<br>
Whether it violates policy or not is a fair debate. I say it does
not.<br>
<div class="im"><br>
<br>
> When it comes to policy on .org, the question is do we
allow themes or plugins to upsell priority non-GPL themes and
plugins? The answer as I understood it was a resounding no. You
yourself said this is not allowed, so I'm not sure why you're
claiming this situation is different then what it is.<br>
<br>
</div>The issue isn't about "non-GPL". If they say
it's GPL, then I accept<br>
that, and it's GPL. Done.<br>
<div class="im"><br>
<br>
>> Now, the review requirements go far beyond GPL,
and that's fair<br>
>> enough. But there is no real case where you would
ever need to "modify<br>
>> a pro theme heavily" to be GPL-Compatible.
Whoever told you that this<br>
>> was the reason was mistaken.<br>
><br>
> Actually they weren't wrong. This has been WPORG policy
for over 3 years now as Chip mentioned.<br>
<br>
</div>If the theme review team has been incorrectly
interpreting the GPL and<br>
using it in a mistaken way, then I'm very saddened by that, and
I<br>
offer my assistance to correct and educate the team in any way
that I<br>
can.<br>
<div class="HOEnZb"><div
class="h5"><br>
-Otto<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a
moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>
<br><fieldset
class="mimeAttachmentHeader"></fieldset><br><pre
wrap="">_______________________________________________
theme-reviewers
mailing list
theme-reviewers@lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers
</pre>
</blockquote><br>" style="">
<p style="margin: 1.2em 0px ! important;">I think some of you are
misunderstanding what the GPL is about. It‘s about licensing
what you’re allowed to do with the code, not about licensing
what happens when you actually run the code. Here's a quick
theme for you:</p>
<p style="margin: 1.2em 0px ! important;"><code style="font-size:
0.85em; font-family:
Consolas,Inconsolata,Courier,monospace;margin: 0px 0.15em;
padding: 0px 0.3em; white-space: pre-wrap; border: 1px solid
rgb(234, 234, 234); background-color: rgb(248, 248, 248);
border-radius: 3px 3px 3px 3px; display: inline;">style.css</code>:</p>
<div><code style="font-size: 0.85em; font-family:
Consolas,Inconsolata,Courier,monospace;margin: 0px 0.15em; padding: 0px
0.3em; white-space: pre-wrap; border: 1px solid rgb(234, 234, 234);
background-color: rgb(248, 248, 248); border-radius: 3px 3px 3px 3px;
display: inline;white-space: pre; overflow: auto; border-radius: 3px 3px
3px 3px; border: 1px solid rgb(204, 204, 204); padding: 0.5em
0.7em;display: block; padding: 0.5em; color: rgb(51, 51, 51);
background: none repeat scroll 0% 0% rgb(248, 248, 255);">/*<br>Theme
Name: Test<br>License: GPL v2+<br>*/</code></div>
<p style="margin: 1.2em 0px ! important;"><code style="font-size:
0.85em; font-family:
Consolas,Inconsolata,Courier,monospace;margin: 0px 0.15em;
padding: 0px 0.3em; white-space: pre-wrap; border: 1px solid
rgb(234, 234, 234); background-color: rgb(248, 248, 248);
border-radius: 3px 3px 3px 3px; display: inline;">index.php</code>:</p>
<div><code style="font-size: 0.85em; font-family:
Consolas,Inconsolata,Courier,monospace;margin: 0px 0.15em; padding: 0px
0.3em; white-space: pre-wrap; border: 1px solid rgb(234, 234, 234);
background-color: rgb(248, 248, 248); border-radius: 3px 3px 3px 3px;
display: inline;white-space: pre; overflow: auto; border-radius: 3px 3px
3px 3px; border: 1px solid rgb(204, 204, 204); padding: 0.5em
0.7em;display: block; padding: 0.5em; color: rgb(51, 51, 51);
background: none repeat scroll 0% 0% rgb(248, 248, 255);"><?php
wp_die( 'Your site broke!' ); ?></code></div>
<p style="margin: 1.2em 0px ! important;">That would restrict a
user‘s ability to use WordPress, but I licensed it under the
GPL. Therefore, it does not restrict the user’s ability to use,
copy, modify, or distribute the code.</p>
<p style="margin: 1.2em 0px ! important;">When we talk about the
ability to “use” the code, it's not about whether the code works
in a certain way for whatever application. You have the ability
to use it (the code) how you see fit with no added restrictions.
</p>
<p style="margin: 1.2em 0px ! important;">Just to make things a
little clearer, make sure you understand this particular line
from the <a moz-do-not-send="true"
href="http://www.gnu.org/licenses/gpl-2.0.html">GPL</a>:</p>
<p style="margin: 1.2em 0px ! important;">Is Pagelines placing any
additional restrictions on those items listed from the GPL?</p>
<p style="margin: 1.2em 0px ! important;">The only things I'm
concerned with were stated in my previous email about policy on
blocking features within a theme that WordPress.org hosts.</p>
<p style="margin: 1.2em 0px ! important;">On 9/20/2013 4:01 PM,
Ünsal Korkmaz wrote:</p>
<div class="markdown-here-exclude">
</div>
</div>
<div>_______________________________________________<br>theme-reviewers
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br><a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="unsalkorkmaz@gmail.com" photoname="Ünsal Korkmaz"
src="cid:part2.00010506.08070809@danemorganmedia.com"
name="postbox-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:unsalkorkmaz@gmail.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Ünsal Korkmaz</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Friday, September
20, 2013 16:01</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div dir="ltr">I am not expert
on GPL but if i cant use a code in WordPress Multisite because of a
license or code restriction (not talking about multisite compatible),
its not GPL in my eyes.. even author can say its gpl code.. <div>
<br></div><div><strong
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px">preserve,
protect and promote the freedom to use, study, copy, modify, and
redistribute computer software, and to defend the rights of Free
Software users. </strong><span
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px">from </span><a
moz-do-not-send="true" href="http://www.gnu.org/">http://www.gnu.org/</a><br>
</div><div><br></div><div>And yes, we cant use this
theme/plugin/whatever in multisite if not developer licensed: <a
moz-do-not-send="true" href="http://www.pagelines.com/pricing/">http://www.pagelines.com/pricing/</a></div><div><strong
style="color:rgb(53,56,42);font-family:sans-serif;font-size:13px"><br>
</strong></div></div><div class="gmail_extra"><br><br><br></div>
<div>_______________________________________________<br>theme-reviewers
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br><a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="otto@ottodestruct.com" photoname="Otto"
src="cid:part3.08080101.09070806@danemorganmedia.com"
name="postbox-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:otto@ottodestruct.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Otto</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Friday, September
20, 2013 15:49</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><pre wrap="">On Fri, Sep 20, 2013 at 3:38 PM, Trent Lapinski <a class="moz-txt-link-rfc2396E" href="mailto:trent@cyberchimps.com"><trent@cyberchimps.com></a> wrote:
</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">If the copyright holder says that the terms are GPL, then the terms
are GPL. Period. No magic coding trickery can make it "incompatible"
with those terms.
</pre></blockquote><pre wrap="">Just because you claim something is GPL does not make it true.
</pre></blockquote><pre wrap=""><!---->
If you are the copyright holder, because you *wrote the damn thing*,
then it absolutely does make it true. Every single time, without fail.
Only the copyright holder has the power to license the work. That's
the whole point of copyright.
</pre><blockquote type="cite"><pre wrap="">There are plenty of people who release code under the GPL and violate the terms, and there have been several lawsuits on this matter. <a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/gpl-violation.html">http://www.gnu.org/licenses/gpl-violation.html</a>
The GPL is not the same as copyright, there is no inherent law granting you the right. If you release something under the GPL that is not GPL compatible, it is a GPL violation and you lose the privilege to claim your code is GPL compatible.
</pre></blockquote><pre wrap=""><!---->
This is so wrong that I honestly don't know where to start.
Time for quick copyright school lessons:
- The creator of a work gets the copyright to that work. This gives
them all the rights to it. Nobody else has any rights to it at all.
- The copyright holder can give those rights to others. They can do it
freely, or make it subject to conditions. The conditions are called
the "license".
- The GPL is a license like any other. It is the contract by which the
copyright holder gives you, the person with no rights, the ability to
exercise those rights from the copyright holder.
- The copyright holder cannot violate their own license. The very
notion of this fundamentally misunderstands how licenses work. The
license applies to you and everybody else. Not to them.
</pre><blockquote type="cite"><pre wrap="">If you look at the violations page, one of the questions to determine if there is a violation is: "Is the available source code complete, or is it designed for linking in other non-free modules?"
This is exactly what we're discussing.
</pre></blockquote><pre wrap=""><!---->
Violations can only occur to licensees. Not to the licensor.
</pre><blockquote type="cite"><pre wrap="">PageLines is releasing a supposedly GPL compatible theme linking to a plugin that forces users to pay a subscription validated through the use of a priority API to use supposedly GPL compatible code. This is a violation of the GPL and renders both the theme and plugin as non-compatible with the GPL, and WPORG policy.
</pre></blockquote><pre wrap=""><!---->
This has no bearing on the GPL in any way whatsoever. The theme/plugin
are licensed under the GPL because *their author says so*. That's the
end of it, really.
Whether it violates policy or not is a fair debate. I say it does not.
</pre><blockquote type="cite"><pre wrap="">When it comes to policy on .org, the question is do we allow themes or plugins to upsell priority non-GPL themes and plugins? The answer as I understood it was a resounding no. You yourself said this is not allowed, so I'm not sure why you're claiming this situation is different then what it is.
</pre></blockquote><pre wrap=""><!---->
The issue isn't about "non-GPL". If they say it's GPL, then I accept
that, and it's GPL. Done.
</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Now, the review requirements go far beyond GPL, and that's fair
enough. But there is no real case where you would ever need to "modify
a pro theme heavily" to be GPL-Compatible. Whoever told you that this
was the reason was mistaken.
</pre></blockquote><pre wrap="">Actually they weren't wrong. This has been WPORG policy for over 3 years now as Chip mentioned.
</pre></blockquote><pre wrap=""><!---->
If the theme review team has been incorrectly interpreting the GPL and
using it in a mistaken way, then I'm very saddened by that, and I
offer my assistance to correct and educate the team in any way that I
can.
-Otto
_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="trent@cyberchimps.com" photoname="Trent Lapinski"
src="cid:part4.08090600.06020003@danemorganmedia.com"
name="postbox-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:trent@cyberchimps.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Trent Lapinski</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Friday, September
20, 2013 15:38</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><blockquote type="cite"><pre wrap="">If the copyright holder says that the terms are GPL, then the terms
are GPL. Period. No magic coding trickery can make it "incompatible"
with those terms.
</pre></blockquote><pre wrap=""><!---->
Just because you claim something is GPL does not make it true.
There are plenty of people who release code under the GPL and violate the terms, and there have been several lawsuits on this matter. <a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/gpl-violation.html">http://www.gnu.org/licenses/gpl-violation.html</a>
The GPL is not the same as copyright, there is no inherent law granting you the right. If you release something under the GPL that is not GPL compatible, it is a GPL violation and you lose the privilege to claim your code is GPL compatible.
If you look at the violations page, one of the questions to determine if there is a violation is: "Is the available source code complete, or is it designed for linking in other non-free modules?"
This is exactly what we're discussing.
PageLines is releasing a supposedly GPL compatible theme linking to a plugin that forces users to pay a subscription validated through the use of a priority API to use supposedly GPL compatible code. This is a violation of the GPL and renders both the theme and plugin as non-compatible with the GPL, and WPORG policy.
When it comes to policy on .org, the question is do we allow themes or plugins to upsell priority non-GPL themes and plugins? The answer as I understood it was a resounding no. You yourself said this is not allowed, so I'm not sure why you're claiming this situation is different then what it is.
</pre><blockquote type="cite"><pre wrap="">Now, the review requirements go far beyond GPL, and that's fair
enough. But there is no real case where you would ever need to "modify
a pro theme heavily" to be GPL-Compatible. Whoever told you that this
was the reason was mistaken.
</pre></blockquote><pre wrap=""><!---->
Actually they weren't wrong. This has been WPORG policy for over 3 years now as Chip mentioned.
--Trent Lapinski
=============
CEO of CyberChimps Inc
On Sep 20, 2013, at 1:01 PM, Otto <a class="moz-txt-link-rfc2396E" href="mailto:otto@ottodestruct.com"><otto@ottodestruct.com></a> wrote:
</pre><blockquote type="cite"><pre wrap="">If the copyright holder says that the terms are GPL, then the terms
are GPL. Period. No magic coding trickery can make it "incompatible"
with those terms.
-Otto
_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre></blockquote><pre wrap=""><!---->
_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="otto@ottodestruct.com" photoname="Otto"
src="cid:part3.08080101.09070806@danemorganmedia.com"
name="postbox-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:otto@ottodestruct.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Otto</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Friday, September
20, 2013 15:01</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div><!----><br>You throw
around the term "GPL-compatible" pretty freely, but I don't<br>think you
really understand what it is that you're saying here.<br><br>*Code
cannot be incompatible with the GPL*.<br>Ever.<br>Period.<br><br>Only
other licenses can be incompatible with the GPL. Code is just<br>code.
It cannot be "incompatible" with a legal document.<br><br>If I write a
piece of code that only works on my computer (using<br>whatever method I
like) and release that code, then I can release it<br>under the terms
of the GPL. Those are the terms for the code. The code<br>itself is
useless to anybody not using my computer, but that does not<br>matter.
Those are still the terms.<br><br>If the copyright holder says that the
terms are GPL, then the terms<br>are GPL. Period. No magic coding
trickery can make it "incompatible"<br>with those terms.<br><br>-Otto<br>_______________________________________________<br>theme-reviewers
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br><a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br></div></div>
</blockquote>
</body></html>