4 ms·
It's a perfectly well accepted term in context (jargon); if it's new to you then that's fine but it's not a fault of the term. When you use open source code, yo
by yjftsjthsd-h 5y ago
It's a perfectly well accepted term in context (jargon); if it's new to you then that's fine but it's not a fault of the term. When you use open source code, you have to comply with the license requirements on that code. Sometimes, it's possible to combine code because the licenses can both be applied to the combined result at the same time. For instance, many permissive licenses boil down to a requirement that you include the original author in credits for the program. The GPL requires that you share the source code that went into a binary with anybody who gets a copy of binary (basically). Since you can fulfill both of these requirements at the same time, you can freely combine code into the two licenses (although the result will effectively be all GPL), so they're compatible. Because GPL & CDDL both require that the relevant code must be licensed under their license specifically, you can't fulfill both requirements at the same time unless the code was originally dual-licensed by the original authors, because you can't change GPL code to CDDL or vice-versa.
(IANAL and this is simplified; tread cautiously)
- Rochus 5y agoThanks. The question was meant more rhetorically, since lawyers (I also studied law) usually have a hard time with OSS licenses, and many developers make assumptions that often don't match reality. A seemingly "well accepted" assumption often turns out to be a costly mistake. I therefore share your recommendation: tread cautiously.