Gender and tenure diversity in GitHub teams

B.N. Vasilescu, D. Posnett, B. Ray, M.G.J. Brand, van den, A. Serebrenik, P. Devanbu, V. Filkov

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    255 Citations (Scopus)
    3 Downloads (Pure)


    Software development is usually a collaborative venture. Open Source Software (OSS) projects are no exception; indeed, by design, the OSS approach can accommodate teams that are more open, geographically distributed, and dynamic than commercial teams. This, we find, leads to OSS teams that are quite diverse. Team diversity, predominantly in offline groups, is known to correlate with team output, mostly with positive effects. How about in OSS? Using GitHub, the largest publicly available collection of OSS projects, we studied how gender and tenure diversity relate to team productivity and turnover. Using regression modeling of GitHub data and the results of a survey, we show that both gender and tenure diversity are positive and significant predictors of productivity, together explaining a sizable fraction of the data variability. These results can inform decision making on all levels, leading to better outcomes in recruiting and performance.
    Original languageEnglish
    Title of host publication33rd Annual ACM Conference on Human Factors in Computing Systems (CHI'15, Seoul, Korea, April 18-23, 2015)
    Place of PublicationNew York NY
    PublisherAssociation for Computing Machinery, Inc
    ISBN (Print)978-1-4503-3145-6
    Publication statusPublished - 2015
    Event33rd Annual ACM Conference on Human Factors in Computing Systems, CHI 2015 - Seoul, Korea, Republic of
    Duration: 18 Apr 201523 Apr 2015
    Conference number: 33


    Conference33rd Annual ACM Conference on Human Factors in Computing Systems, CHI 2015
    Abbreviated titleCHI 2015
    Country/TerritoryKorea, Republic of
    Internet address


    Dive into the research topics of 'Gender and tenure diversity in GitHub teams'. Together they form a unique fingerprint.

    Cite this