Reuse and maintenance practices among divergent forks in three software ecosystems
Open accessThe DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Abstract
With the rise of social coding platforms that rely on distributed version control systems, software reuse is also on the rise. Many software developers leverage this reuse by creating variants through forking, to account for different customer needs, markets, or environments. Forked variants then form a so-called software family; they share a common code base and are maintained in parallel by same or different developers. As such, software families can easily arise within software ecosystems, which are large collections of interdependent software components maintained by communities of collaborating contributors. However, little is known about the existence and characteristics of such families within ecosystems, especially about their maintenance practices. Improving our empirical understanding of such families will help build better tools for maintaining and evolving such families. We empirically explore maintenance practices in such fork-based software families within ecosystems of open-source software. Our focus is on three of the largest software ecosystems existence today: , , and . We identify and analyze software families that are maintained together and that exist both on the official distribution platform (Google play, , and ) as well as on GitHub , allowing us to analyze reuse practices in depth. We mine and identify 38 software families, 526 software families, and 8,837 software families from the ecosystems of , , and , to study their characteristics and code-propagation practices. We provide scripts for analyzing code integration within our families. Interestingly, our results show that there is little code integration across the studied software families from the three ecosystems. Our studied families also show that techniques of direct integration using git outside of GitHub is more commonly used than GitHub pull requests. Overall, we hope to raise awareness about the existence of software families within larger ecosystems of software, calling for further research and better tools support to effectively maintain and evolve them.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Curating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365 · cited 1×
“md file; and (7) has a number of forks ≥ 2 to reduce the chance of finding student assignments (Munaiah et al. 2017).”
BackgroundGamalielsson, J., & Lundell, B. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2013.11.1077 · Cited by 125 · cited 1×
“2019; 2020) or on the community dynamics as influenced by forking (Gamalielsson and Lundell 2014).”
BackgroundCode Forking, Governance, and Sustainability in Open Source Software
Nyman, L., & Lindman, J. (2013) · Technology Innovation Management Review · doi:10.22215/timreview/644 · Cited by 81
A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes
Robles, G., & González-Barahona, J. M. (2012) · IFIP Advances in Information and Communication Technology · doi:10.1007/978-3-642-33442-9_1 · Cited by 67 · cited 3×
“2020) and (Robles and González-Barahona 2012)), we investigate additional phenomena, such as code propagation with RQ3.”
BackgroundPerspectives on Code Forking and Sustainability in Open Source Software
Nyman, L., Mikkonen, T., Lindman, J., & Fougère, M. (2012) · IFIP Advances in Information and Communication Technology · doi:10.1007/978-3-642-33442-9_21 · Cited by 45
How has forking changed in the last 20 years?: a study of hard forks on GitHub
Zhou, S., Vasilescu, B., & Kästner, C. (2020) · Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering · doi:10.1145/3377811.3380412 · Cited by 36
Causes of merge conflicts: a case study of ElasticSearch
Mahmood, W., Chagama, M., Berger, T., & Hebig, R. (2020) · Proceedings of the 14th International Working Conference on Variability Modelling of Software-Intensive Systems · doi:10.1145/3377024.3377047 · Cited by 10
Self-citation
Cited by
PaReco: patched clones and missed patches among the divergent variants of a software family
Ramkisoen, P. K., Businge, J., van Bladel, B., Decan, A., Demeyer, S., De Roover, C., & Khomh, F. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3549112 · Cited by 10
Self-citationVariant Forks - Motivations and Impediments
Businge, J., Zerouali, A., Decan, A., Mens, T., Demeyer, S., & De Roover, C. (2022) · 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00105 · Cited by 7
“[10] also investigated the interaction between mainline and variants.”
BackgroundMethodInfluentialSelf-citationPatchTrack: Analyzing ChatGPT's Impact on Software Patch Decision-Making in Pull Requests
Ogenrwot, D., & Businge, J. (2024) · Proceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3691620.3695338 · Cited by 3
Self-citationAnalyzing Variant Forks of Software Repositories from Social Coding Platforms
Businge, J., Abdi, M., & Demeyer, S. (2023) · Software Ecosystems · doi:10.1007/978-3-031-36060-2_6 · Cited by 1
Self-citationAgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub
Ogenrwot, D., & Businge, J. (2026) · Proceedings of the 3rd ACM International Conference on AI-Powered Software · doi:10.1145/3805760.3814923
Self-citation
Metadata
- Authors
- Businge, J., Openja, M., Nadi, S., & Berger, T.
- Venue
- Empirical Software Engineering
- Published
- 2022-03
- Volume
- 27
- Issue
- 2
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W4214871480
- Cited by
- 37
- References
- 7
- FWCI
- 7.05
- Type
- journal article
- Language
- en
- Open access
- hybrid
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Reuse and maintenance practices among divergent forks in three software ecosystems. https://app.cochat.ai/papers/10.1007/s10664-021-10078-2
- The paper
- Businge, J., Openja, M., Nadi, S., & Berger, T. (2022). Reuse and maintenance practices among divergent forks in three software ecosystems. Empirical Software Engineering. https://doi.org/10.1007/s10664-021-10078-2
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.