> Hi Frank,
> With the PythonOCC license now being GPLv3, I was wondering, if a > company wished to use it in a commercial application, would there be > any > way to "purchase" some kind of "commercial" license (like a > dual-licensing scheme)? Indeed, PythonOCC will adapt to a dual licensing model. The recent move to GPL is an initial step in that process. > If I understand it correctly, OpenCascade can be > used in commercial apps in a "non-viral" way, but not PythonOCC. We haven't worked out the exact details of our licensing model yet, apart from the fact that it will be dual licensed. > I know there is no PythonOCC organization (yet!), but what about > funding > some development in this way? If you have an interest, well than we'll simply will speed up the process of moving to a dual license. We're trying to formulate the best possible licensing strategy, which really is pretty involved. Since a lot depends on it, we want to get it right the first time. > I love OS and understand the benefits of GPL, but I was just curious, > knowing from past work experience that this question will come up. You're right, and we have given it quite a lot though the past few months. Moving to GPL sure has been a good idea, but the second step to a dual licensing model is somewhat harder to define. Thanks for your interest, -jelle _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
