2

I'm currently handling a project where devolopers have used the 3 different oss codes & respective licenses abovementioned and also proprietary code. scenario is as follows:

  • The sw tool being developed will use the oss code (set of libraries) without modifications;
  • The libraries will be used in binary form;
  • Proprietary source code is not intermixed with libraries code; but
  • It calls the use of the api of the libraries.

I know that Apache 2.0 and Mozilla 1.1 are incompatible. Since i can also apply Mozilla's 2.0 license terms this makes all these different licenses compatible with each other?

Getting to the question: what license terms should prevail? or is the correct way to distribute the sw tool to do it including a ABOUT file with all the different license terms?

  • Wait, there are proprietary libraries that are used? – Zizouz212 Feb 11 '16 at 0:11
  • no, the proprietary code will call the use of api of the oss libraries. – paul black Feb 11 '16 at 11:39
  • @Zizouz212, can you help? – paul black Feb 12 '16 at 10:03
  • So the resultant program is one that is proprietary? – Zizouz212 Feb 13 '16 at 16:09
  • that's actually implicit in my question. does calling the use of api libraries forces me to apply those license terms? or can I just simply distribute tose licenses with the respective license terms in the same package and keep the code proprietary? – paul black Feb 13 '16 at 16:24
1

I'm neglecting any proprietary terms that may affect your program.

Since you don't modify any code or binaries of the open source projects...

  • BSD licensed code: Make sure to attribute, display license notice;
  • Apache 2.0 code: Make sure to attribute, display license notice;
  • Mozilla 2.0 code: No changes, make sure to attribute, display license notice.

So basically, nothing "prevails."

What you need to do in your application is assure that you provide all projects with the attribution they require, through displaying the license notices.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.