Cited by 1,262Open Source Software InnovationsSoftware Engineering Techniques and PracticesKnowledge Management and Sharing

Motivation of software developers in Open Source projects: an Internet-based survey of contributors to the Linux kernel

Hertel, Guido, Niedner, Sven, Herrmann, Stefanie·2003·Research Policy

Integrity signals

Registry

Crossref · 10.1016/s0048-7333(03)00047-7

Cites

2 of 2 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Open source contributors are 98% male (Henkel and Tins, 2004) and 96% male (Hertel et al., 2003).

    “Henkel and Tins (2004) and Hertel et al , (2003) report, respectively, that open source contributors are 98% and 96% male.”

    From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Hertel et al , (2003)

  • Social psychology incentives and identification with the Linux community are poor predictors of how many hours members will work.

    “Similarly, Hertel et al. (2003) find that social psychology incentives and identification with the Linux community are poor predictors of how many hours members will work.”

    From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Hertel et al. (2003)

  • 43% of LINUX kernel developers sometimes or always receive salary for their work.

    “Ghosh et al (2002) report that 54% of respondents were paid for open source work; Lakhani and Wolf (2005) report that 55% of respondents contributed code during work hours; and Hertel et al (2003) report that 43% of LINUX kernel developers sometimes or always receive salary for their work.”

    From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Hertel et al (2003)

  • Developers assess both expected benefits and costs they must incur for their decisions of OSS code contributions.

    “According to this perspective, developers assess both expected benefits and costs they must incur for their decisions of OSS code contributions (Atkinson 1957, Hertel et al. 2003, Setia et al. 2012).”
  • These results are consistent with our argument that AI pair programmers could increase developer coding participation by increasing the expected benefits and reducing the expected costs developers face when deciding whether to contribute.

    “These results are consistent with our argument that AI pair programmers could increase developer coding participation by increasing the expected benefits and reducing the expected costs developers face when deciding whether to contribute (Atkinson 1957, Hertel et al. 2003, Setia et al. 2012, Wen et al. 2013).”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Hertel, G., Niedner, S., & Herrmann, S.
Affiliations
Christian-Albrechts-Universität zu Kiel (DE)
Corresponding author
Hertel, Guido
Venue
Research Policy
Publisher
Elsevier BV
Published
2003-07
Volume
32
Issue
7
Pages
1159-1177
ISSN
0048-7333 (ISSN-L)
OpenAlex
W2044679885
Cited by
1,262
References
2
Citations by year
2026: 20 · 2025: 16 · 2024: 12 · 2023: 23 · 2022: 20 · 2021: 37 · 2020: 33 · 2019: 42 · 2018: 58 · 2017: 37 · 2016: 75 · 2015: 67 · 2014: 85 · 2013: 77 · 2012: 81
FWCI
141.43
Type
journal article
Language
en
Open access
closed
Locations
  • Research Policy (publishedVersion)
  • RePEc: Research Papers in Economics (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Social Sciences › Communication › Knowledge Management and Sharing
Keywords
developer motivation, open source software, Linux kernel, open source contributors, software development teams, team goals, self-efficacy

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review