Perfect!<br><br><div class="gmail_quote">On 16 August 2012 12:10, Chandra Maharzan <span dir="ltr"><<a href="mailto:maharzan@gmail.com" target="_blank">maharzan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you Otto for clarifying on the ticket. This guy can't stop<br>
discussing. I love your last comment. :)<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Aug 16, 2012 at 9:23 PM, Chandra Maharzan <<a href="mailto:maharzan@gmail.com">maharzan@gmail.com</a>> wrote:<br>
> Perhaps, you can add this in the REQUIRED points in the review<br>
> guidelines. This guy was always arguing about this was not REQUIRED<br>
> and that was not required whenever I was trying to explain for a<br>
> better code quality/features that <a href="http://wp.org" target="_blank">wp.org</a> hosts.<br>
><br>
> On Thu, Aug 16, 2012 at 9:18 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>> Yes, that's an important distinction, and clarifies why what this Theme was<br>
>> doing is not acceptable.<br>
>><br>
>> Normally, an "upsell" Theme will promote a *separate*, commercial version of<br>
>> a Theme, that includes the code for additional functionality. What this<br>
>> Theme is doing is putting the functionality in the free version, and then<br>
>> *crippling* that functionality by requiring an "activation key".<br>
>><br>
>> Chip<br>
>><br>
>><br>
>> On Thu, Aug 16, 2012 at 10:29 AM, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
>>><br>
>>> On Thu, Aug 16, 2012 at 10:17 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
>>> wrote:<br>
>>> > The Theme has to be fully functional out-of-the-box (i.e. it can't be<br>
>>> > "crippleware"). The Theme cannot put core WordPress functionality behind<br>
>>> > a<br>
>>> > paywall.<br>
>>> ><br>
>>> > A Theme can put *additional* options behind a paywall. For example, a<br>
>>> > Theme<br>
>>> > can't put all dynamic sidebars behind the paywall, but a Theme can have<br>
>>> > one<br>
>>> > or more dynamic sidebars in the free version, and then add *additional*<br>
>>> > dynamic sidebars in the commercial version.<br>
>>><br>
>>> A theme in our directory cannot put *any functionality that is<br>
>>> contained entirely within the theme* behind a paywall.<br>
>>><br>
>>> If somebody wants to sell code, then they should sell that code<br>
>>> separately and elsewhere.<br>
>>><br>
>>> The themes on WordPress.org are free. If somebody is putting in<br>
>>> payment gateways in them to just "turn on" some piece of that theme,<br>
>>> then no, that is absolutely not allowed.<br>
>>><br>
>>> If it's in our repo, then it must be free and non-crippled. If you<br>
>>> want to sell it, then it shouldn't be in our repo.<br>
>>><br>
>>> -Otto<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>
>><br>
>><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>
><br>
><br>
><br>
> --<br>
> cmans<br>
<br>
<br>
<br>
--<br>
cmans<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>
</div></div></blockquote></div><br>