Code Forking and Software Development Project Sustainability: Evidence from GitHub
Bibliographic record
Abstract
Increasing numbers of software projects-proprietary and open source-are developed and maintained by heterogeneous communities of developers. As a result, the sustainability of software projects has become an important issue for members of those communities and their user bases. Building on the idea of forking as “an individual developer's behavior of copying an existing project's code base” and its signaling of active community involvement and participation, we ask the question: How does forking impact the sustainability of software development projects? Through the curation of digital trace data gathered from 749 software projects hosted on GitHub, we develop a longitudinal model to explain the contributions of various types of forking on software development project sustainability. Our findings contribute to research by moving beyond the conceptualization of forking as a monolithic concept and shows the benefits of certain types of forking for software projects' sustainability.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.011 | 0.088 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.005 | 0.008 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.003 | 0.005 |
| Open science | 0.002 | 0.006 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".