10 • Does the license complicate the intended release model? Many commercial licenses restrict redistribution in a way that prohibits INL from releasing the software as desired. Some licenses do not allow use of the software when working with others, or they may impose terms on the product that may not allow for the preferred deployment strategy. What do authors need to track? Authors should maintain a record of the third party software, along with the licenses and versions integrated with or depended upon by the INL software. Dependencies and integrations should be recorded as separate categories, as this has implica- tions for licensing. Authors should record how the software is incorporated and the manner of integration with the third party software. Examples include: • Static linkage • Dynamic linkage • VM integration, such as a jar file being loaded by the JVM or a Python module being loaded by the interpreter • Textual inclusion, such as a C-style #include directive • URL links that instruct a browser to download and include additional components, such as JavaScript packages or images • External services accessed over the network • Out of process application communication mechanisms such as memory mapped files, pipes or DBUS • Copy and paste third party code directly into INL software Authors should be specific with the mechanism of linkage, as this can impact licensing considerations. Authors also need to record where the software was obtained; for example, the GitHub repo of the source code or the project’s home page. This information should be provided when the author submits the SDR. The SDR should be updated periodically as the asset list changes.