 source software to proprietary products. However, there are certain restrictions put on downstream users of the open source code under per- missive licenses, for example, the termination of the permissive license if a downstream user challenges the software with a "submarine" patent (e.g., the Apache 2.0 license). 3. Weak Copyleft Licenses: Here the originator of the open source software makes a con- scious choice to copyright its software, and then license it under the so-called "copyleft" terms. Copyleft is a strategy of utilizing copyright law to pursue the policy goal of fostering and encouraging the equal and inalienable right to copy, share, modify, and improve cre- ative works of authorship. One of the conditions the downstream user must satisfy before distributing "copyleft" software is that any changes such user makes to that software be likewise released under the copyleft license. A copyleft license ensures that all modified The Shift to Software versions of the code remain free of restrictions in the same way. (e.g., the Eclipse and the LGPL licenses). 4. Strong Copyleft Licenses: Strong copyleft licenses have significant conditions fostering software sharing. Such licenses are said to keep software "forever free" of use restrictions. In addition to having weak copyright restrictions, strong copyleft licenses have other con- ditions that may usurp or co-opt adjacent or linked proprietary code, depending on how the copyleft code is combined or linked with the proprietary code. (e.g., the GPLv2 or GPLv3 license, [9]). LINUX AND APACHE FOUNDATIONS, OpenStack, ODL, AND THE OPNFV Initially, open-source projects involved only a small number of devoted people, but the promise of these projects led to success and this brought the involvement of big corporations as consum- ers and contributors. Big corporation involvement necessitated a need for structure around gover- nance, eventually incorporation of the activity and the reasonable expectation that the project would be marketed, sold, serviced, funded, evo