Cited by 7Open Source Software InnovationsSoftware Engineering ResearchSoftware Engineering Techniques and Practices

Variant Forks - Motivations and Impediments

Open access
Businge, John, Zerouali, Ahmed, Decan, Alexandre, Mens, Tom, Demeyer, Serge, De Roover, Coen·2022·2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)

Abstract

Social coding platforms centred around git provide explicit facilities to share code between projects: forks, pull requests, cherry-picking to name but a few. Variant forks are an interesting phenomenon in that respect, as they permit for different projects to peacefully co-exist, yet explicitly acknowledge the common ancestry. Several researchers analysed forking practices on open source platforms and observed that variant forks get created frequently. However, little is known on the motivations for launching such a variant fork. Is it mainly technical (e.g., diverging features), governance (e.g., diverging interests), legal (e.g., diverging licences), or do other factors come into play? We report the results of an exploratory qualitative analysis on the motivations behind creating and maintaining variant forks. We surveyed 105 maintainers of different active open source variant projects hosted on GitHub. Our study extends previous findings, identifying a number of fine-grained common motivations for launching a variant fork and listing concrete impediments for maintaining the co-existing projects.

Integrity signals

Registry

Crossref · 10.1109/saner53432.2022.00105

Cites

3 of 3 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Hard forks cannot always be avoided, they are a relatively new phenomenon despite platforms like GitHub lowering the bar and making it easier for people to create them.

    “While hard forks cannot always be avoided, they are a relatively new phenomenon despite platforms like GitHub lowering the bar and making it easier for people to create them (Businge et al. 2022).”
  • Hard forks can be motivated by legal disputes, technical differences, and vendor competition.

    “While hard forks can be motivated by legal disputes (Businge et al. 2022), technical differences (Overhage and Widjaja 2022), and vendor competition (Karhu et al. 2020), the multifacetedness of hard forks remains a bit of a paradox in open source as they represent a significant shock to an open source project, yet provide a path towards sustainability (Nyman et al. 2012;Acquatella et al. 2024) th”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Businge, J., Zerouali, A., Decan, A., Mens, T., Demeyer, S., & De Roover, C.
Affiliations
  • University of Antwerp (BE)
  • Vrije Universiteit Brussel (BE)
  • University of Mons (BE)
  • Vrije Universiteit Brussels,Brussels,Belgium
Venue
2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)
Publisher
IEEE
Published
2022-03
Pages
867-877
OpenAlex
W4286530330
Cited by
7
References
3
Citations by year
2025: 2 · 2024: 2 · 2023: 1 · 2022: 2
FWCI
2.28
Type
conference paper
Language
en
Open access
Locations
  • IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) (publishedVersion)
  • ORBi UMONS (submittedVersion, other-oa)
  • VUBIR (Vrije Universiteit Brussel) (submittedVersion)
Funders
  • Fonds De La Recherche Scientifique - FNRS (O.0157.18F-RG43)
  • Fonds Wetenschappelijk Onderzoek
  • Vlaamse regering
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
software forks, open source software, software governance, software licensing, GitHub, software evolution

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