[JSch-users] a license issue [Re: jsch file transfer, etc]
Status: Alpha
Brought to you by:
ymnk
From: <ym...@jc...> - 2003-02-07 01:28:59
|
Hi, +-From: Dale Anson <******@****************.com> -- |_Date: Thu, 06 Feb 2003 16:18:08 -0800 ___________ | |I've been busy with other things, but wanted to get back to you |about this. I have two ant tasks done now that rely on your ssh |library and work well. Thanks so much for the work you've done in |putting this library together. I've run into a license issue, |however. Would it be possible to license jsch with an Apache style |license instead of LGPL? This is a key requirement for getting |the tasks submitted to the Ant project, they cannot accept GPL or |LGPL as it somehow conflicts with the Apache license. I'm not a |lawyer and don't really see much difference between the two, so |maybe it doesn't make a difference to you either? # That is timely question for me and I want hear comments from jsch-users mailing, # so I will write a reply to that mailing list with BCC: for you(Dale Anson). Recently, some large open source project has also asked me about a possibility of charging the license from LGPL to other open source license. Their code is under the term of some open source license, but, according to them, LGPL is not acceptable because of the ambiguity of LGPL. IMHO, if the change of license will make people happy, I will do. It is great pleasure for me to hear that my stuff works for somebody. In fact, the code of jsch is written by only one person(ymnk), so I can do without much of difficulties. However, I'm hesitating to take a step to such a direction. You may know that there is a sensitive and sad history in pure java ssh implementation. I mean that Mindbright had changed their GPLed MindTerm to the proprietary and many people in open source community had been disappointed in that decision. If I change the license of jsch, It will be under BSD style license, but if that change disappoints somebody, it is sad for me. I want to hear your comments and suggestions. Thanks, -- ymnk |