English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Tools annual

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Presents the access of premium content as premium feature

Premium Content

Global: Zendy Plus annual

Global: Zendy Free Plan

Motivation: Society's dependence on Open Source Software (OSS) and thecommunities that maintain the OSS is ever-growing. So are the potential risksof, e.g., vulnerabilities being introduced in projects not actively maintained.By assessing an OSS project's capability to stay viable and maintained overtime without interruption or weakening, i.e., the OSS health, users canconsider the risk implied by using the OSS as is, and if necessary, decidewhether to help improve the health or choose another option. However, suchassessment is complex as OSS health covers a wide range of sub-topics, andexisting support is limited. Aim: We aim to create an overview ofcharacteristics that affect the health of an OSS project and enable theassessment thereof. Method: We conduct a snowball literature review based on astart set of 9 papers, and identify 146 relevant papers over two iterations offorward and backward snowballing. Health characteristics are elicited and codedusing structured and axial coding into a framework structure. Results: Thefinal framework consists of 104 health characteristics divided among 15 themes.Characteristics address the socio-technical spectrum of the community of actorsmaintaining the OSS project, the software and other deliverables beingmaintained, and the orchestration facilitating the maintenance. Characteristicsare further divided based on the level of abstraction they address, i.e., theOSS project-level specifically, or the project's overarching ecosystem ofrelated OSS projects. Conclusion: The framework provides an overview of thewide span of health characteristics that may need to be considered whenevaluating OSS health and can serve as a foundation both for research andpractice.

How to characterize the health of an Open Source Software project? A snowball literature review of an emerging practice