On the relation between Github communication activity and merge conflicts

Vale, Gustavo; Schmid, Angelika; Santos, Alcemir Rodrigues; Almeida, Eduardo Santana de; Apel, Sven

doi:10.1007/s10664-019-09774-x

Cited by 19 publications

(17 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For comparing the comprehensibility of Go and Java, 50 popular, open-source projects of each language are selected from GitHub that fulfill the criteria presented in Section 2 [17]. The popularity of a project is measured based on the number of stars, as followed in [18], [19]. Table I shows the top 5 projects from each language along with their number of stars and LOCs.…”

Section: Experimentation and Results Analysismentioning

confidence: 99%

Analyzing Program Comprehensibility of Go Projects

Asad¹

2021

Proceedings of the 33rd International Conference on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Program comprehension is one of the most important activities in developing and maintaining software. Although existing studies have examined aspects of Go such as design patterns, code smells and comment density, the comprehensibility of Go has not been explored yet. This study analyzes the comprehensibility of Go by comparing it with Java based on five metrics namely Too Long Files, Too Long Methods, Nesting Depth, Lack of Cohesive Comments and Duplicate Comments. For comparison, 50 popular, diverse and open-source projects are selected from each language. Results show that Go projects outperform Java in terms of Nesting Depth, Lack of Cohesive Comments and Duplicate Comments.

show abstract

Section: Experimentation and Results Analysismentioning

confidence: 99%

Analyzing Program Comprehensibility of Go Projects

Asad¹

2021

Proceedings of the 33rd International Conference on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…2) Data Collection: For each project, we plan to collect data from two sources: GITHUB API and GH ARCHIVE 2 . We use two sources because the official GITHUB API has put limitation access to a project's historical event 3 . Tab.…”

Section: A Step 1 Data Collection and Clean 1) Sampling Targeted Proj...mentioning

confidence: 99%

“…Access via Google BigQuery: https://console.cloud.google.com/bigquery?project=githubar3 The current version of the GITHUB API only allows to access 300 events or events in up to the past 90 days, whichever is met first.…”

mentioning

confidence: 99%

Cross-status Communication and Project Outcomesin OSS Development A Language Style Matching Perspective

Han¹,

Wang²,

Yang³

et al. 2021

Preprint

View full text Add to dashboard Cite

Background. The success of an open source software (OSS) project requires effective communication among its members. Given that OSS projects often have established social status systems, much communication may happen between individuals of different statuses, particularly, elite developers who have project management privileges and ordinary project contributors. Since sociolinguistics literature and our prior work have found that groups in different status would be likely develop different language styles, which may hinder critical cross-status communication, and hereby influence the project's outcomes. Objectives. We seek to develop an understanding of cross-status communication, as well as its impacts on an OSS project's outcomes in terms of productivity and quality. The anticipated results describe the linguistic similarities and differences of crossstatus communication and reveal the relationships between these linguistic similarities and differences and project outcomes. Method. We approach the above research objectives with the language style matching (LSM) tool which measures the similarities of cross-status communication in multiple language style features. For each sampled project, we first dynamically identify elite developers having project administration privileges. Then, we capture the cross-status communication between elite and non-elite developers; and calculate the LSM features of these two group of individuals. The LSM variables, together with project outcomes, will be used to fit regression models to analyze potential relationships between cross-status communication and project outcomes. Limitations. The study has several limitations. First, it considers project hosted on GITHUB only. Second, to ensure data availability, our sample is drawn from top projects, thus may not be able to represent all projects. Third, we only consider a limited number of linguistic variables.

show abstract

“…Software development often requires social interaction. So, previous studies have provided mechanisms to avoid and minimize merge conflicts, for instance, the communication among developers is efficient for avoiding merge conflicts [17].…”

Section: Avoiding Reducing Merge Conflictsmentioning

confidence: 99%

Merging problems in modern version control systems

Khleel

Nehéz

2020

MDT

View full text Add to dashboard Cite

During software development, when developers change the same part of the code concurrently, this may be led to merging conflicts. Resolving these conflicts might be costly and time-consuming. Three types of conflicts may arise during merge processes: textual, syntactic, and semantic. Textual conflicts occur when merging a concurrent operation, such as addition, removal or edition take place over the same parts of code. Syntactic conflicts occur when concurrent operations break the syntactic structure of the source code files when merged. Finally, a semantic conflict occurs when the merged modification is compiled without error but malfunctions. Version management systems usually use textual merging technique; users can synchronize their modifications with other users working in parallel with them, in this process, a merge is performed between local modifications and remote modifications. The previous work has examined different mechanisms to detect and resolve conflicts and proposed different tools for resolving merge conflicts, such as two-way merging, three-way merging, state-based merging, and operation-based merging. This paper discusses and investigates many concepts related to merging conflicts by asking and answering these questions; what are the factors that most affect in a merge conflict, how to avoiding and reducing merge conflicts, how to detecting merge conflicts, and how to resolve them.

show abstract

On the relation between Github communication activity and merge conflicts

Cited by 19 publications

References 40 publications

Analyzing Program Comprehensibility of Go Projects

Analyzing Program Comprehensibility of Go Projects

Cross-status Communication and Project Outcomesin OSS Development A Language Style Matching Perspective

Merging problems in modern version control systems

Contact Info

Product

Resources

About