Skip to main content
Law

Return to Question

added 10 characters in body
Source Link
Zizouz212
Zizouz212
  • 2.6k
  • 20
  • 33

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:

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

iI 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?

gettingGetting 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?

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 oss code (set of librarie) 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?

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?

Source Link
paul black
paul black
  • 462
  • 1
  • 4
  • 11

3-clause BSD + Apache License 2.0 + Mozilla Public License 1.1

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 oss code (set of librarie) 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?