Releasing Open Source
We have worked with the Office of General Counsel to identify the ideal licenses to use when releasing University-owned copyrights through open source. Follow the University Regents policy for details.
Open source releases are ideal for projects that need additional improvement or maintenance. An open source release can be a bridge to build a community of users that together enhance the impact and value of the software or copyrighted tool.
We encourage you to choose a license that best serves the University’s mission and your academic discipline.
Open Source Resources
- Open Source Basics—explains Open Source Software (OSS) basics.
- Standard OSS Licenses—describes benefits of releasing software
- Open Source Business Models—details common open source licenses
- Open Source Handout—quick guide to OSS and working with OTC.
- OSS Watch—provides unbiased advice and guidance on the use, development, and licensing of open source software.
- Creative Commons—helps you legally share your knowledge and creativity.
- TL; DR Legal—software licenses presented in plain, easy-to-comprehend language.
License Recommendations for Software
Preferred: GNU General Public License version 3
- Users can: Use commercially, modify, distribute, place warranty, and use patent claims.
- Users cannot: Sublicense or hold the creator liable.
- Users must: Include original version, state the changes made, disclose source code, include license documentation, include copyright, and include installation instructions
Acceptable: MIT License
- Users can: Use commercially, modify, distribute, sublicense, use privately.
- Users cannot: Hold the creator liable.
- Users must: Include copyright and include license.
License Recommendations for Creative Works
Preferred: Creative Commons-Noncommercial-ShareAlike
Acceptable: Any Creative Commons License