Ai, I noticed that i sent it personally and not to the list Meaning - the pythonocc organisation can issue a 'commercial' license with a commercial developer, or do you mean that Python-OCC will become available under a non-viral license model such as the MIT license (or LGPL if I recall correctly)
Rgds, J 2009/3/23 Jelle Feringa <jelleferi...@gmail.com>: > >> I am not too comfortable with this licensing scheme's, would you care >> to elaborate on the 'dual-licensing' scheme and what this would >> entail. Why would an OS based project want to proceed this way >> anyway?! > > Dual licensing is common ground really. The problem with some of the OS > licenses is that they're considered viral. > If you use such a license, the software you're building with the component > has to become open-source than too. > So, if you are developing a proprietary software, that's a deal breaker > often. > By adapting a dual license you serve both an open source as well as a > commercial interest. > Its a situation where everybody wins really. > > -jelle > _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
