Evaluating process quality in GNOME based on change request data

Schackmann, Holger; Lichter, Horst

doi:10.1109/msr.2009.5069485

Cited by 7 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several studies have focused on GNOME's bug database (Bugzilla), whose purpose have been: (1) predict the bug severity [40,42] (2) determine quality of bug reports [2,69], and (3) determine the efficiency of developers to address issues [44].…”

Section: Previous Studies Of Gnomementioning

confidence: 99%

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Poo-Caamaño

Knauss

Singer

et al. 2017

J Internet Serv Appl

View full text Add to dashboard Cite

Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects are coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers' interactions. Through a case study, we cataloged communication channels, determined the main channel from which we categorized high level communication and coordination activities spanning five releases, and triangulated our results by interviewing ten key developers. We found that a release schedule, influence (instead of direct control), and diversity are the main factors that positively impact the release process in the GNOME ecosystem. We report a set of lessons learned that encapsulates our understanding of how the Release Management process function in a FOSS ecosystem, we learned that: (1) ensure that the release team follows the main communication channels used by developers, (2) provide a common place for coordination for an ecosystem, (3) consider including both good technical and social skills in a release team, (4) aim for a diverse release team, (5) based on lack of power, lobbying and consensus based management must be followed, (6) help the release team in the coordination process with a well defined schedule, and (7) release team work is different from regular software work. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.

show abstract

Section: Previous Studies Of Gnomementioning

confidence: 99%

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Poo-Caamaño

Knauss

Singer

et al. 2017

J Internet Serv Appl

View full text Add to dashboard Cite

show abstract

“…Assigning developers to bug‐fixing activities is considered as a form of staffing. Schackman et al studied professional programmers with an average of 7 years' experience. The general finding that ‘there are order‐of‐magnitude differences among programmers’ has been confirmed by other studies such as and .…”

Section: Related Workmentioning

confidence: 99%

An empirical investigation of single‐objective and multiobjective evolutionary algorithms for developer's assignment to bugs

Karim

Ruhe

Rahman³

et al. 2016

J Software Evolu Process

View full text Add to dashboard Cite

In this paper, the modeling of developers' assignment to bugs (DAB) is studied. The problem is modeled both as a single objective (minimize bug fix time) and as a bi-objective (minimize bug fix time and cost) combinatorial optimization problem. Two models of developer assignment are considered where in the first model a single developer is assigned per bug (single developer model), while in the second model a single developer is assigned for each competency area of a bug (individual competency model). The latter model is proposed in this paper. For the single developer model, GA@DAB, an existing genetic algorithm-based approach, is extended to support precedence among bugs. For the individual competency model of DAB, one genetic algorithm-based approach (Competence@DAB) and one nondominated sorting genetic algorithm II-based approach (CompetenceMulti 2 @DAB ) are proposed to generate solutions minimizing time and minimizing both time and cost, respectively. The performance of the proposed approaches was evaluated for 2040 bugs of 19 open-source milestone projects from the ECLIPSE platform. Our results and analysis show that the proposed individual competency model is far better than the single developer model, with average bug fix time reduction of 39.7% across all projects.

show abstract

“…The body of recent empirical work on OSS is so varied and ample that it is difficult to summarize the main findings in clear and unequivocal terms: one way of understanding the current related literature is dividing it in studies "on OSS systems" [10], [11] and studies "with OSS systems" [12]. Specifically analysing the behavior of OSS developers, several works have highlighted the presence of core and additional developers, their level of engagement [13], the effects of territoriality [14], and even frameworks for comparing and contrasting the processes of different communities [15].…”

Section: Introductionmentioning

confidence: 99%

Developing an h-index for OSS developers

Capiluppi

Serebrenik

Youssef

2012

2012 9th IEEE Working Conference on Mining Software Repositories (MSR)

View full text Add to dashboard Cite

Abstract-The public data available in Open Source Software (OSS) repositories has been used for many practical reasons: detecting community structures; identifying key roles among developers; understanding software quality; predicting the arousal of bugs in large OSS systems, and so on; but also to formulate and validate new metrics and proof-of-concepts on general, non-OSS specific, software engineering aspects.One of the results that has not emerged yet from the analysis of OSS repositories is how to help the "career advancement" of developers: given the available data on products and processes used in OSS development, it should be possible to produce measurements to identify and describe a developer, that could be used externally as a measure of recognition and experience.This paper builds on top of the h-index, used in academic contexts, and which is used to determine the recognition of a researcher among her peers. By creating similar indices for OSS (or any) developers, this work could help defining a baseline for measuring and comparing the contributions of OSS developers in an objective, open and reproducible way.

show abstract

Evaluating process quality in GNOME based on change request data

Cited by 7 publications

References 7 publications

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

An empirical investigation of single‐objective and multiobjective evolutionary algorithms for developer's assignment to bugs

Developing an h-index for OSS developers

Contact Info

Product

Resources

About