![]() Therefore, it is critical to nurture the project workforce and avoid losing core developers and their knowledge. ( 2019) showed that 59% of the analyzed projects did not survive after the departure of Truck Factor developers (Williams and Kessler 2002), i.e., developers who hold unique responsibilities in the project. 2015), especially when core contributors are involved. Turnovers often disrupt the community, reduce productivity (Mockus 2010), and degrade product quality (Schilling 2014 Foucault et al. Almost half of the OSS projects that fail do so because of a problem related to the development team (Coelho and Valente 2017). Jabref 2 pdf for one record code#( 2018) reported that, from the perspective of OSS developers, maintainers, and managers, the loss of contributors is a major problem in OSS communities and ecosystems, followed by poor code quality. The success of an OSS project depends on the strength and health of the group behind it (Crowston and Howison 2006 Link and Germonprez 2018 Coelho and Valente 2017). These results may support the creation of policies and mechanisms to make OSS community managers aware of breaks and potential project abandonment. We also analyzed the probability of transitions to/from inactivity and found that developers who pause their activity have a ~35 to ~55% chance to return to an active state yet, if the break lasts for a year or longer, then the probability of resuming activities drops to ~21–26%, with a ~54% chance of complete disengagement. We also show that all core developers take breaks (at least once) and about a half of them (~45%) have completely disengaged from a project for at least one year. About 94% of the surveyed core developers agreed with our state model of inactivity 71% and 79% of them acknowledged their breaks and state transition, respectively. Our results show that our method was effective for identifying developers’ breaks. We also survey core developers to receive their feedback about the identified breaks and transitions. Using this method, we quantitatively analyze the inactivity of core developers in 18 OSS organizations hosted on GitHub. In this paper, we propose a novel method to identify developers’ inactive periods by analyzing the individual rhythm of contributions to the projects. Understanding how developers become inactive or why they take breaks can help communities prevent abandonment and incentivize developers to come back. Jabref 2 pdf for one record software#Several Open-Source Software (OSS) projects depend on the continuity of their development communities to remain sustainable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |