Licensing model for plugins in repository

  • Hello!

    My plugin is almost ready to be published so I have to think about licensing and selling. I intend to host it in the WordPress repository – so, as I read, it must be licensed under the GPLv2. I am ok with that, as long as its compliant with what I thought of to be the business-model:

    1. All functionality of my plugin shall be free for everyone – now and forever.

    2. Anyway, buying and entering a key would allow to toggle the plugin’s name-branding in the backend on and off.

    The name-branding is very subtle and it can even be useful since it shows which table-columns have been added, for example. Anyway, if you setup a WordPress installation for a client, you would probably want to turn those brandings off to give the backend an unified look.

    The model for selling keys would be easy, too: One low-priced key for one installation at a time, movable to another installation, valid forever. The key does not come with any service, warranty or upgrade guarantee.

    Do you think this is still okay with the GPL and WordPress plugin repository guidelines? If not, could you recommend other models for licensing plugins?

    Edit: I want to disable the key-feature first until I am sure the plugin is rock-solid. People submitting valid issues on the development board will get a key for free ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator cubecolour

    (@numeeja)

    The guidelines for what is and is not acceptable are published at https://www.ads-software.com/plugins/about/guidelines/

    I believe what you have suggested would not be allowed under point (5) of these guidelines.

    If you want to sell advanced features for a plugin (such as a “pro” version), then you must sell and serve that code from your own site, we will not host it on our servers.

    Additionally see points (7) & (10) which may also have some relevance.

    Thread Starter Jonathan Weber

    (@jonathanweber)

    Thank you! Even though I would not really provide trialware, I would still request a key to unlock one feature which is, as you say, against the guidelines. Nevertheless I think that this is close at the border to “trying to upsell”, since I am not adding or removing real functionality but only the “upselling advertisement” – which itself is okay, according to point 5. I think there are plugins in the repository that have a much more aggressive approach than the one I aim for…

    Anyway, thank you very much for your thoughts on this!
    Greetings

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Up selling in plugins is fine provide you maintain a subjectively defined limit on how you do that.

    Give this WP Tavern post a read and (wait for it!) the comments.

    https://wptavern.com/whats-your-limit-of-advertising-and-upselling-in-free-wordpress-plugins

    Many plugins up sell there services as well as WordPress related offers. When the plugin crosses a line (and that is subjective, how could it be otherwise?) then the plugin author gets a tap on the shoulder when reported.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Licensing model for plugins in repository’ is closed to new replies.

Tags