Open-source Software Sustainability Models: Initial White Paper From the Informatics Technology for Cancer Research Sustainability and Industry Partnership Working Group

Abstract

Background The National Cancer Institute Informatics Technology for Cancer Research (ITCR) program provides a series of funding mechanisms to create an ecosystem of open-source software (OSS) that serves the needs of cancer research. As the ITCR ecosystem substantially grows, it faces the challenge of the long-term sustainability of the software being developed by ITCR grantees. To address this challenge, the ITCR sustainability and industry partnership working group (SIP-WG) was convened in 2019. Objective The charter of the SIP-WG is to investigate options to enhance the long-term sustainability of the OSS being developed by ITCR, in part by developing a collection of business model archetypes that can serve as sustainability plans for ITCR OSS development initiatives. The working group assembled models from the ITCR program, from other studies, and from the engagement of its extensive network of relationships with other organizations (eg, Chan Zuckerberg Initiative, Open Source Initiative, and Software Sustainability Institute) in support of this objective. Methods This paper reviews the existing sustainability models and describes 10 OSS use cases disseminated by the SIP-WG and others, including 3D Slicer, Bioconductor, Cytoscape, Globus, i2b2 (Informatics for Integrating Biology and the Bedside) and tranSMART, Insight Toolkit, Linux, Observational Health Data Sciences and Informatics tools, R, and REDCap (Research Electronic Data Capture), in 10 sustainability aspects: governance, documentation, code quality, support, ecosystem collaboration, security, legal, finance, marketing, and dependency hygiene. Results Information available to the public reveals that all 10 OSS have effective governance, comprehensive documentation, high code quality, reliable dependency hygiene, strong user and developer support, and active marketing. These OSS include a variety of licensing models (eg, general public license version 2, general public license version 3, Berkeley Software Distribution, and Apache 3) and financial models (eg, federal research funding, industry and membership support, and commercial support). However, detailed information on ecosystem collaboration and security is not publicly provided by most OSS. Conclusions We recommend 6 essential attributes for research software: alignment with unmet scientific needs, a dedicated development team, a vibrant user community, a feasible licensing model, a sustainable financial model, and effective product management. We also stress important actions to be considered in future ITCR activities that involve the discussion of the sustainability and licensing models for ITCR OSS, the establishment of a central library, the allocation of consulting resources to code quality control, ecosystem collaboration, security, and dependency hygiene.

Addressing barriers in FAIR data practices for biomedical data

“…This instability in project longevity makes people unwilling to adopt new projects and create linkages between existing and new platforms, and often new initiatives recreate existing functionality in a defunct project whose funding expired. Recently, institutes like the National Cancer Institute (NCI) 15 , NIAID, the National Heart, Lung, and Blood Institute (NHLBI), and the National Eye Institute (NEI) have developed dedicated mechanisms to support informatics and data science research and tool development. These programs are essential to ensure investments in FAIR sharing infrastructure are not squandered by promoting sustainable research software development, fostering a robust developer community, and developing career paths for research software engineers.…”

An Environment for Sustainable Research Software in Germany and Beyond: Current State, Open Challenges, and Call for Action

“…Therefore, it is necessary to comprehensively motivate sustainable research software practice. In the following, we identify stakeholders of research software (see [58][59][60]), and explicate their particular motivations for sustainable research software. Subsequently, we specify challenges towards satisfying the demands of the individual stakeholders.…”