<div dir="ltr">Yes and no. Like I said: it's not something that we investigate with any special diligence. But it's not about the linkage. If we know about it, simply removing the link doesn't resolve the issue.<div>
<br></div><div>Say Joe Developer sells Themes on TF under the Regular License. Joe Developer then submits a Theme to WPORG, and his ThemeURI has a banner ad for his TF offerings. The reviewer notes the licensing issue with the TF-offered Themes. Joe Developer then simply removing the TF link from the ThemeURI page wouldn't allow the Theme to be approved for WPORG. Joe Developer would have to re-license his TF-offered WordPress Themes as 100% GPL.</div>
<div><br></div><div>So, the TL:DR:</div><div><br></div><div>1) It's a matter of WORG policy regarding licensing</div><div>2) If we know about it, we have to act accordingly</div><div>3) While I fully support the WPORG policy, I think Theme Reviewers have far more important and value-added things to do than dig several degrees of separation for licensing issues; so,</div>
<div>4) We're not going to look for it any more diligently than any other licensing issue, so if someone actively tries to segregate TF offerings from WPORG offerings, it's very likely we won't notice it.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 28, 2013 at 3:48 PM, Japheth Thomson <span dir="ltr"><<a href="mailto:japh@envato.com" target="_blank">japh@envato.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ah, I think I'm with you now:<div><br></div><div>So two completely separate themes, one on WP.org and one on TF.net, that don't link to each other in any way = fine.</div>
<div><br></div><div>Linking to TF.net somehow via a WP.org theme = not fine.</div>
<div><br></div><div>Right?</div><div><br></div><div>Cheers,</div><div>Japh</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 29 July 2013 05:46, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Japh,<div><br></div><div>Yes, for as long as I can remember. To be honest, it's not something that we spent a lot of time investigating, but before Envato introduced the 100% GPL license option, if someone advertised their ThemeForest-hosted Themes or Plugins from ThemeURI or AuthorURI, we would have to "not-approve" the Theme, as a matter of WPORG policy.</div>
<div><br></div><div>(That's why I was one of the biggest fans of the move to offer a 100% GPL license, so that the issue could go away.)</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div>
On Sun, Jul 28, 2013 at 3:40 PM, Japheth Thomson <span dir="ltr"><<a href="mailto:japh@envato.com" target="_blank">japh@envato.com</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Chip,<div><br></div><div>Did I read you correctly there? Are you saying that if someone is selling themes or plugins on ThemeForest or CodeCanyon, they must use the 100% GPL license, otherwise they are not allowed to also distribute other themes on WordPress.org?</div>
<div><br></div><div>Has that been the rule for long?</div><div><br></div><div>Cheers,</div><div>Japh</div><div><br></div></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On 29 July 2013 05:33, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If you host on <a href="http://wordpress.org" target="_blank">wordpress.org</a>, any Themes or Plugins that you sell on ThemeForest must be distributed under the ThemeForest 100% GPL license. Other than that, the usual commercial/up-sell Theme guidelines apply.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Sun, Jul 28, 2013 at 2:08 PM, Ünsal Korkmaz <span dir="ltr"><<a href="mailto:unsalkorkmaz@gmail.com" target="_blank">unsalkorkmaz@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi,<div>I am preparing to release my first commercial child theme that using <a href="http://wordpress.org/themes/firmasite" target="_blank">FirmaSite</a> as parent theme. </div>
<div>FirmaSite theme's support & information site is <a href="http://theme.firmasite.com" target="_blank">http://theme.firmasite.com</a></div>
<div>I will put commercial child theme to ThemeForest as gpl theme. My questions are;</div><div><ul><li>Is there any restriction on this? </li><li>Can i put a page on <a href="http://theme.firmasite.com" target="_blank">http://theme.firmasite.com</a> about this commercial child-theme?</li>
<li>Can i put link to ThemeForest in commercial child-theme's page?</li></ul><div><br></div></div><div>( Sorry if its unrelated to this mail list )</div>
<br></div></div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br>Japh Thomson<br>WordPress Evangelist<br><a href="http://wp.envato.com" target="_blank">http://wp.envato.com</a><div>
<a href="http://twitter.com/envato" target="_blank">http://twitter.com/envato</a><br>
<br></div>
</font></span></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Japh Thomson<br>WordPress Evangelist<br><a href="http://wp.envato.com" target="_blank">http://wp.envato.com</a><div><a href="http://twitter.com/envato" target="_blank">http://twitter.com/envato</a><br>
<br></div>
</div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>