Finalizing WP Plugin Kit, Have a few questions.

Hello,

I am finishing up a new WordPress Plugin Development Kit/Framework. Going to submit the kit to the market place before Monday.

It includes professional admin designs with options. The plugin includes a plugin-core that makes it A LOT easier to develop a plugin. It’s actually a framework that I designed to work similarly to CodeIgniter. There’s a lot of helper functions to do stuff like version checking API , automatic updates, short codes, drop-down menus, etc… Aside from the helpers, the code is OOP .

Sample code: $this->load->helper(‘common_helper’); $vars = array(‘name’ => ‘Daniel Cronin’); $this->load->view(‘admin_index’, $vars); $this->load->js(‘plugin_admin.js’, array(‘jquery’));

A lot of features are auto-loaded or easily configurable. I’m also going to include templates for documentation, tutorial videos (Introduction, How to Build a Plugin in under 5 Minutes, Documentation Overview), and other assets for developers.

I’ve been developing plugins for customers. Typically it pays $200-$500 for a plugin. Using this plugin kit it saves all the time you spend creating the admin, design, and trying to understand the WP Codex. I’m really hoping that the kit will save time, and make everyone more money.

Questions: 1.) I know that there will be three common usages. —a.) One-time plugin for a customer (The regular license covers this) —b.) Use the kit to develop plugins for multiple customers (The extended license covers this) —c.) To build a plugin for resale (on the Envato market place, or elsewhere) (There’s no license for this)

For anyone who purchases the extended license, I would like to give limited permission for resale of the resulting plugin.

The conditions are: 1.) The resulting plugin is not a plugin generation kit. (Basically, I don’t want people to buy their plugin just for the plugin development kit code.) 2.) The resulting plugin MUST be sold exclusively on the Envato Marketplace. I think this is fair. 3.) The plugin-core must not be modified. This is to ensure that the plugin will not conflict with other plugins that use the same core.

All the work in the development kit is either Public Domain (no attribution) or created by me.

In the future, I want to release other plugins that use the core, as well as libraries/helpers/themes that can be purchased that work with the kit.

I’m not sure how I can license the development kit. Can I just write the added license agreement to the product page? Can I even release my code with this sort of license?

2.) I want to allow anyone to create an extension (library/helper/theme) for the plugin development kit without having to purchase an extended license. As long as they do not include any of the plugin development kit (the code must be sold independently).

Also, if they want to write an extended library, they can give it away for free. Again, as long as they do not include the development kit code.

What do I need to do to make this possible?

My goal for the kit is just to make life easier for developers, and to make it profitable. But the kit is way more useful (and profitable) for developers if they can create a marketable product.

Best regards, Daniel