How Are Paid and Volunteer Open Source Developers Different? A Study of the Rust Project

• URL: http://arxiv.org/abs/2401.13940v1
• Date: Thu, 25 Jan 2024 04:43:17 GMT
• Title: How Are Paid and Volunteer Open Source Developers Different? A Study of the Rust Project
• Authors: Yuxia Zhang, Mian Qin, Klaas-Jan Stol, Minghui Zhou, and Hui Liu
• Abstract summary: 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.
• Score: 11.298032569278686
• License: http://creativecommons.org/licenses/by/4.0/
• Abstract: It is now commonplace for organizations to pay developers to work on specific open source software (OSS) projects to pursue their business goals. Such paid developers work alongside voluntary contributors, but given the different motivations of these two groups of developers, conflict may arise, which may pose a threat to a project's sustainability. This paper presents an empirical study of paid developers and volunteers in Rust, a popular open source programming language project. Rust is a particularly interesting case given considerable concerns about corporate participation. We compare volunteers and paid developers through contribution characteristics and long-term participation, and solicit volunteers' perceptions on paid developers. 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; and being paid plays a positive role in becoming a long-term contributor. We also find that volunteers do have some prejudices against paid developers. This study suggests that the dichotomous view of paid vs. volunteer developers is too simplistic and that further subgroups can be identified. Companies should become more sensitive to how they engage with OSS communities, in certain ways as suggested by this study.

Related papers

• Empirical Analysis of Pull Requests for Google Summer of Code [0.0]
  The Google Summer of Code (GSoC) is a global initiative that matches students or new contributors with experienced mentors to work on open-source projects. This study presents an empirical analysis of pull requests created by interns during the GSoC program.
  arXiv  Detail & Related papers  (2024-12-17T17:42:43Z)
• Myth: The loss of core developers is a critical issue for OSS communities [1.392008330500134]
  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.
  arXiv  Detail & Related papers  (2024-11-30T01:47:59Z)
• Discovery of Timeline and Crowd Reaction of Software Vulnerability Disclosures [47.435076500269545]
  Apache Log4J was found to be vulnerable to remote code execution attacks. More than 35,000 packages were forced to update their Log4J libraries with the latest version. It is practically reasonable for software developers to update their third-party libraries whenever the software vendors have released a vulnerable-free version.
  arXiv  Detail & Related papers  (2024-11-12T01:55:51Z)
• OpenHands: An Open Platform for AI Software Developers as Generalist Agents [109.8507367518992]
  We introduce OpenHands, a platform for the development of AI agents that interact with the world in similar ways to a human developer. We describe how the platform allows for the implementation of new agents, safe interaction with sandboxed environments for code execution, and incorporation of evaluation benchmarks.
  arXiv  Detail & Related papers  (2024-07-23T17:50:43Z)
• Characterising Developer Sentiment in Software Components: An Exploratory Study of Gentoo [6.253919624802852]
  Collaborative software development happens in teams, that cooperate on shared artefacts, and discuss development on online platforms. Previous research has shown how communication between team members, especially in an open-source environment, can become extremely toxic. Our study shows that, in recent years, negative emotions have generally decreased in the communication between Gentoo developers.
  arXiv  Detail & Related papers  (2024-05-27T09:22:47Z)
• 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)
• 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)
• Rethinking People Analytics With Inverse Transparency by Design [57.67333075002697]
  We propose a new design approach for workforce analytics we refer to as inverse transparency by design. We find that architectural changes are made without inhibiting core functionality. We conclude that inverse transparency by design is a promising approach to realize accepted and responsible people analytics.
  arXiv  Detail & Related papers  (2023-05-16T21:37:35Z)
• "STILL AROUND": Experiences and Survival Strategies of Veteran Women Software Developers [53.5211430148752]
  We conducted 14 interviews to examine the experiences of people at the intersection of ageism and sexism. We identified 283 codes, which fell into three main categories: Strategies, Experiences, and Perception. Several strategies we identified, such as (Deliberately) Not Trying to Look Younger, were not previously described in the software engineering literature.
  arXiv  Detail & Related papers  (2023-02-07T19:26:15Z)
• ForestEyes Project: Conception, Enhancements, and Challenges [68.8204255655161]
  This work presents a Citizen Science project called ForestEyes. It uses volunteer's answers through the analysis and classification of remote sensing images to monitor deforestation regions in rainforests. To evaluate the quality of those answers, different campaigns/workflows were launched using remote sensing images from Brazilian Legal Amazon.
  arXiv  Detail & Related papers  (2022-08-24T17:48:12Z)
• 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.