A Guide for Authors of Software — 2017 9 How can authors ensure third party software/assets are okay to use? Most software, even open source software, comes with terms and conditions attached to the use, integration, modification and redistribution of the software to other parties. When determining whether the software in question can be used, the author should validate that the software’s license is compatible with INL’s intended use and deployment strategy. The IP terms of any contractor licenses should also be carefully reviewed. Authors are encouraged to consult TD or Legal if they need assistance reviewing agreements. How can an author ensure subcontractor- developed code is okay to use? INL’s standard subcontracting terms are often incompatible with some deployment strategies. It is critical that when authors request work from third parties, they also contact TD to ensure that the licensing terms in our subcontracts or agreements are compatible with the chosen deployment strategy. How can authors ensure open-source code is okay to use? In addition to generally being available at no cost, software under open-source licenses tends to have license terms that are more favorable than those available from proprietary software that is free of charge. The software will normally have source code available that can be audited and modified to work with INL’s system, and defects can be fixed without having to rely on the original authors. The software allows for redistribution to third parties and permits INL to extend the life of the software and use it to build new products. However, not all open-source licenses are the same, and some may restrict TD in ways that are not conducive to the deployment strategy for the software. Authors should disclose all third party licensed software that is planned to be included in the project, so TD can help assess whether the software is appropriate. Authors are encouraged to contact TD to assist in identifying whether it is permissible to utilize a third party asset or to aid in acquiring a license from the author. Some open-source licenses grant sufficient rights to INL to be compatible for a wide variety of purposes, making it possible for TD to approve their use implicitly. However, authors must still record and disclose the use of third party code to TD. The preceding chart provides common open-source licenses and their associated restrictions. How do authors ensure code without a license is okay to use? Software that does not have a license granting INL the right to utilize it is problematic. The unlicensed software might be freely downloadable from the internet, or it may have been obtained from a third party directly. If this software is integrated with INL’s software, it may impose a restriction in the future that is unfavorable. For instance, the software developers may ask for money for licensing after it has been released or even forbid its use altogether. INL always needs to have a software license for any software or code used or integrated with its own. How do authors ensure commercially licensed software is okay to use? A commercial license for software needs to be evaluated carefully before use or incorporation. The following should be considered as well: • Is the software available for free or is there a cost? • Is it a one-time cost, or an ongoing cost?