An exploratory study of the pull-based software development model

Gousios, Georgios; Pinzger, Martin; Deursen, Arie van

doi:10.1145/2568225.2568260

Cited by 507 publications

(536 citation statements)

References 30 publications

Supporting

Mentioning

521

Contrasting

Unclassified

Order By: Relevance

“…GitHub has tapped into the opportunity to facilitate pull-based development by offering workflow support tools, such as code reviewing systems and integrated issue trackers. Gousios et al reported the impacts of pullbased development based on mining repository data: fast development, transparency in project management, attracting contributions, crowd sourcing of code review, and democratizing development [3]. GitHub is also considered as a developers' social networking service, and it promotes software development through formal and informal collaboration, called social coding.…”

Section: Introductionmentioning

confidence: 99%

Investigating and Projecting Population Structures in Open Source Software Projects: A Case Study of Projects in GitHub

Onoue

Hata

Monden

et al. 2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYGitHub is a developers' social networking service that hosts a great number of open source software (OSS) projects. Although some of the hosted projects are growing and have many developers, most projects are organized by a few developers and face difficulties in terms of sustainability. OSS projects depend mainly on volunteer developers, and attracting and retaining these volunteers are major concerns of the project stakeholders. To investigate the population structures of OSS development communities in detail and conduct software analytics to obtain actionable information, we apply a demographic approach. Demography is the scientific study of population and seeks to identify the levels and trends in the size and components of a population. This paper presents a case study, investigating the characteristics of the population structures of OSS projects on GitHub, and shows population projections generated with the well-known cohort component method. We found that there are four types of population structures in OSS development communities in terms of experiences and contributions. In addition, we projected the future population accurately using a cohort component population projection method. This method predicts a population of the next period using a survival rate calculated from past population. To the best of our knowledge, this is the first study that applied demography to the field of OSS research. Our approach addressing OSS-related problems based on demography will bring new insights, since studying population is novel in OSS research. Understanding current and future structures of OSS projects can help practitioners to monitor a project, gain awareness of what is happening, manage risks, and evaluate past decisions.

show abstract

Section: Introductionmentioning

confidence: 99%

Investigating and Projecting Population Structures in Open Source Software Projects: A Case Study of Projects in GitHub

Onoue

Hata

Monden

et al. 2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…In addition, GitHub also provides various software project development data. Hence, the data of GitHub has been widely used in previous studies [26][27][28][29][30].…”

Section: Subject Projectsmentioning

confidence: 99%

Understanding Review Expertise of Developers: A Reviewer Recommendation Approach Based on Latent Dirichlet Allocation

Kim

Lee

2018

Symmetry

View full text Add to dashboard Cite

Abstract:The code reviewer assignment problem affects the reviewing time of a source code change. To effectively perform the code review process of a software project, the code reviewer assignment problem must be dealt with. Reviewer recommendation can reduce the time required for finding appropriate reviewers for a given source code change. In this paper, we propose a reviewer recommendation approach based on latent Dirichlet allocation (LDA). The proposed reviewer recommendation approach consists of a review expertise generation phase and a reviewer recommendation phase. The review expertise generation phase generates the review expertise of developers for topics of source code changes from the review history of a software project. The reviewer recommendation phase computes the review scores of the developers according to the topic distribution of a given source code change and the review expertise of the developers. In an empirical evaluation of five open source projects, we confirm that the proposed reviewer recommendation approach obtains better average top-10 accuracy than existing reviewer recommendation approaches.

show abstract

“…Previous studies have also excluded a number of OSS projects after their initial sampling. Samoladas et al (2010) and Gousios and Pinzger (2014) applied certain selection criteria to exclude projects from their initial selection. Midha and Palvia (2012) based on certain project selection criteria, reduced their initial sample from 887 to 283.…”

Section: Storage Of Projects Metadata and Revisionsmentioning

confidence: 99%

An empirical study on the interplay between semantic coupling and co-change of software classes

2017

View full text Add to dashboard Cite

Software systems continuously evolve to accommodate new features and interoperability relationships between artifacts point to increasingly relevant software change impacts. During maintenance, developers must ensure that related entities are updated to be consistent with these changes. Studies in the static change impact analysis domain have identified that a combination of source code and lexical information outperforms using each one when adopted independently. However, the extraction of lexical information and the measure of how loosely or closely related two software artifacts are, considering the semantic information embedded in their comments and identifiers has been carried out using somewhat complex information retrieval (IR) techniques. The interplay between software semantic and change relationship strengths has also not been extensively studied. This work aims to fill both gaps by comparing the effectiveness of measuring semantic coupling of OO software classes using (i) simple identifier based techniques and (ii) the word corpora of the entire classes in a software system. Afterwards, we empirically investigate the interplay between semantic and change coupling. The empirical results show that: (1) identifier based methods have more computational efficiency but cannot always be used interchangeably with corpora-based methods of computing semantic coupling of classes and (2) there is no correlation between semantic and change coupling. Furthermore we found that (3) there is a directional relationship between the two, as over 70% of the semantic dependencies are also linked by change coupling but not vice versa.

show abstract

An exploratory study of the pull-based software development model

Cited by 507 publications

References 30 publications

Investigating and Projecting Population Structures in Open Source Software Projects: A Case Study of Projects in GitHub

Investigating and Projecting Population Structures in Open Source Software Projects: A Case Study of Projects in GitHub

Understanding Review Expertise of Developers: A Reviewer Recommendation Approach Based on Latent Dirichlet Allocation

An empirical study on the interplay between semantic coupling and co-change of software classes

Contact Info

Product

Resources

About