|
From: John S. <js...@gm...> - 2020-07-28 20:57:05
|
On Tue, Jul 28, 2020 at 7:54 AM Timmy Jose <tim...@ya...> wrote: Hey Timmy, Nice to hear from you. I have a question about the licensing aspects of writing a port/derivative > work using some of the APIs of jgrapht. Looking at the licensing page, > suppose I decided to choose LGPL 2.1, can anyone: > 1. Confirm that a port/using the APIs with custom implementation in a > different language (from Java, that is) is all right? > It would depend on how your port is to be licensed. If you redistributed it as LGPL (or GPL), there should be no issue. In fact, that's what we've done (keeping the EPL dual licensing as well) with the recently released Python bindings: https://python-jgrapht.readthedocs.io/en/jgrapht-1.5.0.0/ Those build on top of an underlying C api, which is not a port, but rather a wrapper for the native code compiled ahead of time from Java via GraalVM: https://github.com/jgrapht/jgrapht-capi So...maybe instead of all the work of porting, you might want to consider using the above to create bindings for whatever language you're interested in (and perhaps sharing that with the community)? If your port were redistributed under a different license, that would be something to discuss with a lawyer, of which I am not one. |
