Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m somewhat confused about the implications of introducing source code licensed under the GNU Lesser General Public License. I’m developing a test framework and I want to use and modify an open source project as part of the existing framework. Does this imply that the entire test framework should be open sourced?
You can integrate the LGPL component into a proprietary solution as long as it stays separate. So for example linking is fine, usage as a processor is fine. Bundling is also fine, as long as you clearly state that the bundle contains LGPL software and which that is.
You certainly can modify that software to your needs, that is the whole point of Open Source Software. However of you spread it again afterwards, for example by bundling it with your framework, you have to publish your modifications.
In general follow this rule of thumb:
You can use it and modify it to your needs, but do not try to make it appear as if you implemented that solution. Be fair and give credits to those who did the work for you.