Hello Lars,
The GPL license that is on VTKEdge right now requires you to release
your source code with a license compatible with GPL if you distribute
your application. However, I won't go into much detail on this because
shortly (in the next few weeks) we will be changing the license on
VTKEdge to a BSD license which is a non-reciprocal open course license
(doesn't require you to release your code as source). Keep your eye on
the vtkedge.org web site and this mailing list for an announcement when
the change is made.
Lisa
Lars Friedrich Lars wrote:
Hello,
I have a general question regarding VTKEdge's licensing model:
(because I do not understand when exactly I would need the VTKEdge Commercial
License)
I am developing an application that uses ITK, VTK and Qt. I am thinking about
integrating some VTKEdge-features (GP-GPU-based volume rendering for example).
Let us assume that I DO NOT MODIFY any of the original VTKEdge-files, but I
link against the unmodified VTKEdge-library and possibly derive from some of
the VTKEdge-classes and change their behavior slightly in the sub-classes.
Moreover, let us assume that the application goes commercial one day (this is
surely not my inmost desire - however, I have to think about it now for some
reasons) - either the application itself has its price or a related service
costs money. Would I then have to purchase one or more VTKEdge Commercial
Licenses? Would I have to publish the source code of my application? I mean,
it's clear that the application must explicitly announce that it uses ITK, VTK,
Qt (LGPL) and VTKEdge, but do I also have to make the classes derived from
VTKEdge and my own classes publicly available?
Maybe that question sounds naive or even capitalistic (no!), but I have little
experience with such licensing schemes ...
Thank you!!
regards,
lars
_______________________________________________
VtkEdge mailing list
[email protected]
http://public.kitware.com/cgi-bin/mailman/listinfo/vtkedge
