Open Source Release of Software

Public release of software source code developed by UT Southwestern faculty, trainees, and employees

Policies & instructions regarding 1) when it is appropriate to do so, and 2) if so, how to do it

** For anyone seeking to privately share with an external party any software developed by UT Southwestern faculty, trainees, and/or employees: please contact the UT Southwestern Office for Technology Development for further advice and assistance prior to initiating such sharing**

UT Southwestern recognizes that, at times, UT Southwestern employees (including faculty) and trainees may need to publicly release, as part of meeting their scholarly obligations, software source code they have developed within the course and scope of their employment or affiliation with UT Southwestern. Such obligations may include, for example, a journal requiring the public release of source code for software that is integral to the manuscript to be published, a granting agency requiring that source code developed under the funded research project be made publicly available, etc.

With the exception of certain limited exclusions delineated in UT Southwestern Policy INP-101 (https://www.utsouthwestern.edu/edumedia/edufiles/about_us/admin_offices/technology_development/Current INP-101 (2022.10.04).pdf), the rights in such software are owned by the Board of Regents of The University of Texas System (“Board of Regents”), of which UT Southwestern is a component institution. Any public release of the source code of such software (e.g., through online software repositories such as GitHub and other similar tools) shall 1) be done only to the extent necessary to meet such scholarly obligations, and 2) be accompanied with the copyright and license language shown below (italicized, bold):

Copyright (c) [insert appropriate year] The University of Texas Southwestern Medical Center.

Redistribution and use in source and binary forms, with or without modification, are permitted for academic research use only (subject to the limitations in the disclaimer below) provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

ANY USE OR REDISTRIBUTION OF THIS SOFTWARE FOR COMMERCIAL PURPOSES, WHETHER IN SOURCE OR BINARY FORM, WITH OR WITHOUT MODIFICATION, IS EXPRESSLY PROHIBITED; ANY USE OR REDISTRIBUTION BY A FOR-PROFIT ENTITY SHALL COMPRISE USE OR REDISTRIBUTION FOR COMMERCIAL PURPOSES.

NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE GRANTED BY THIS LICENSE. THIS SOFTWARE, AND ANY ACCOMPANYING DOCUMENTATION, IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE OR ANY OF ITS ACCOMPANYING DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Any public release of software source code owned by the Board of Regents (as described above) for purposes beyond what is described above, and/or without insertion of the above copyright and license language, is prohibited, unless the author(s) of such source code obtains express written permission from the Office for Technology Development. By way of example, if circumstances require that a different license be used, the author(s) of such source code must first consult with the Office for Technology Development and obtain such permission.

Please contact the UT Southwestern Office for Technology Development with any questions.

Email: technologydevelopment@utsouthwestern.edu