Will you come back to contribute? Investigating the inactivity of OSS core developers in GitHub

• DOI: 10.1007/s10664-021-10012-6
• Publication Date: 2022-03-19T08:19:42Z
• Authors: Fabio Calefato; Marco Aurélio Gerosa; Giuseppe Iaffaldano; Filippo Lanubile; Igor Steinmacher
• Keywords: Disengagement theory; Abandonment (legal); Code refactoring

Several Open Source Software (OSS) projects depend on the continuity of their development communities to remain sustainable. Understanding how developers become inactive or why they take breaks can help prevent abandonment and incentivize come back. In this paper, we propose a novel method identify developers' periods by analyzing individual rhythm contributions projects. Using method, quantitatively analyze inactivity core in 18 OSS organizations hosted GitHub. We also survey receive feedback about identified transitions. Our results show that our was effective for identifying breaks. About 94% surveyed agreed with state model inactivity; 71% 79% them acknowledged transition, respectively. all (at least once) half (~45%}) have completely disengaged from project at one year. analyzed probability transitions to/from found who pause activity ~35-55\% chance return an active state; yet, if break lasts year longer, then resuming activities drops ~21-26%, ~54% complete disengagement. These may support creation policies mechanisms make community managers aware potential abandonment.