Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How Does Contributors' Involvement Influence the Build Status of an Open-Source Software Project?

Gustavo Pinto
January 14, 2018
120

How Does Contributors' Involvement Influence the Build Status of an Open-Source Software Project?

Gustavo Pinto

January 14, 2018
Tweet

More Decks by Gustavo Pinto

Transcript

  1. Motivation (1/3) Casual contributors represent a large part of the

    OSS community (49%) and their contributions are far from trivial.
  2. They have little or no prior knowledge on the project

    domain Casual Contributors They might put more effort to create their first pull- request
  3. Methodology TravisTorrent TravisCI CI Build Data Commiter Data Dataset Dataset

    without duplicated users User Disambiguation Technique Data Cleaning Dataset with 1,074 curated projects Data Processing Data Statistical Tests
  4. Data Overview # Users 0 5000 10000 15000 20000 Builds

    1 2 3 4 5+ 0 150000 300000 450000 600000 Casual Non-Casual 1,074 projects 35,360 users 619,370 builds # Builds
  5. Results 0 250 500 750 1000 No difference Higher Casual

    Success Lower Casual Success Being a casual contributor is not a strong indicator for creating failing builds # Number of Projects
  6. 0 22.5 45 67.5 90 0 1.15 2.3 3.45 4.6

    Results Casual contributions are smaller, both in modified source-code lines and modified files Median of Modified LoC Median of Modified Files
  7. 0 1.15 2.3 3.45 4.6 No difference Higher Casual Success

    Lower Casual Success Results Projects in which casuals fail more than non-casuals run more jobs per build. Median of jobs per build