Hello, I will take a look at what you have, but if there is no way that you can either make exceptions to a pure GPL license or make modifications to it then we cannot use your code in Bacula as it currently exists, or we will be in violation of your license. I'm not suggesting that you change to another license, only that the license you are using is not compatible with a lot of existing software.
If you are moving to GPLv3 that essentially locks us out of using your library since GPLv2 is an incompatible license, and it also means that you *ARE* able to make modifications to your license, and I would suggest that you look even more deeply into these issues than you already have. The problem isn't for Bacula to work something out. Bacula is now Open Software. It is "freer" than your software, less restricted (or will be as soon as I work out the appropriate modification). The problem is that your current license is restrictive and forbits GPL Open Software projects such as Bacula from using it. In otherwords the interpretation of your license as taken by FSF makes your software closed with respect our Open Software. It isn't a question of throwing out your license, but a question of deciding whether or not you want to be bound by what I consider certain (in Stallmans words) "onerous" license conditions. Anyway, thanks for taking contact with us, and good luck with your project. Best regards, Kern On Friday 07 September 2007 10:58, Dan Shearer wrote: > On Fri, Sep 07, 2007 at 09:53:05AM +0200, Kern Sibbald wrote: > > I haven't read your document you, but will do so shortly. > > It covers general points on MAPI mailboxes, so hopefully should be some > use whatever your technical and licensing situation. > > > 1. Bacula *really* needs some way to backup Exchange in a way that if > > the user/admin wants, he can restore a single mail box. If you are > > working on such a feature, it would be *very* interesting to us. > > This is only a small modification of features we have already delivered, > such as you can try out for yourself with openchangeclient at the > commandline to get a feel for the possibilities. > > > 3. There is a *BIG* license problem with the GPL. Basically it forbids > > using GPL licensed code with a large class of OSI Open Software. This > > point seems to be very poorly understood by developers as was the case > > for myself. Bacula is licensed under GPLv2, but it will shortly be a > > modified GPLv2. > > There is nothing we can do about this, it comes from upstream. If you > wish to compile against our libraries, you need to be GPLv2+ (note the > plus) or GPLv3. This will not be changing. There's 15 years or so of > code development we're relying on, so it is unlikely anyone will be > providing us with alternatives any time soon. We have enough to do > interoperating with Exchange. > > > Are you aware that since Bacula uses GPLv2, that we are forbidden from > > using GPLv3 code because it is not compatible, and much more seriously, > > we are forbidden (actually in violation of certain GPL licenses) to use > > OpenSSL code, which is the basis of our data and communications > > encryption. > > Right, understood. We have looked closely at these same issues. > > > 2. Remove all 3rd party GPL'ed software from one's product, then modify > > one's GPL license to permit using OSI Open Source software. Bacula is > > just in the process of doing this. > > GPLv2+, if at all possible. > > > Bottom line: IMO, the GPL is a very restrictive license that has some > > onerous > > It is not a debate OpenChange can have, see above. > > > are using a standard GPL license, we cannot use your code unless we work > > out > > We are currently GPLv2+, moving to GPLv3. We have no choice. We're not > unhappy with that, in our situation, but we are sympathetic to your > situation. > > > Final note: I really would like to try to work with you guys on your > > Exchange interface. Given the above license problems, do you think we > > can find a solution? > > We have zero room to move. If you are able to work something out we'd be > delighted to work with you. > > You might want to look at a loose plugin interface, such as Asterisk and > its agi interface, which can use commandline tools. At least there you > will be able to get something going quickly. There is a long tradition > of Unix backup tools executing 'foo' on a remote host and producing > stdout for interpretation by an intelligent system. I understand this is > not what you're looking for. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
