I wanted to follow up and make sure you received my responses to your email.
We are definitely interested in resolving these so we can be included in debian releases: Anyway comments below: > -----Original Message----- > From: Kari Pahula [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 06, 2006 4:06 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Licensing problems with appWeb > > Hello. > > I'm considering packaging appWeb for Debian, but have found a few > problems with appWeb's licensing. To be more specific, not all parts > of it are licensed under a GPL-compatible license, even though most of > appWeb is under GPL. Great. Sounds good. > > Portions of url.cpp are under Apache's license. There are a few > different versions of that license, and it doesn't specify which one, > but none are GPL compatible. There really is only a couple of lines there. We could rewrite to remove that code. Let me think about that and get back to you. > The PHP modules in http/modules are licensed under PHP license, which > is not GPL compatible. Also, the openssl module will link to the > openssl library, which isn't GPL compatible, either. I'm not certain > if using dlopen is enough to make openssl a separate work. We are using openssl as a library just like any other part of linux so that should be fine. You could omit PHP or we could configure it to run using CGI that would avoid any license issue. We also provide AppWeb with a commercial license that is compatible with Apache and PHP licenses. > I could avoid any GPL compatibility issues with the modules by just > not compiling in the offending modules. But it would be possible to > allow the use of non-GPL-compatible code by amending the license with > an exception, explicitly allowing mixing it with the offending > licenses. I've explained the situation before at > http://bugs.debian.org/361010 Okay, let me check that out. Thanks. > > But I'm not quite sure if changing the license is an option here, > seeing that parts of appWeb are under GoAhead Software Inc's > copyright. The GoAhead license is pretty broad so it should not be a problem. > > Unfortunately, I can't work as easily around url.cpp's apache license > as with the modules. Otherwise I would just proceed with the > technical side of packaging appWeb for Debian already. I can look after that. It really was more of a algorithmic credit rather than code copied from Apache. It should be easy to clarify. It is less than 100 lines. > > It's ultimately up to you what you would do with these issues. > Obviously my opinion in this should not be taken as a legal advice, > but I don't think that appWeb would be distributable in Debian as it > is now. But being in the clear with regard to licensing would be your > benefit, too. Agree, and thanks for your help. I'm committed to solving these issues if you want to continue with your packaging efforts. Michael O'Brien AppWeb Lead. > -----Original Message----- > From: Kari Pahula [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 06, 2006 4:06 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Licensing problems with appWeb > > Hello. > > I'm considering packaging appWeb for Debian, but have found a few > problems with appWeb's licensing. To be more specific, not all parts > of it are licensed under a GPL-compatible license, even though most of > appWeb is under GPL. > > Portions of url.cpp are under Apache's license. There are a few > different versions of that license, and it doesn't specify which one, > but none are GPL compatible. > > The PHP modules in http/modules are licensed under PHP license, which > is not GPL compatible. Also, the openssl module will link to the > openssl library, which isn't GPL compatible, either. I'm not certain > if using dlopen is enough to make openssl a separate work. > > I could avoid any GPL compatibility issues with the modules by just > not compiling in the offending modules. But it would be possible to > allow the use of non-GPL-compatible code by amending the license with > an exception, explicitly allowing mixing it with the offending > licenses. I've explained the situation before at > http://bugs.debian.org/361010 > > But I'm not quite sure if changing the license is an option here, > seeing that parts of appWeb are under GoAhead Software Inc's > copyright. > > Unfortunately, I can't work as easily around url.cpp's apache license > as with the modules. Otherwise I would just proceed with the > technical side of packaging appWeb for Debian already. > > It's ultimately up to you what you would do with these issues. > Obviously my opinion in this should not be taken as a legal advice, > but I don't think that appWeb would be distributable in Debian as it > is now. But being in the clear with regard to licensing would be your > benefit, too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
