8 Common Open-Source Licenses and Primary Restrictions Third party software assets under these common open-source licenses may be used and integrated with INL software without TD approval. However, the integration of these assets must be recorded and disclosed to TD when submitting a software disclosure record. By implementing code or assets under the following licenses, INL may be required to meet obligations such as providing attributions to the author(s).Yet, implementing code or assets under these licenses is unlikely to restrict INL’s ability to distribute the project to others or commercialize the code. • Apache Software License • Python Software Foundation License • MIT • BSD • Artistic License 2.0 • Creative Commons Public Domain Dedication (CC0) • Creative Commons Attribution (CC-BY) Assets under these common open-source licenses may be used as tools by authors (as a stand-alone application), but may not be integrated into INL software without explicit TD approval: Implementing code or assets under the following licenses may restrict INL’s ability to distribute to others or commercialize the code, may have ambiguous requirements, or may contain explicit language.TD must evaluate their use in INL software on a case-by-case basis before integrating them to ensure they are appropriate. • GNU General Public License (GPL) • GNU Library or “Lesser” General Public License (LGPL) • Mozilla Public License (MPL) • Eclipse Public License (EPL) • Artistic License 1.0 • WTFPL Assets under these common open-source licenses require TD approval to use or integrate with INL software: Integrating or merely using code or assets under the following licenses may restrict INL’s deployment strategy options (even when not directly integrated with our own software). Use of code or assets under these licenses must be evaluated separately for each case. • GNU Affero General Public License • Creative Commons licenses (Excluding CC0 and CC-BY)