Re: license issuse in qterm

2008-01-10 Thread Bas Wijnen
On Sat, Jan 05, 2008 at 03:56:56PM +0800, LI Daobing wrote: I am the maintainer of qterm and I am checking the license issue in qterm. qterm is release under GPL-2+ as a whole, and the source files are released under GPL-2+, LGPL-2.1+, BSD-2 and others. qterm/ssh/getput.h is released under

Re: license issuse in qterm

2008-01-10 Thread John Halton
On Jan 10, 2008 8:52 AM, Bas Wijnen [EMAIL PROTECTED] wrote: and if the derived work is incompatible with the protocol description in the RFC file, it must be called by a name other than ssh or Secure Shell. This may be a problem. However, to me it seems this just

Re: license issuse in qterm

2008-01-10 Thread Francesco Poli
On Thu, 10 Jan 2008 18:10:34 + John Halton wrote: On Jan 10, 2008 8:52 AM, Bas Wijnen [EMAIL PROTECTED] wrote: and if the derived work is incompatible with the protocol description in the RFC file, it must be called by a name other than ssh or Secure Shell.

license issuse in qterm

2008-01-05 Thread LI Daobing
Hello, I am the maintainer of qterm and I am checking the license issue in qterm. qterm is release under GPL-2+ as a whole, and the source files are released under GPL-2+, LGPL-2.1+, BSD-2 and others. qterm/ssh/getput.h is released under following license[1]. And I don't know whether it's OK to

Re: license issuse in qterm

2008-01-05 Thread Francesco Poli
On Sat, 5 Jan 2008 15:56:56 +0800 LI Daobing wrote: Hello, Hi! [...] qterm is release under GPL-2+ as a whole, and the source files are released under GPL-2+, LGPL-2.1+, BSD-2 and others. qterm/ssh/getput.h is released under following license[1]. And I don't know whether it's OK to