Heroes in FLOSS Projects: An Explorative Study

@article{Ricca2010HeroesIF,
  title={Heroes in FLOSS Projects: An Explorative Study},
  author={Filippo Ricca and Alessandro Marchetto},
  journal={2010 17th Working Conference on Reverse Engineering},
  year={2010},
  pages={155-159}
}
  • F. Ricca, A. Marchetto
  • Published 13 October 2010
  • Computer Science
  • 2010 17th Working Conference on Reverse Engineering
It is well recognized that the presence of Heroes, i.e., tireless developers who are the only ones who know certain critical parts of a system, can increase the risk of project failure, especially if these developers decide to leave the project. Instead, the relationship between Heroes and maintenance tasks is unknown because little investigated so far. In this paper, we first have implemented a tool to identify Heroes. Then, we have conducted an explorative study with 37 randomly selected open… 

Figures and Tables from this paper

Recommending People in Developers' Collaboration Network
TLDR
This work extracts information available from Source forge, the largest database of open source software, and builds developer collaboration network comprising of information on developers, projects, and project properties, and recommends a list of top developers that are most compatible based on their programming language skills.
On the Difficulty of Computing the Truck Factor
TLDR
The situation implementing the only approach proposed in literature able to compute the Truck Factor is explored, and an exploratory study with 37 open source projects is conducted for discovering limitations and drawbacks that could prevent its usage.
Modeling the Effects of Project Management Strategies on Long-Term Product Knowledge
. In a team, people sometimes leave the team and become replaced by new persons with less experience, and sometimes people par-ticipate in new activities and thereby obtain new knowledge. Different
Modeling the effects of project management strategies on long-term product knowledge
In a team, people sometimes leave the team and become replaced by new persons with less experience, and sometimes people participate in new activities and thereby obtain new knowledge. Different
Modeling the Effects of Project Management Strategies on Long-Term Product Knowledge
TLDR
An initial approach for how this type of knowledge can be modeled as a stochastic process is presented and how the model can be further elaborated and evaluated is discussed.
Systematic literature review : Risks in OSS adoption
  • Computer Science
  • 2014
TLDR
A systematic literature review on risks in OSS adoption contributes to the discovery of the initial requirements for a new risk analysis process with a preliminary screening of the techniques used for data gathering and for giving evidence to claims.
Evolving Software Systems
TLDR
Each chapter presents the state of the art in a particular topic, as well as the current research, available tool support and remaining challenges, covering a broad spectrum of software evolution topics.
Is my project's truck factor low?: theoretical and empirical considerations about the truck factor threshold
TLDR
This preliminary paper presents a theoretical model concerning the Truck Factor and investigates its use to define the maximum achievable Truck Factor value in a project, and conducts an experiment in which the proposed model is applied to real software projects with the aim of comparing it with the unique threshold proposed in literature.
Can Some Programming Languages Be Considered Harmful?
TLDR
This paper raises a number of questions concerning language safety and design sociotechnical experiments to answer them and suggests language designers use methods that are least harmful when making new libraries, protocols and domain-specific languages.
Developer social networks in software engineering: construction, analysis, and applications
TLDR
The state-of-the-art methods in the three steps of Developer Social Networks, namely construction, analysis, and applications are summarized and the relationships among them are investigated.

References

SHOWING 1-8 OF 8 REFERENCES
The influence of organizational structure on software quality
TLDR
This paper presents a metric scheme to quantify organizational complexity, in relation to the product development process to identify if the metrics impact failure-proneness, and provides empirical evidence that the organizational metrics are related to, and are effective predictors of failure- proneness.
How developers drive software evolution
TLDR
The mapping between the changes and the author identifiers (e.g., user names) provided by versioning repositories is used to define the ownership map visualization to understand when and how different developers interacted in which way and in which part of the system.
Extreme programming explained - embrace change
TLDR
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Do too many cooks spoil the broth? Using the number of developers to enhance defect prediction models
TLDR
It is concluded that while many factors can “spoil the broth” (lead to the release of software with too many defects), the number of developers is not a major influence.
Managing Code Ownership
TLDR
This article describes four code ownership models, ranging from one individual owning an entire system to the collective ownership that is a core extreme programming practice.
Can developer-module networks predict failures?
TLDR
Results of the experiments show that central modules are more failure-prone than modules located in surrounding areas of the network, and which centrality measures are significant to predict the probability and number of post-release failures.
Extreme Programming Explained
Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new