- Kabuki Strong Source-available License - An open-source license designed to protect your copyright rights, sole monetization by the IP Owner, and forces users to donate back any improvements. It features a clause that allows for commercial use under a separate paid license from your website agreed upon before download, facilitating one-time donations, closed-source Software-as-a-Service, and avoiding app store fees. Use this license if you need to prevent others from profiting from your open-source products and books without paying you.
- Kabuki Weak Source-available License - An open-source license designed to provide the most protection to free-to-use projects from Open-source Theft from predatorial companies and individuals by granting free personal licenses with an instant termination clause for anyone engaging in Open-source theft. The license additionally allows those affected by the license restriction to purchase a license through a designated website. Use this license if you want the open-source to be used by end-users for commercial purposes without donating improvements.
- Kabuki Strong Source-closed License - A closed-source license designed to maximize your legal rights by protecting your copyright under a trade secret common law provision. This is the license generally recommended for products/businesses that do not sub-license their products.
- Kabuki Weak Source-closed License - A closed-source license designed to protect your copyright rights only and attempt to keep your IP confidential. Use this license if you are sub-licensing your product.
Traditional open-source licenses have a variety of ups and downs that must be weighed by each project founder and maintainer. Most developers pick a license because they feel like they like the idea of one camp over the other, but all traditional licenses suffer the same failure: they're all susceptible to big tech takeovers because the license didn't protect themselves from Open-source Theft, closed-source Software-as-a-Service, and the license aren't successful at creating a sales funnel. Companies such as Amazon that have virtually endless pockets can take over projects with traditional licenses like GPL, Apache License, MIT, BSD, etc by tactics such as paying contributors the open-source project becomes dependent on, then taking over a project's development community by sheer numbers and creating forks of the project then shifting the development to their own project, and ultimately making the profits off of your project through their unfair AWs market dominance while you get nothing. Nothing is stopping a company from using your open-source briefly to create a competitors and shifting your users to their closed-source Software-as-a-Service.
Source-available licenses fix these problems
To use this license, create a ReadMe.md file in every folder of your repository and copy and paste the License section into every markdown file in your repository. In your source code, place the Doxygen header in each one of your source code files.
Copyright ©2019-22 Kabuki Starship™; all rights reserved.