2018
DOI: 10.1016/j.infsof.2018.03.010
|View full text |Cite
|
Sign up to set email alerts
|

Surgical teams on GitHub: Modeling performance of GitHub project development processes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

3
16
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
10

Relationship

0
10

Authors

Journals

citations
Cited by 34 publications
(28 citation statements)
references
References 26 publications
3
16
0
Order By: Relevance
“…In the three-way interaction with coordinative complexity, the negative effect of knowledge loss was reversed as complexity increased. This suggests that although some abandoned code persisted in the project, the code was continually modified by a steady stream of newcomers and, in line with recent research on OSS teams (Jarczyk, Jaroszewicz, Wierzbicki, Pawlak, & Jankowski-Lorek, 2018), a small group of developers managed the task interdependencies introduced by newcomers in the project. We observed a similar effect with respect to the three-way interaction including component complexity.…”
Section: Resultsmentioning
confidence: 58%
“…In the three-way interaction with coordinative complexity, the negative effect of knowledge loss was reversed as complexity increased. This suggests that although some abandoned code persisted in the project, the code was continually modified by a steady stream of newcomers and, in line with recent research on OSS teams (Jarczyk, Jaroszewicz, Wierzbicki, Pawlak, & Jankowski-Lorek, 2018), a small group of developers managed the task interdependencies introduced by newcomers in the project. We observed a similar effect with respect to the three-way interaction including component complexity.…”
Section: Resultsmentioning
confidence: 58%
“…[5] 1700 22,000 0.07 [26] 1255 58,092 0.02 [27] 1070 1600 0.66 [25] 62,607 9447 0.15 [30] 62,607 9447 0.15 Our study 100 41,280 0.002…”
Section: Paper Id Number Of User Number Of Project Ratio (~)mentioning
confidence: 76%
“…Some of the studies in this category focus on taking as the main information the commitments to follow up on issues that may occur in the project or with the developers, and that represent a challenge when executing software maintenance. Thus, the study 115 (Jarczyk et al, 2017), the closing of issues (errors and characteristics) is studied using it as main information for the analysis (commits) in software projects, which allows a better understanding of the factors that affect the completion rates of issues in software projects.…”
Section: Rq1 What Kind Of Information Is Taken As Input For the Analy...mentioning
confidence: 99%