Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
With Qt 4.5 being release to LGPL, would it be possible for eXaro to be release as LGPL too? I think it could increase interest in eXaro since reports are very used on commercial apps.
I don't know, exaro depends on other libs which are GPL, ex: zint.
If you convince zint guys to release zint under lgpl I think I'll release eXaro to v2 lgpl too.
I use eXaro on commercial apps, but they are open source.
Well I have posted a message at the zint forum asking then if they would be willing to change their license. Can't hurt to ask :)
I'll post here after I get any sort of reply from then.
Well I got a reply from developers of zint and they said that their code is heavily based on another GPL code, and it seems to be able to change license it would require a rewrite of some parts and don't seem to have an interest in doing so. Would it be possible then to make zint optional? That way commercial software would be able to use eXaro (without zint compiled in, which means no bar codes) and so would free software (with zint compiled in).
Is it possible? I'm willing to do this task if enables eXaro to be LGPL. I really do believe that making eXaro LGPL would increase developer interest on it. And I'm more than willing to put code to help this idea :D
Ok, I'll release eXaro project under LGPL >=v3 too.
I'll skip all plugins which depends on GPL libs if you choose to compile eXaro under LGPL.
If you wan't to write some code please start by rewriting stringList plugin of propertyEditor project (http://code.google.com/p/propertyeditor/). eXaro's designer depends on this project , and for stringList plugin I copy the editor from qt's sources (which are GPL). So if you want to help to release eXaro under LGPL there is a good start.
I want to make this clear, eXaro will be release under GPL and LGPL v3, and I'll accept only GPL and GPL+ LGPL code. I'll not accept other licenses and I'll not accept LGPL only license.
Ok, I'll take a look at the stringList plugin. But if the same code exists in Qt 4.5 (which is being released as LGPL) there shouldn't be any problems with using it's code with LGPL code now. From what part exactly did you copied it from? I'll take a look at a source snapshot from Qt 4.5 and seem if it's there. If it is, than there's no need to change it, am I right?
As for accepting only GPL/LGPL code I think it's great. I think they are good licenses and I have helped in projects that use then before (http://gitorious.org/projects/dlib - I created the netuno-sandbox repo for example). I think that if folks want to use eXaro in their commercial software they should give back any improvements they make to it to the whole community. That way eXaro will continue to improve more and more!
Just one thing, this week I'm gonna be very busy (work trip) so I'll probably only be able to work on the stringList (and other things) next week.
As I promise I relicense eXaro under GPL and LGPL (see: http://code.google.com/p/exaro/source/detail?r=88\), now trunk is dual license and GPL is the default license.
If you want to use eXaro under LGPL license, you have to edit top "CMakeLists.txt" and choose LGPL.
About the stringlist plugin, only the editor you have to rewrite because AFAIK Qt 4.5 is not yet released under LGPL, it will be released under LGPL, but now isn't. So if you want to use eXaro now under LGPL you should rewrite only the editor.
I'm not hurry, when you have time and want you are welcome.
But remember ONLY GPL or GPL+LGPL code I'll accept :).