b'A Guide for Authors of Software2017TD and Legal can review each unique situation and make achanges reviewed. If the project has already been deployed and determination. They may request the submission of a Softwarethere is ongoing development, file a new SDR referencing the Disclosure Record (SDR) or Outside Activities Form (480.05) tooriginal SDR and advance the version in the new SDR to distin-gather the necessary details.guish the releases. This allows TD to track the development in If INL determines that it owns the software, the author mayrelation to the original SDR rather than treating it as an unrelated request to obtain proprietary licensing for the software fromproject, saving resources and expediting the process.INL. Alternatively, INL may release the software under open- Should the work be protected with patents source licensing where the author, and the public, will have access to it. Additionally, the Director of Technology Deploy- in addition to copyright?ment may decline to assert ownership in certain circumstances,In many cases, software is most appropriately protected by based on recommendations of potential stakeholders. If thiscopyright. If the software uses a new and innovative procedure occurs, DOE retains ownership of the software, and theor process, then file an Invention Disclosure Record (IDR) in author(s) can request ownership or a license from DOE-CHIPDS (the same system used to file SDRs).(Chicago) patent counsel.Filing an IDR initiates the process of assessing the invention, Can authors contribute to open-sourceand determining if it should be protected by a patent, which projects as part of their job? may be strategically used to more effectively bring the technology to market in some cases, or which may bring INL additional Yes, authors are encouraged to contribute to open-sourcelicensing royalties to fund further research. projects as long as they have filed an SDR for the contributionsCan software be released as open source?and it has been approved by TD. When ongoing contributions are anticipated, TD may give a broader scope of approval soYes, if open source is the best mechanism to deploy the that the author does not need a separate disclosure for each bugsoftware, it supports programmatic objectives, and doing so fix or small feature change. Whenever an author modifies thirdcomplies with export control and other contract requirements. party open-source code, they should evaluate the possibility ofINL and TD strongly support releasing software to achieve the contributing their changes back to the original project and filegreatest impact for our technological advances when possible. an SDR for these changes. Authors may not simply send a pullTD makes licensing strategy decisions based on the recommen-request, code patch, or equivalent to the external project withoutdations/guidance from BEST, management, program sponsors, TDs approval. export control and other supporting entities. What if the scope of the work changes afterCan authors give the software to others?filing a Software Disclosure Record? Software should not be given to any non-INL employee unless Changes to the core functionality of the software must be docu- TD reviews and approves the transfer. TD ensures that all of mented to comply with DOE requirements. If the project is stillINLs contract requirements are met and that the software is transferred under the appropriate agreements. If there is a need under initial development and has not been deployed, contactto share the software with others, contact TD and they will assist TD and they can amend the projects description and have thein getting the proper agreement in place.5'