J Aaron Farr

Username jaaronfarr
Follow

All comments 9
Comments by J Aaron Farr 2
Comments on J Aaron Farr's content 7

Comments

J Aaron Farr commented on Making Open Source Work @mksaad Your question now applies to slides starting with #49. Slide #49 (License Scope) places the license on a spectrum related to the protections and conditions under which the license requires the source code remain open and freely available. On the left hand side we have the Apache License which allows for sub-licensing under a proprietary license, thus not requiring any combined works to remain open. On the other side we have the GPL which requires all combined works to remain open. In the middle, we have licenses such as the MPL, EPL, and LGPL which require the originally licensed code to remain open but that the code can be used (under certain conditions) in a larger, proprietary licensed work. The next set of slides present three scenarios and seek to answer the question: "When I combine open source code with proprietary code, can I sub-license the combined work under a proprietary license?" In each of these examples, the blue-ish documents with the 1’s and 0’s represent open source licensed code. The white documents represent proprietary licensed code. In the first example, the code is simply combined without any special divisions. In this case, the AL allows for relicensing, the GPL does not. The EPL/MPL/LGPL licenses are questionable. For example, the MPL’s trigger is file based, thus in this case, you can likely relicense. But the EPL trigger’s trigger is based on the definition of a derivative work, in which case, you can likely not relicense this combined work. The second example divides the open source code and the proprietary code into two clearly demarcated modules. In this case, the EPL/MPL/LGPL license question becomes more clear as this is the intended use case for these licenses. The final example considers the case in which we still have separate code modules, but a small bit of open source code has been cut and paste and put into the proprietary module. Now we’re back at the first scenario in which the sub-licensing option is largely dependent on the particularities of the open source license. Hope that clears things up! 7 months ago
J Aaron Farr commented on Making Open Source Work Unfortunately, it appears as though the slide animations are not complete here. I’m uploading a new version of the presentation and I’ll post an explanation when that is done. 7 months ago