1 / 13

Releasing Research Software Source Code

Releasing Research Software Source Code. A Discussion. Natasha M. Wright, MA, MPH Presidential Management Fellow December 17, 2014. Open Source Movement. S oftware that can be freely used, changed, and shared by anyone Unlimited number of contributors

hobsons
Télécharger la présentation

Releasing Research Software Source Code

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Releasing Research Software Source Code A Discussion Natasha M. Wright, MA, MPHPresidential Management Fellow December 17, 2014

  2. Open 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

  3. Open Source @ NCIEmpowering Cancer Research through Open Development • 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/

  4. Guidelines 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

  5. Guidelines 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

  6. Guidelines 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

  7. Guidelines 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

  8. Summary • Select a platform to release software code • Select and attach a license / model agreement • Acknowledge funding sources & provide citation instructions

  9. Summary • Include disclaimers • Disseminate & track in compliance with federal guidelines

  10. NCI Contact Ms. Wendy Patterson, Esq. Technology Transfer Advisor NCI Technology Transfer Center NCI Office of Management pattersw@mail.nih.gov 240-276-5498

  11. OSS Draft Guidelines For Comments https://nciphub.org/resources/790

  12. Acknowledgments • Ishwar Chandramouliswaran • JuliKlemm • Richard Lambert • Carl McCabe • Wendy Patterson

  13. Open 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

More Related