[theme-reviewers] GPL and limiting usage

[Chip Bennett]

There is no "server side function set". ALL the code is contained in the
Plugin. The server connection is merely to determine if the payment
subscription is current, and if it isn't, code contained within the
distributed Plugin is disabled.

That is a usage restriction.


On Fri, Sep 20, 2013 at 3:32 PM, Dane Morgan <dane at danemorganmedia.com>wrote:

> So the code that was moved to a plugin *is* GPL and the keys just grant
> api type access between the code and a server side function set. In the
> same way that, for instance, akismet. If someone wanted to provide all of
> the data they could potentially set up their own server and achieve similar
> functionality without keeping a subscription?
>
>
> Otto wrote:
>
>> The concern here was originally that the "pro code" in question was in
>> the theme. Outside of the GPL, WordPress.org does not allow code to be
>> hosted in its repositories that requires payment to function. It's one
>> thing to connect to a service (even a paid one) to do something with
>> that service, but it's wholly another thing to have code that
>> otherwise works but which is simply "disabled" by the service until
>> payment is made.
>>
>> If you want to sell "code", then you host that code yourself. That was
>> the primary concern, and why I suggested they move that code into a
>> separate plugin.
>>
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130920/bb095a6d/attachment.html>