Clarification of open-source licensing issues
Posted on 2009-04-08
I apologise if my question appears to be a repeat of other posted questions about open source licensing I have trawled the database and cant find anything that completely explains what I need to know. I am not expecting a lawyers response, but some good common-sense advice would be appreciated.
I am developing a software library that will link to two open source libraries, both of which are published under multiple licenses (GPL, LGPL, MPL). I assume that this means that my library would be considered a derivative work?
Although my development work is largely complete, I wish to create an open source project around it, in order to improve its maturity prior to release.
Once complete, I wish to incorporate my library in a proprietary application and possibly also commercially license it to other developers for use in their proprietary applications. Does this mean that it needs dual licenses? Are there any ethical issues with this? Are there any procedures I should follow when accepting public contributions?
Finally, when releasing my proprietary application, what is the correct procedure for distributing the binaries of the two other underlying libraries? Do I simply have to acknowledge them from within my own license file? If so, could you post some example wording?
Sorry for so many questions and many thanks for any insight you can offer.