Papers › Forking Around: Correlation of forking practices with the success of a project
Forking Around: Correlation of forking practices with the success of a project
Anurag Dhasmana, Arindaam Roy, Divjeet Singh Jas, Kiranpreet Kaur, Pinn Prugsanapan
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Forking-based development has made it easier and straightforward for developers to contribute to open-source software (OSS). Developers can fork an existing project and add changes in their local version without interrupting the development process in the main project. Despite the efficiency of OSS, more than 80% of the projects are not sustainable. Identifying the elements related to OSS success can enlighten developers regarding the sustainability of a project. In our study, we explore whether or not the inefficiencies which arise due to forking-based development like redundant development, fragmented communities, lack of modularity, etc. have any relation to the outcome of a project in terms of sustainability. We formulate eight metrics to quantify attributes for projects in the ASFI dataset. To find the correlation between the metrics and the success of a project, we built a logistic regression model to metrics with significant p-values and performed backward stepwise regression analysis, using the stepAIC function in R to cross-check our findings. The findings show that modularity, centralized management index, and hard forks are consequential for the success of a project. Developers can use the outcomes of our research to plan and structure their projects to increase the probability of their success.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections