DeepAI AI Chat
Log In Sign Up

Why Software Projects need Heroes (Lessons Learned from 1100+ Projects)

by   Suvodeep Majumder, et al.

A "hero" project is one where 80 the 20 since they might cause bottlenecks in development and communication. However, there is little empirical evidence on this matter. Further, recent studies show that such hero projects are very prevalent. Accordingly, this paper explores the effect of having heroes in project, from a code quality perspective. We identify the heroes developer communities in 1100+ open source GitHub projects. Based on the analysis, we find that (a) hero projects are majorly all projects; and (b) the commits from "hero developers" (who contribute most to the code) result in far fewer bugs than other developers. That is, contrary to the literature, heroes are standard and very useful part of modern open source projects.


page 5

page 7


Why We Engage in FLOSS: Answers from Core Developers

The maintenance and evolution of Free/Libre Open Source Software (FLOSS)...

We Don't Need Another Hero? The Impact of "Heroes" on Software Development

A software project has "Hero Developers" when 80 delivered by 20 heroes ...

From One to Hundreds: Multi-Licensing in the JavaScript Ecosystem

Open source licenses create a legal framework that plays a crucial role ...

Can instability variations warn developers when open-source projects boost?

Although architecture instability has been studied and measured using a ...

A Dataset of Enterprise-Driven Open Source Software

We present a dataset of open source software developed mainly by enterpr...

Open-Source Projects and their Collaborative Development Workflows

For teams using distributed version control systems, the right collabora...

Understanding Emotions of Developer Community Towards Software Documentation

The availability of open-source projects facilitates developers to contr...