Open Source Is Not One Thing: A Typology of Open-Source Software Sub-Genres

Jul 16, 2026

Open source software (OSS) is diverse rather than uniform: a project’s purpose, governance, and funding shape community formation, contributor behavior, and maintenance practices. Empirical studies often sample OSS as a whole, risking overgeneralized conclusions across fundamentally different community and organizational models. This work proposes fourteen distinguishable OSS sub-genres, grounded in a multi-source review of 3,925 papers, and evaluates generalizability through a research agenda.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages5

Reading Time13 min

Introduction

Why OSS is not homogeneous

Practical implications for contribution and sustainability

Related Work

Existing OSS classification schemes

Contributions and Research Agenda

Typology and framework

Research agenda and generalizability

Open Source Is Not One Thing: A Typology of Open-Source Software Sub-Genres Mohamed Ouf [24blr2@queensu.ca](24blr2@queensu.ca)[ ](24blr2@queensu.ca)Queen’s University Kingston, Ontario, Canada Rowan Hussein [rhuss060@uottawa.ca](rhuss060@uottawa.ca)[ ](rhuss060@uottawa.ca)University of Ottawa Ottawa, Ontario, Canada arXiv :2607 .0 1750v 1 [ cs .CY] 2 Jul 2026 Abstract Open source software (OSS) is not homogeneous. A project’s purpose, governance, and funding shape how its community forms, who contributes, and how the software is maintained, yet empirical research often samples OSS broadly and reports findings as if they held for open source as a whole. We argue that OSS comprises distinguishable sub-genres, and that the sub-genre a study samples bounds how far its findings generalize. Using a light, multisource review that screens 3,925 unique papers, we synthesize a typology of fourteen OSS sub-genres, from well-studied ones such as community-driven, company-backed, foundation-governed, research and scientific, and open source for social good (OSS4SG), to under-studied ones such as multi-company co-opetition, protestware, and open-source appropriate technology. We place the subgenres in a framework that records each one’s primary driver, governance, and funding, with its maturity in the literature and representative projects, and we present a research agenda whose central question is whether findings established on one sub-genre transfer to others. The contribution is the typology and the agenda rather than a complete census, and we mark the sub-genres whose empirical support is thin. CCS Concepts • Software and its engineering → Open source model. Keywords open source software, software ecosystems, typology, taxonomy, empirical software engineering, mining software repositories, software sustainability, OSS4SG 1 Introduction Open source software (OSS) is not one thing. Empirical research nonetheless samples it as though it were. Studies draw a set of popular GitHub projects, fit models of contributor retention, onboarding, or code quality, and report the results for open source in general. The implicit assumption is that a community Linux distribution, a single-vendor database, a university research library, a humanitarian health-records system, and a one-person utility differ only in size and popularity. They do not. They differ in why the project exists, who decides its direction, how the work is paid for, and how the community behaves. Recent evidence makes the difference concrete. A comparison of mission-driven open source for social good (OSS4SG) and conventional OSS reports different community structure, contributor retention, and code-quality management, with OSS4SG communities retaining contributors (“sticky”) and conventional projects attracting many who do not stay (“magnetic”) [39]. The newcomer-to-core pathway also differs by sub-genre, and contributors in OSS4SG reach core status at higher rates and through more than one route [38] . Even the way a newcomer first joins, whether through a mentorship program, a hackathon, or independently, is associated with how long they stay [36] . When two sub-genres diverge this far, a retention model or an onboarding program validated on one of them need not hold for the others. Coarse metrics such as stars and commit counts hide the structure that decides whether a finding generalizes. The distinction matters in practice as well. A developer deciding where to contribute gains from knowing what kind of project they are approaching, because its governance, funding, and community behavior set what a first contribution takes and how a newcomer is received. Social barriers at the first contribution already push newcomers to abandon projects [49], and the path into a single-vendor product differs from the path into a volunteer distribution or a research library. Sub-genre bears on sustainability too. How a project is funded and who maintains it, a

FAQs

Why do the authors argue that OSS is not one homogeneous category?

They note that OSS projects differ in purpose, governance, funding, and resulting community behavior, so findings from one kind of project may not transfer to others.

How many OSS sub-genres does the paper propose, and how were they derived?

The paper synthesizes a typology of fourteen OSS sub-genres using a light, multi-source review that screens 3,925 unique papers.

What is the central research agenda question proposed by the authors?

Whether empirical findings established on one OSS sub-genre generalize to other sub-genres, with sub-genre treated as a variable to report and control in studies.

Jul 16, 2026

Upload by Olivia Brown