Myth: The loss of core developers is a critical issue for OSS communities

• URL: http://arxiv.org/abs/2412.00313v1
• Date: Sat, 30 Nov 2024 01:47:59 GMT
• Title: Myth: The loss of core developers is a critical issue for OSS communities
• Authors: Olivier Nourry, Masanari Kondo, Shinobu Saito, Yukako Iimura, Naoyasu Ubayashi, Yasutaka Kamei,
• Abstract summary: 89% of studied projects have experienced losing their core development team at least once. In 70% of cases, this project abandonment happens within the first three years of the project life. Most OSS projects rely on a single core developer to maintain development activities.
• Score: 1.392008330500134
• License:
• Abstract: Throughout their lifetime, open-source software systems will naturally attract new contributors and lose existing contributors. Not all OSS contributors are equal, however, as some contributors within a project possess significant knowledge and expertise of the codebase (i.e., core developers). When investigating the ability of projects to attract new contributors and how often a project loses contributors, it is therefore important to take into account the expertise of the contributors. Since core developers are vital to the longevity of projects, we therefore aim to find out: can OSS projects attract new core developers and how often do OSS projects lose core developers? To investigate core developer contribution patterns, we calculate the truck factor (or bus factor) of over 36,000 OSS projects to investigate how often TF developers join or abandon OSS projects. We find that 89% of our studied projects have experienced losing their core development team at least once. Our results also show that in 70% of cases, this project abandonment happens within the first three years of the project life. We also find that most OSS projects rely on a single core developer to maintain development activities. Finally, we find that only 27% of projects that were abandoned were able to attract at least one new TF developer. Our analysis shows that it is not uncommon for OSS projects to lose their initial core development team. This is likely due to most OSS project relying on a single core developer to maintain development activities. The first year of development is critical for OSS projects since this is where they are most at risk of losing their core developer(s). Additionally, projects that lose their core developer(s) early seem less likely to survive this event than projects that lost their core developers later on during their life.

Related papers

• Project Archetypes: A Blessing and a Curse for AI Development [3.2157163136267943]
  The development of applications using machine learning and artificial intelligence provides a context in which existing archetypes might outdate and need to be questioned, adapted, or replaced. We analyzed 36 interviews from 21 projects between IBM Watson and client companies and identified four project archetypes members initially used to understand the projects. We then derive a new project archetype, cognitive computing project, from the interviews. It can inform future development projects based on AI-development platforms.
  arXiv  Detail & Related papers  (2024-08-08T08:52:19Z)
• Leveraging Large Language Models for Efficient Failure Analysis in Game Development [47.618236610219554]
  This paper proposes a new approach to automatically identify which change in the code caused a test to fail. The method leverages Large Language Models (LLMs) to associate error messages with the corresponding code changes causing the failure. Our approach reaches an accuracy of 71% in our newly created dataset, which comprises issues reported by developers at EA over a period of one year.
  arXiv  Detail & Related papers  (2024-06-11T09:21:50Z)
• How Are Paid and Volunteer Open Source Developers Different? A Study of the Rust Project [11.298032569278686]
  This paper presents an empirical study of paid developers and volunteers in Rust, a popular open source programming language project. We find that core paid developers tend to contribute more frequently; commits contributed by one-time paid developers have bigger sizes; peripheral paid developers implement more features. We also find that volunteers do have some prejudices against paid developers.
  arXiv  Detail & Related papers  (2024-01-25T04:43:17Z)
• DevEval: Evaluating Code Generation in Practical Software Projects [52.16841274646796]
  We propose a new benchmark named DevEval, aligned with Developers' experiences in practical projects. DevEval is collected through a rigorous pipeline, containing 2,690 samples from 119 practical projects. We assess five popular LLMs on DevEval and reveal their actual abilities in code generation.
  arXiv  Detail & Related papers  (2024-01-12T06:51:30Z)
• Unveiling Diversity: Empowering OSS Project Leaders with Community Diversity and Turnover Dashboards [51.67585198094836]
  CommunityTapestry is a dynamic real-time community dashboard. It presents key diversity and turnover signals that we identified from the literature. It helped project leaders identify areas of improvement and gave them actionable information.
  arXiv  Detail & Related papers  (2023-12-13T22:12:57Z)
• Embedded Software Development with Digital Twins: Specific Requirements for Small and Medium-Sized Enterprises [55.57032418885258]
  Digital twins have the potential for cost-effective software development and maintenance strategies. We interviewed SMEs about their current development processes. First results show that real-time requirements prevent, to date, a Software-in-the-Loop development approach.
  arXiv  Detail & Related papers  (2023-09-17T08:56:36Z)
• How Early Participation Determines Long-Term Sustained Activity in GitHub Projects? [20.236570418427533]
  We aim to explore the relationship between early participation factors and long-term project sustainability. We leverage a novel methodology combining the Blumberg model of performance and machine learning to predict the sustainability of 290,255 GitHub projects. We quantitatively show that early participants have a positive effect on project's future sustained activity if they have prior experience in OSS project incubation.
  arXiv  Detail & Related papers  (2023-08-11T08:24:41Z)
• Trusting code in the wild: A social network-based centrality rating for developers in the Rust ecosystem [1.3581810800092387]
  This study builds a social network of 6,949 developers across the collaboration activity from 1,644 Rust packages. We evaluate if code coming from a developer with a higher centrality rating is likely to be accepted with lesser scrutiny by the downstream projects.
  arXiv  Detail & Related papers  (2023-05-31T23:24:03Z)
• An Exploratory Study on the Evidence of Hackathons' Role in Solving OSS Newcomers' Challenges [54.56931759953522]
  We aim to understand and discuss the challenges newcomers face when joining an OSS project. We collect evidence on how hackathons were used to address those challenges.
  arXiv  Detail & Related papers  (2023-05-16T15:40:19Z)
• One-off Events? An Empirical Study of Hackathon Code Creation and Reuse [69.98625403567553]
  We aim to understand the evolution of code used in and created during hackathon events. We collected information about 22,183 hackathon projects from DevPost.
  arXiv  Detail & Related papers  (2022-07-03T11:49:52Z)
• Leaving My Fingerprints: Motivations and Challenges of Contributing to OSS for Social Good [17.145094780239564]
  We conducted 21 semi-structured interviews with OSS for Social Good contributors. We find that the majority of contributors demonstrate a distinction between OSS4SG and OSS. OSS4SG contributors evaluate the owners of the project significantly more than OSS contributors.
  arXiv  Detail & Related papers  (2021-04-26T21:50:11Z)

This list is automatically generated from the titles and abstracts of the papers in this site.

This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.