I need a pure OSS (open source) version of my product; however for certain customers, I also need to offer commercial licensing with no LGPL components. What should I do?
In this situation, purchase Pro or better licenses, but ship only LGPL functionality as part of your product. This allows you to offer either LGPL or commercial terms for the SmartClient component of your overall product. Note this approach still allows you to use the tools from the commercial project, such as Visual Builder and its DataSource Wizards. So long as the product you ship includes only the LGPL runtime, you can still offer customers a 100% OSS version of your product. You can alternatively ship two versions of your product, one pure OSS product incorporating only the SmartClient LGPL runtime, and a second non-OSS product with extended features based on commercial versions of SmartClient. For example, the non-OSS version of your product could offer richer export options, or offer Analytics capabilities based on the SmartClient Analytics module.
Related Questions
- I want to offer product on SugarExchange and make it available to Sugar Open Source, Sugar Professional and Sugar Enterprise customers. How do I do this?
- What is concurrent use of software? Are concurrent Product Use Rights (PUR) available to commercial volume licensing customers?
- I am developing a commercial, closed-source product. Should i use the 0.4 or 0.5 version of the library?
