Wiki source code of Spectrum of FLOW Licenses: Visualizing Derivative, Associated and Redistributed Works
Last modified by Joseph Potvin on 2023/02/17 01:53
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | [[image:flow_licenses1midsize.png]] | ||
| 2 | |||
| 3 | * Permissive licenses (MIT, Apache) carry no restrictions on re-licensing when blending source code for distribution. | ||
| 4 | * Elastic licenses (Eclipse) require that the original source code and its direct derivatives remain under the original licenses, whereas any code that is added can be under any license(s). | ||
| 5 | * Unified licenses (GPL, AGPL) require consistent licensing of software at the program level when blending code for distribution. | ||
| 6 | |||
| 7 | [[image:flow_licenses2midsize.png]] | ||
| 8 | |||
| 9 | Source: Potvin, J. 2012. "Flow Licensing and Contracting: Applied Intellectual Resource Economics in the Canadian Public Sector". In: Mark Perry & Brian Fitzgerald (eds). 2012. __Knowledge Policy for the 21st Century: A Legal Perspective.__ Irwin Law Publishers: [[http:~~/~~/www.irwinlaw.com/pages/knowledge-policy-for-the-21st-century~~-~~-a-legal-perspective>>url:http://www.irwinlaw.com/pages/knowledge-policy-for-the-21st-century--a-legal-perspective]] |