Licensing models, as options
This page is for designers deciding under which terms to sell. Each model is an option; none is recommended here, and the choice deserves a lawyer's review.
The models
| Model | Code | Assets | Money comes from | Risk |
|---|---|---|---|---|
| All GPL | GPL | GPL or Creative Commons | Services, convenience, trust | Others may resell the same files |
| GPL code, separate asset license | GPL | Your own terms (for example: use in the buyer's sites, no redistribution) | Copies with assets, services | The asset license must be clear and the theme must work without them |
| GPL plus a service agreement | GPL | Any of the above | Support, updates delivery, maintenance | Your time is the product |
| Proprietary | Your own terms | Your own terms | Copies | Templates and PHP that run inside a GPL program may be considered a derivative work; get legal advice first |
The package and RAD wizards can record each choice: GPL family, Creative Commons, and LicenseRef-Proprietary
(Choosing a license in the package wizard).
Questions that decide
- Do I want others to improve and share my theme? (GPL)
- Is my value in the files or in my time? (files: assets license or proprietary; time: services)
- Can I enforce a restriction at all, and is it worth it?
- What do my buyers' lawyers accept? (Many organizations prefer well-known licenses.)
Step by step
- Answer the four questions.
- Pick a model and write it as one sentence for the product page.
- Have a lawyer check the sentence and your terms.
- Put the license files into the theme (Licensing choices).
Related pages
- The GPL and selling
- Images and fonts under separate licenses
- Commercial terms next to the GPL
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.