|
From: Timmy J. <tim...@ya...> - 2020-07-29 03:31:27
|
<div>Hello John,</div><div> </div><div>Thank you for the very helpful response!</div><div> </div><div>Yes, licence-wise, going the way of LGPL should be quite okay for the library I have in mind. :-)</div><div> </div><div>That being said, you do make a very good point of providing a language binding for the C API - both in terms of being much less work, but also being able to keep in sync with jgrapht core. I will have to seriously consider this option in lieu of going for a full port from scratch.</div><div> </div><div>Thank you for sharing the links. I will play around with them a bit and mull over best approach!</div><div> </div><div>Best Regards,</div><div> </div><div>Timmy</div><div> </div><div><br /></div><div><br /></div><div>28.07.2020, 13:57, "John Sichi" <js...@gm...>:</div><blockquote><div dir="ltr"><div dir="ltr"><br /></div><br /><div class="f13ca48719c8a60033905b23b39675agmail_quote"><div class="334d7d341e3233c5b27ca91297445127gmail_attr" dir="ltr">On Tue, Jul 28, 2020 at 7:54 AM Timmy Jose <<a href="mailto:tim...@ya...">tim...@ya...</a>> wrote:<br /></div><div class="334d7d341e3233c5b27ca91297445127gmail_attr" dir="ltr"><br /></div><div class="334d7d341e3233c5b27ca91297445127gmail_attr">Hey Timmy,</div><div class="334d7d341e3233c5b27ca91297445127gmail_attr"><br /></div><div class="334d7d341e3233c5b27ca91297445127gmail_attr">Nice to hear from you.</div><div class="334d7d341e3233c5b27ca91297445127gmail_attr" dir="ltr"><br /></div><blockquote class="f13ca48719c8a60033905b23b39675agmail_quote" style="border-left-color:rgb( 204 , 204 , 204 );border-left-style:solid;border-left-width:1px;margin:0px 0px 0px 0.8ex;padding-left:1ex"><div>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:<br /></div><div><div> 1. Confirm that a port/using the APIs with custom implementation in a different language (from Java, that is) is all right?</div></div></blockquote><div><br /></div><div>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:</div><div> <br /></div><div><a href="https://python-jgrapht.readthedocs.io/en/jgrapht-1.5.0.0/">https://python-jgrapht.readthedocs.io/en/jgrapht-1.5.0.0/</a><br /></div><div><br /></div><div>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:</div><div><br /></div><div><a href="https://github.com/jgrapht/jgrapht-capi">https://github.com/jgrapht/jgrapht-capi</a><br /></div><div><br /></div><div>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)?</div><div><br /></div><div>If your port were redistributed under a different license, that would be something to discuss with a lawyer, of which I am not one.</div><div><br /></div></div></div> </blockquote> |
