ORNL Software Licensing
- Table of Contents
This page contains information meant for ORNL Employees with instructions for how to mark their source code projects. It is not intended to serve as legal advice.
Required Actions
All ORNL software must be approved for open source release before being uploaded to the ORNL GitHub organization. See the Copyright Software Submission Application page on the ORNL internal web site for more information.
Open Source License
To be approved for release, your code must use an open source license (or the ORNL open source license). The following files are examples of open source licenses you can use.
- Apache 2.0 License with LLVM Exception
- Apache 2.0 License
- BSD-3 License
- GPL-2.0 License
- GPL-3.0 License
- LGPL-2.1 License
- MIT License
If your repository was approved for release under a different open source license, the text of that license will be provided by for you.
Other Considerations
In addition to obtaining approval to release your code as open source, you should also consider what kind of open source project you want to create around your code. Do you want to build a community of contributors, will it be part of an ecosystem, etc? To help understand the different aspects of open source projects, you can find best practices and other information in the CORSA Open-source software project documents repository.
Have Questions?
If you still have questions or need more information, contact the ORNL GitHub Admins.