论文标题
如何表征开源软件项目的健康?新兴练习的雪球文学评论
How to characterize the health of an Open Source Software project? A snowball literature review of an emerging practice
论文作者
论文摘要
动机:社会对开源软件(OSS)和维护OSS的社区的依赖正在不断发展。例如,在未积极维护的项目中引入漏洞的潜在风险也是如此。通过评估OSS项目保持可行的能力,并随着时间的推移而无需中断或弱化,即OSS健康,用户可以考虑使用OSS所隐含的风险,并在必要时决定是否帮助改善健康或选择其他选择。但是,这种评估很复杂,因为OSS健康涵盖了广泛的子主题,并且现有的支持受到限制。目的:我们旨在概述影响OSS项目健康的特征并实现其评估。方法:我们根据9篇论文的起始集进行了雪球文献综述,并在两次前后滚雪球的两次迭代中确定了146篇相关论文。使用结构化和轴向编码将健康特征引发和编码为框架结构。结果:最终框架由104个健康特征组成,分为15个主题。特征涉及维护OSS项目,维护软件和其他可交付成果的参与者社区的社会技术范围,并促进了促进维护的编排。特征是根据他们所说的抽象水平(即OSS项目级别的特定或项目相关OSS项目的总体生态系统)进一步分配的。结论:该框架概述了评估OSS健康时可能需要考虑的广泛健康特征,并可以作为研究和实践的基础。
Motivation: Society's dependence on Open Source Software (OSS) and the communities that maintain the OSS is ever-growing. So are the potential risks of, e.g., vulnerabilities being introduced in projects not actively maintained. By assessing an OSS project's capability to stay viable and maintained over time without interruption or weakening, i.e., the OSS health, users can consider the risk implied by using the OSS as is, and if necessary, decide whether to help improve the health or choose another option. However, such assessment is complex as OSS health covers a wide range of sub-topics, and existing support is limited. Aim: We aim to create an overview of characteristics that affect the health of an OSS project and enable the assessment thereof. Method: We conduct a snowball literature review based on a start set of 9 papers, and identify 146 relevant papers over two iterations of forward and backward snowballing. Health characteristics are elicited and coded using structured and axial coding into a framework structure. Results: The final framework consists of 104 health characteristics divided among 15 themes. Characteristics address the socio-technical spectrum of the community of actors maintaining the OSS project, the software and other deliverables being maintained, and the orchestration facilitating the maintenance. Characteristics are further divided based on the level of abstraction they address, i.e., the OSS project-level specifically, or the project's overarching ecosystem of related OSS projects. Conclusion: The framework provides an overview of the wide span of health characteristics that may need to be considered when evaluating OSS health and can serve as a foundation both for research and practice.