Skip to main content
Software Engineering

Return to Answer

added 337 characters in body
Source Link
vbence
vbence
  • 101
  • 3

The following is true to most of the opensource licenses:

When you embed an opensource component into your product or your product can not function without it your product is considered a derivative work.

Some of these licenses are sticky, meaning if you create a derivative work and you publish it, then you have to also publish it as an opensource program (under the same license as the component). GPL is an example for this kind.

There are more permissive licenses which are not sticky, meaning you do not have to redistribute your program (and full source code) under the same license. For example MPL is not sticky.

Edit

If you are using their code you have to comply with their rules (the license the chose).

The MPL defines what is considered a derivative work based on files. For example if you copy-paste MPL-ed code into your source file, then that file falls under MPL too. GPL uses more lofty ideas which are open to interpretation.

The following is true to most of the opensource licenses:

When you embed an opensource component into your product or your product can not function without it your product is considered a derivative work.

Some of these licenses are sticky, meaning if you create a derivative work and you publish it, then you have to also publish it as an opensource program (under the same license as the component). GPL is an example for this kind.

There are more permissive licenses which are not sticky, meaning you do not have to redistribute your program (and full source code) under the same license. For example MPL is not sticky.

The following is true to most of the opensource licenses:

When you embed an opensource component into your product or your product can not function without it your product is considered a derivative work.

Some of these licenses are sticky, meaning if you create a derivative work and you publish it, then you have to also publish it as an opensource program (under the same license as the component). GPL is an example for this kind.

There are more permissive licenses which are not sticky, meaning you do not have to redistribute your program (and full source code) under the same license. For example MPL is not sticky.

Edit

If you are using their code you have to comply with their rules (the license the chose).

The MPL defines what is considered a derivative work based on files. For example if you copy-paste MPL-ed code into your source file, then that file falls under MPL too. GPL uses more lofty ideas which are open to interpretation.

Source Link
vbence
vbence
  • 101
  • 3

The following is true to most of the opensource licenses:

When you embed an opensource component into your product or your product can not function without it your product is considered a derivative work.

Some of these licenses are sticky, meaning if you create a derivative work and you publish it, then you have to also publish it as an opensource program (under the same license as the component). GPL is an example for this kind.

There are more permissive licenses which are not sticky, meaning you do not have to redistribute your program (and full source code) under the same license. For example MPL is not sticky.