Hello:
I noticed that Theia uses both EPL2.0 and GPL2.0 licenses. Does this mean that if we develop an IDE based on Theia and sell it as a commercial product, we need to open source it?
Really appreciate!
Hello:
I noticed that Theia uses both EPL2.0 and GPL2.0 licenses. Does this mean that if we develop an IDE based on Theia and sell it as a commercial product, we need to open source it?
Really appreciate!
Hey @inlann,
Does this mean that if we develop an IDE based on Theia and sell it as a commercial product, we need to open source it?
No, the EPL is quite permissive, and allows adopters to sell software build on Eclipse frameworks/projects as they like, without the need to make their source code openly available. The only thing that needs to be open sourced is if you were to modify Theia. Changes to projects under EPL need to be public. See also here.
We modified some code in the dev-packages since we need to generate our src-gen/*
. Is this a modification of Theia?
Strictly speaking yes! If the modification can be useful for others, too, you can contribute it. If the customization is very specific, maybe you can refactor the respective part to allow for your customization to be pluged-in? I.e. you keep your own code not open source, but modify the place where you applied a change to be customizable? If none of the two options make sense, you can still keep the modification in a public fork.
It is hard to provide a good answer without knowing the details of your change, can you share more details?
Best regards,
Jonas