CoChat
Sign Up
Cited by 1Open Source Software InnovationsSoftware Engineering ResearchSoftware Engineering Techniques and Practices

The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.

Behind Developer Contributions on Conflicting Merge Scenarios

Vale, Gustavo, Fernandes, Eduardo, Figueiredo, Eduardo, Apel, Sven·2023·2023 IEEE 23rd International Working Conference on Source Code Analysis and Manipulation (SCAM)
DOI 10.1109/scam59687.2023.00014
Open this paper in CoChat — free account

Abstract

Context: The success of Open Source Software (OSS) projects typically depends on simultaneous contributions of several developers. These contributions often affect the same changing source files and may lead to merge conflicts when integrated. Previous studies investigated the reduction of conflicting merge scenarios. However, empirical evidence on the involvement of OSS contributors in conflicting merge scenarios is scarce. Objective: We aim to fill this gap with a large-scale quantitative study with the goal of understanding: 1) the extent in which OSS contributors are involved in conflicting merge scenarios; 2) characteristics of these contributors; and 3) characteristics of changing source files. Method: We collect both contributor data and contribution data from 66 popular GitHub projects and analyze data of 2972 distinct contributors who were involved in at least one conflicting merge scenario. We rely on both descriptive and inferential statistics to address our research questions. Results: About 80% of the analyzed contributors are involved in only one or two conflicting merge scenarios. Additionally, 42 out of the 66 projects had its top-one contributor as the one mostly involved in conflicting merge scenarios. Finally, only a small set of changing source files are involved in conflicting merge scenarios. Conclusions: We advocate that training the typically small group of contributors involved in conflicting merge scenarios could significantly reduce the number of merge conflicts.

Overview

Integrity signals

Registry

Crossref · 10.1109/scam59687.2023.00014

Cites

2 of 2 references verified0 citation errors · 0 not checkable

Statistics

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

Verification

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?

Citations

Cites

Flagged first, then by citations

Show all 2 references

Research works printed but not linked: 41

  1. 10.1007/s10664-017-9586-1 · DOI · Paper page
  2. 10.1145/2351676.2351694 · DOI
  3. 10.1145/2025113.2025141 · DOI
  4. 10.1109/32.6156 · DOI
  5. 10.1145/1240624.1240823 · DOI
  6. 10.1145/1453101.1453107 · DOI
  7. 10.1016/j.jss.2018.09.016 · DOI · Paper page
  8. 10.1145/2025113.2025139 · DOI
  9. 10.1109/HICSS.2006.101 · DOI · Paper page
  10. 10.1109/TSE.2005.73 · DOI
  11. 10.1016/j.infsof.2020.106347 · DOI
  12. 10.1109/TSE.2018.2871083 · DOI · Paper page
  13. 10.1109/tse.2022.3215289 · DOI
  14. 10.1145/2884781.2884826 · DOI
  15. 10.1109/ICSE.2015.55 · DOI
  16. 10.1109/ICSE.2012.6227180 · DOI
  17. 10.1080/01621459.1972.10481251 · DOI
  18. 10.1109/ISSRE5003.2020.00016 · DOI
  19. 10.1109/ICSE.2017.23 · DOI
  20. 10.1145/2597073.2597074 · DOI
  21. 10.1109/ICSE.2013.6606619 · DOI
  22. 10.1109/TSE.2022.3143766 · DOI
  23. 10.1007/s10515-017-0227-0 · DOI
  24. 10.1016/j.jss.2017.09.032 · DOI
  25. 10.1145/3377024.3377047 · DOI · Paper page
  26. 10.1002/smr.2435 · DOI
  27. 10.1145/567793.567795 · DOI · Paper page
  28. 10.1007/s10664-018-9674-x · DOI
  29. 10.1109/ESEM.2019.8870173 · DOI
  30. 10.1145/2597073.2597113 · DOI
  31. 10.1145/2594458 · DOI
  32. 10.1145/2597073.2597107 · DOI
  33. 10.1109/MSR.2009.5069497 · DOI
  34. 10.1109/TSE.2011.64 · DOI
  35. 10.1145/2441776.2441791 · DOI
  36. 10.1109/TSE.2016.2584053 · DOI · Paper page
  37. 10.1109/SBES.2010.26 · DOI
  38. 10.1145/2568225.2568315 · DOI
  39. 10.1109/TSE.2021.3130098 · DOI
  40. 10.1007/s10664-019-09774-x · DOI
  41. 10.1007/978-3-642-29044-2 · DOI · Paper page

Cited by

Sorted by citations

See all 1

Metadata

Authors
Vale, G., Fernandes, E., Figueiredo, E., & Apel, S.
Affiliations
  • Saarland University (DE)
  • University of Southern Denmark (DK)
  • Universidade Federal de Minas Gerais (BR)
ORCID
Venue
2023 IEEE 23rd International Working Conference on Source Code Analysis and Manipulation (SCAM)
Publisher
IEEE
Published
2023-10-02
Pages
25-36
DOI
10.1109/scam59687.2023.00014
OpenAlex
W4389988511
Cited by
1
References
2
Citations by year
2026: 1
FWCI
0.30
Type
conference paper
Language
en
Open access
closed
Licence
Locations
  • IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) (publishedVersion)
  • University of Southern Denmark Research Portal (University of Southern Denmark) (publishedVersion)
Funders
EMI
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
merge conflicts, open source software, developer contributions, GitHub projects

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