Palantir: Early Detection of Development Conflicts Arising from Parallel Code Changes
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
The earlier a conflict is detected, the easier it is to resolve-this is the main precept of workspace awareness. Workspace awareness seeks to provide users with information of relevant ongoing parallel changes occurring in private workspaces, thereby enabling the early detection and resolution of potential conflicts. The key approach is to unobtrusively inform developers of potential conflicts arising because of concurrent changes to the same file and dependency violations in ongoing parallel work. This paper describes our research goals, approach, and implementation of workspace awareness through Palantír and includes a comprehensive evaluation involving two laboratory experiments. We present both quantitative and qualitative results from the experiments, which demonstrate that the use of Palantír, as compared to not using Palantír 1) leads to both earlier detection and earlier resolution of a larger number of conflicts, 2) leaves fewer conflicts unresolved in the code base that was ultimately checked in, and 3) involves reasonable overhead. Furthermore, we report on interesting changes in users' behavior, especially how conflict resolution strategies changed among Palantír users.
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
Awareness and coordination in shared workspaces
Dourish, P., & Bellotti, V. (1992) · Proceedings of the 1992 ACM conference on Computer-supported cooperative work - CSCW '92 · doi:10.1145/143457.143468 · Cited by 2,550 · cited 1×
“The notion of awareness has gathered considerable attention in the Computer-Supported Cooperative Work (CSCW) literature, where it was first characterized as “an understanding of the activities of others, which provides a context for your own activity” [18].”
BackgroundA field study of the software design process for large systems
Curtis, B., Krasner, H., & Iscoe, N. (1988) · Communications of the ACM · doi:10.1145/50087.50089 · Cited by 2,076
Distance, dependencies, and delay in a global collaboration
Herbsleb, J. D., Mockus, A., Finholt, T. A., & Grinter, R. E. (2000) · Proceedings of the 2000 ACM conference on Computer supported cooperative work · doi:10.1145/358916.359003 · Cited by 395
Why distance matters: effects on cooperation, persuasion and deception
Bradner, E., & Mark, G. (2002) · Proceedings of the 2002 ACM conference on Computer supported cooperative work · doi:10.1145/587078.587110 · Cited by 224 · cited 1×
“To mitigate this risk, we designed our experiments to use confederates, research personnel acting as virtual team members [7], [50].”
MethodCommunication networks in geographically distributed software development
Cataldo, M., & Herbsleb, J. D. (2008) · Proceedings of the 2008 ACM conference on Computer supported cooperative work · doi:10.1145/1460563.1460654 · Cited by 98 · cited 1×
“This has implications for a large body of work involving empirical studies that use communication as a proxy for studying coordination [8], [9], [33], [48], [55].”
Background
Cited by
On the Nature of Merge Conflicts: A Study of 2,731 Open Source Java Projects Hosted by GitHub
Ghiotto, G., Murta, L., Barros, M., & van der Hoek, A. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2871083 · Cited by 67
“CASI [34], CloudStudio [35], CoDesign [36], CollabVS [37], Crystal [22], FastDash [38], Palantír [39], SafeCommit [40], Syde [41], and WeCode [42] all monitor developer workspaces to detect when two developers begin modifying the same file or different files that exhibit some syntactic or semantic dependency.”
BackgroundUnderstanding semi-structured merge conflict characteristics in open-source Java projects
Accioly, P., Borba, P., & Cavalcanti, G. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9586-1 · Cited by 48
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
Behind Developer Contributions on Conflicting Merge Scenarios
Vale, G., Fernandes, E., Figueiredo, E., & Apel, S. (2023) · 2023 IEEE 23rd International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam59687.2023.00014 · Cited by 1
Metadata
- Authors
- Sarma, A., Redmiles, D. F., & van der Hoek, A.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2012-07
- Volume
- 38
- Issue
- 4
- Pages
- 889-908
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- OpenAlex
- W2155951198
- Cited by
- 105
- References
- 5
- FWCI
- 20.35
- Type
- journal article
- Language
- en
- Open access
- closed
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
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.