Nat

iona

l Can

cer

Inst

itute

Releasing Research Software Source CodeReleasing Research Software Source Code

Natasha M. Wright, MA, MPHPresidential Management Fellow

December 17, 2014

A Discussion

Open Source MovementOpen Source Movement

• Software that can be freely used, changed, and shared by anyone

• Unlimited number of contributors

• Great tool for collaboration, innovation, and quality improvement

• Distributed under licenses only approved by the Open Source Initiative (OSI) to prevent proliferation of licenses

• Center for Biomedical Informatics and Information Technology (CBIIT) seeks to

• Support the rapid informatics innovation

• Enable better tools by crowdsourcing innovation

• Empower the community to drive priorities

• Examples

• GitHub Open Source Repositories

• NASA Open Source Initiative

• NCIP Open Source at http://ncip.github.io/

Open Source @ NCIEmpowering Cancer Research through Open Development

Open Source @ NCIEmpowering Cancer Research through Open Development

Guidelines for Releasing Open Source Research SoftwareGuidelines for Releasing Open Source Research Software

• Applicable for re-suable, polished source code & “one-off” code

• FAQs format with general questions, pre-release guidance, post-release guidance, and appendices

• Researched policies and best practices

• Drafted in consultation with OGC, TTC, CBIIT/NCIP, OCE, NCBI, & DCEG/CCR research communities

Guidelines at a Glance: General QuestionsGuidelines at a Glance: General Questions

• Source code availability

– Upon request

– Open source

• Advantages of ‘open source’ software

• Determination of NCI rights to release software code when developed with a contractor

Guidelines at a Glance: Pre-release GuidanceGuidelines at a Glance: Pre-release Guidance

• Platforms for open source software release

– NCI webserver

– Social coding, programming language sites

• Etiquette to follow when using social media

• Need for & choice of license for release of software code

• Credit NIH as a source of funding in all or part, DOIs

• Disclaimers

Guidelines at a Glance: Post-release GuidanceGuidelines at a Glance: Post-release Guidance

• Expectation of technical support in perpetuity: Not required

• Ability to restrict access and use of the software: No

• Outreach and monitor use and impact: if you can/want

SummarySummary

1. Select a platform to release software code

2. Select and attach a license / model agreement

3. Acknowledge funding sources & provide citation instructions

SummarySummary

4.Include disclaimers

5.Disseminate & track in compliance with federal guidelines

NCI ContactNCI Contact

Ms. Wendy Patterson, Esq.

Technology Transfer Advisor

NCI Technology Transfer Center

NCI Office of Management

pattersw@mail.nih.gov

240-276-5498

OSS Draft Guidelines For CommentsOSS Draft Guidelines For Comments

https://nciphub.org/resources/790

AcknowledgmentsAcknowledgments

• Ishwar Chandramouliswaran

• Juli Klemm

• Richard Lambert

• Carl McCabe

• Wendy Patterson

Open ForumOpen Forum

• Capture go-to resources for documenting software code (Q9)

• Topics missing from this guide, but should be included

• Information highlighted today that seems unclear or confusing

• Structure/order of the guide

• Specific questions that need more refinement

• Need/relevance for such a resource outside of NCI

• Logical next steps