adaptation-slr/SLR_references_total/both_waves_references/t2-acm-3.bib

@inproceedings{10.1145/1508865.1508977,
author = {Morelli, Ralph and de Lanerolle, Trishan},
title = {Foss 101: engaging introductory students in the open source movement},
year = {2009},
isbn = {9781605581835},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1508865.1508977},
doi = {10.1145/1508865.1508977},
abstract = {Can engaging students in free and open source software(FOSS) pique their interest in computer science? This paper describes an introductory computer science course that introduced students to using FOSS, to contributing to a humanitarian FOSS project, and to studying the broader impact of FOSS on our society. Students learned basic webprogramming skills (PHP/MySQL) and made small but significant contributions to a global FOSS project. Mistakes were made and opportunities were missed. But overall theexperiment was a success and the experience was enjoyable and educational for students and instructor alike. By building on what worked well, this course could serve as a model for incorporating study of FOSS into the introductory computing curriculum.},
booktitle = {Proceedings of the 40th ACM Technical Symposium on Computer Science Education},
pages = {311–315},
numpages = {5},
keywords = {open source software, open source movement, curriculum development},
location = {Chattanooga, TN, USA},
series = {SIGCSE '09}
}

@article{10.1145/1539024.1508977,
author = {Morelli, Ralph and de Lanerolle, Trishan},
title = {Foss 101: engaging introductory students in the open source movement},
year = {2009},
issue_date = {March 2009},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
volume = {41},
number = {1},
issn = {0097-8418},
url = {https://doi.org/10.1145/1539024.1508977},
doi = {10.1145/1539024.1508977},
abstract = {Can engaging students in free and open source software(FOSS) pique their interest in computer science? This paper describes an introductory computer science course that introduced students to using FOSS, to contributing to a humanitarian FOSS project, and to studying the broader impact of FOSS on our society. Students learned basic webprogramming skills (PHP/MySQL) and made small but significant contributions to a global FOSS project. Mistakes were made and opportunities were missed. But overall theexperiment was a success and the experience was enjoyable and educational for students and instructor alike. By building on what worked well, this course could serve as a model for incorporating study of FOSS into the introductory computing curriculum.},
journal = {SIGCSE Bull.},
month = mar,
pages = {311–315},
numpages = {5},
keywords = {open source software, open source movement, curriculum development}
}

@inproceedings{10.1145/1833272.1833275,
author = {Capiluppi, Andrea and Baravalle, Andres and Heap, Nick W.},
title = {From "community" to "commercial" FLOSS: the case of Moodle},
year = {2010},
isbn = {9781605589787},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1833272.1833275},
doi = {10.1145/1833272.1833275},
abstract = {This paper documents the evolution of Moodle, an advanced Content Management System, and its transition from a purely volunteer-based project to one driven by commercial interests and stakeholders. The study of its evolution provides evidence of the sustainability of its process: increasing amounts of provided effort by developers correspond to similarly increasing produced outputs to the Moodle system. It is also evident how this OSS system, apart from achieving the transition to a successful multisite, collaborative and community-based OSS project, depends more on its community than its commercial partners.},
booktitle = {Proceedings of the 3rd International Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development},
pages = {11–16},
numpages = {6},
location = {Cape Town, South Africa},
series = {FLOSS '10}
}

@inproceedings{10.1145/3510458.3513020,
author = {Guizani, Mariam and Zimmermann, Thomas and Sarma, Anita and Ford, Denae},
title = {Attracting and retaining OSS contributors with a maintainer dashboard},
year = {2022},
isbn = {9781450392273},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3510458.3513020},
doi = {10.1145/3510458.3513020},
abstract = {Tools and artifacts produced by open source software (OSS) have been woven into the foundation of the technology industry. To keep this foundation intact, the open source community needs to actively invest in sustainable approaches to bring in new contributors and nurture existing ones. We take a first step at this by collaboratively designing a maintainer dashboard that provides recommendations on how to attract and retain open source contributors. For example, by highlighting project goals (e.g., a social good cause) to attract diverse contributors and mechanisms to acknowledge (e.g., a "rising contributor" badge) existing contributors. Next, we conduct a project-specific evaluation with maintainers to better understand use cases in which this tool will be most helpful at supporting their plans for growth. From analyzing feedback, we find recommendations to be useful at signaling projects as welcoming and providing gentle nudges for maintainers to proactively recognize emerging contributors. However, there are complexities to consider when designing recommendations such as the project current development state (e.g., deadlines, milestones, refactoring) and governance model. Finally, we distill our findings to share what the future of recommendations in open source looks like and how to make these recommendations most meaningful over time.Open Source Software (OSS) plays an important role in the development and maintenance of software products that are widely deployed in different domains from computer science to astrophysics and cutting edge medicines research. Chances are there is an open source project for anyone to contribute to. With the recent deployment of the popular Linux open source project on Mars even the sky is no limit. However, OSS projects largely depend on volunteers and attracting, retaining, and keeping contributors engaged is a severe challenge. In this paper, we present the design and evaluation of a dashboard to support community managers, such as maintainers, to track and acknowledge newcomers' contributions. With the support of tools such as ours, maintainers will be better prepared to attract and retain their emerging community.},
booktitle = {Proceedings of the 2022 ACM/IEEE 44th International Conference on Software Engineering: Software Engineering in Society},
pages = {36–40},
numpages = {5},
keywords = {social good, open source, maintainers},
location = {Pittsburgh, Pennsylvania},
series = {ICSE-SEIS '22}
}

@inproceedings{10.1109/ICSE-NIER58687.2023.00010,
author = {Sajadi, Amirali and Damevski, Kostadin and Chatterjee, Preetha},
title = {Interpersonal Trust in OSS: Exploring Dimensions of Trust in GitHub Pull Requests},
year = {2023},
isbn = {9798350300390},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/ICSE-NIER58687.2023.00010},
doi = {10.1109/ICSE-NIER58687.2023.00010},
abstract = {Interpersonal trust plays a crucial role in facilitating collaborative tasks, such as software development. While previous research recognizes the significance of trust in an organizational setting, there is a lack of understanding in how trust is exhibited in OSS distributed teams, where there is an absence of direct, in-person communications. To foster trust and collaboration in OSS teams, we need to understand what trust is and how it is exhibited in written developer communications (e.g., pull requests, chats). In this paper, we first investigate various dimensions of trust to identify the ways trusting behavior can be observed in OSS. Next, we sample a set of 100 GitHub pull requests from Apache Software Foundation (ASF) projects, to analyze and demonstrate how each dimension of trust can be exhibited. Our findings provide preliminary insights into cues that might be helpful to automatically assess team dynamics and establish interpersonal trust in OSS teams, leading to successful and sustainable OSS.},
booktitle = {Proceedings of the 45th International Conference on Software Engineering: New Ideas and Emerging Results},
pages = {19–24},
numpages = {6},
keywords = {pull requests, open source software, trust},
location = {Melbourne, Australia},
series = {ICSE-NIER '23}
}

@inproceedings{10.1145/3611643.3616250,
author = {Fang, Zihan and Endres, Madeline and Zimmermann, Thomas and Ford, Denae and Weimer, Westley and Leach, Kevin and Huang, Yu},
title = {A Four-Year Study of Student Contributions to OSS vs. OSS4SG with a Lightweight Intervention},
year = {2023},
isbn = {9798400703270},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3611643.3616250},
doi = {10.1145/3611643.3616250},
abstract = {Modern software engineering practice and training increasingly rely on Open Source Software (OSS). The recent growth in demand for professional software engineers has led to increased contributions to, and usage of, OSS. However, there is limited understanding of the factors affecting how developers, and how new or student developers in particular, decide which OSS projects to contribute to, a process critical to OSS sustainability, access, adoption, and growth. To better understand OSS contributions from the developers of tomorrow, we conducted a four-year study with 1,361 students investigating the life cycle of their contributions (from project selection to pull request acceptance). During the study, we also delivered a lightweight intervention to promote the awareness of open source projects for social good (OSS4SG), OSS projects that have positive impacts in other domains. Using both quantitative and qualitative methods, we analyze student experience reports and the pull requests they submit. Compared to general OSS projects, we find significant differences in project selection (𝑝 < 0.0001, effect size = 0.84), student motivation (𝑝 < 0.01, effect size = 0.13), and increased pull-request acceptance rates for OSS4SG contributions. We also find that our intervention correlates with increased student contributions to OSS4SG (𝑝 < 0.0001, effect size = 0.38). Finally, we analyze correlations of factors such as gender or working with a partner. Our findings may help improve the experience for new developers participating in OSS4SG and the quality of their contributions. We also hope our work helps educators, project leaders, and contributors to build a mutually-beneficial framework for the future growth of OSS4SG.},
booktitle = {Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering},
pages = {3–15},
numpages = {13},
keywords = {CS Education, Open Source Software, Social Good},
location = {San Francisco, CA, USA},
series = {ESEC/FSE 2023}
}

@inproceedings{10.1109/HICSS.2012.644,
author = {Schilling, Andreas and Laumer, Sven and Weitzel, Tim},
title = {Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects},
year = {2012},
isbn = {9780769545257},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2012.644},
doi = {10.1109/HICSS.2012.644},
abstract = {Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals' subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.},
booktitle = {Proceedings of the 2012 45th Hawaii International Conference on System Sciences},
pages = {3446–3455},
numpages = {10},
keywords = {Team staffing, Recruiting, Open source software development, Open source, Open Source Software, OSS/FLOSS, IS personnel, Developer Retention},
series = {HICSS '12}
}

@inproceedings{10.1145/2214091.2214119,
author = {Schilling, Andreas},
title = {Links to the source - a multidimensional view of social ties for the retention of FLOSS developers},
year = {2012},
isbn = {9781450311106},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2214091.2214119},
doi = {10.1145/2214091.2214119},
abstract = {Free Libre Open Source Software (FLOSS) is of vital importance for the daily life of many private and corporate users. However, the majority of all FLOSS initiatives fail, most commonly due to a lack of sustained developers. In contrast to previous research which used an individual centric or a structural perspective, this dissertation combines motivational and relational aspects to build a comprehensive understanding for FLOSS developers' ongoing project commitment. A unified research model is developed by drawing on established theories from organizational and sociological literature, in particular by combining Self-Determination-Theory (SDT) and Social-Identity-Theory (SIT). Both SDT and SIT have been found valuable concepts for staffing decisions in organizations. In addition to the development and evaluation of the research model, this dissertation derives operational strategies for project managers of FLOSS initiatives on how to enhance the retention behavior of their contributor base.},
booktitle = {Proceedings of the 50th Annual Conference on Computers and People Research},
pages = {103–108},
numpages = {6},
keywords = {turnover intention, social-identity-theory, self-determination-theory, retention, open source, job satisfaction, it personnel},
location = {Milwaukee, Wisconsin, USA},
series = {SIGMIS-CPR '12}
}

@inproceedings{10.1109/CHASE.2015.9,
author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Matsumoto, Kenichi},
title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study},
year = {2015},
isbn = {9781467370318},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/CHASE.2015.9},
doi = {10.1109/CHASE.2015.9},
abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in Git Hub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
booktitle = {Proceedings of the 2015 IEEE/ACM 8th International Workshop on Cooperative and Human Aspects of Software Engineering},
pages = {15–21},
numpages = {7},
keywords = {Population Pyramids, OSS, Game Theory},
series = {CHASE '15}
}

@inproceedings{10.1145/3463274.3463326,
author = {Sharma, Pankajeshwara and Savarimuthu, Tony and Stanger, Nigel},
title = {Influence of Roles in Decision-Making during OSS Development — A Study of Python},
year = {2021},
isbn = {9781450390538},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3463274.3463326},
doi = {10.1145/3463274.3463326},
abstract = {Governance has been highlighted as a key factor in the success of an Open Source Software (OSS) project. It is generally seen that in a mixed meritocracy and autocracy governance model, the decision-making (DM) responsibility regarding what features are included in the OSS is shared among members from select roles; prominently the project leader. However, less examination has been made whether members from these roles are also prominent in DM discussions and how decisions are made, to show they play an integral role in the success of the project. We believe that to establish their influence, it is necessary to examine not only discussions of proposals in which the project leader makes the decisions, but also those where others make the decisions. Therefore, in this study, we examine the prominence of members performing different roles in: (i) making decisions, (ii) performing certain social roles in DM discussions (e.g., discussion starters), (iii) contributing to the OSS development social network through DM discussions, and (iv) how decisions are made under both scenarios. We examine these aspects in the evolution of the well-known Python project. We carried out a data-driven longitudinal study of their email communication spanning 20 years, comprising about 1.5 million emails. These emails contain decisions for 466 Python Enhancement Proposals (PEPs) that document the language’s evolution. Our findings make the influence of different roles transparent to future (new) members, other stakeholders, and more broadly, to the OSS research community.},
booktitle = {Proceedings of the 25th International Conference on Evaluation and Assessment in Software Engineering},
pages = {50–59},
numpages = {10},
keywords = {social network analysis, roles, rationale, onion model, influence, decision-making, Python, PEP, Open Source Software (OSS)},
location = {Trondheim, Norway},
series = {EASE '21}
}

@inproceedings{10.5555/2819321.2819325,
author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Matsumoto, Kenichi},
title = {Characteristics of sustainable OSS projects: a theoretical and empirical study},
year = {2015},
publisher = {IEEE Press},
abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering},
pages = {15–21},
numpages = {7},
location = {Florence, Italy},
series = {CHASE '15}
}

@inproceedings{10.1145/3233391.3233531,
author = {Johri, Aditya and Teo, Hon Jie},
title = {Achieving Equilibrium through Coworking: Work-Life Balance in FLOSS through Multiple Spaces and Media Use},
year = {2018},
isbn = {9781450359368},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3233391.3233531},
doi = {10.1145/3233391.3233531},
abstract = {Participants in FLOSS (Free/Libre Open Source Software) projects are atypical in their collaborative practices given the high demand for virtual work. Through a study of workers from two organizations working on FLOSS projects we identify the boundaries, in terms of productivity and quality of life, of virtual work and actions workers take in order to find a work-life balance. We found that although workers valued the flexibility of working from home, they had difficulty focusing on their work for sustained time periods and often felt isolated. This motivated them to use coworking spaces - physical spaces used as work space by workers not on the same team or even the same firm - as a critical part of their space ecology. In conjunction with their media ecology - a mix of communication technologies including IRC - the space/media mix allowed them to balance their work and personal lives. We draw implications for better supporting FLOSS and virtual work practices through design of media/space and work practices.},
booktitle = {Proceedings of the 14th International Symposium on Open Collaboration},
articleno = {7},
numpages = {11},
keywords = {Work-Life balance, Virtual work, Media-Space Mix, FLOSS teams, Coworking spaces},
location = {Paris, France},
series = {OpenSym '18}
}

@inproceedings{10.1109/SoHeal.2019.00009,
author = {Iaffaldano, Giuseppe and Steinmacher, Igor and Calefato, Fabio and Gerosa, Marco and Lanubile, Filippo},
title = {Why do developers take breaks from contributing to OSS projects? a preliminary analysis},
year = {2019},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/SoHeal.2019.00009},
doi = {10.1109/SoHeal.2019.00009},
abstract = {Creating a successful and sustainable Open Source Software (OSS) project often depends on the strength and the health of the community behind it. Current literature explains the contributors' lifecycle, starting with the motivations that drive people to contribute and barriers to joining OSS projects, covering developers' evolution until they become core members. However, the stages when developers leave the projects are still weakly explored and are not well-defined in existing developers' lifecycle models. In this position paper, we enrich the knowledge about the leaving stage by identifying sleeping and dead states, representing temporary and permanent brakes that developers take from contributing. We conducted a preliminary set of semi-structured interviews with active developers. We analyzed the answers by focusing on defining and understanding the reasons for the transitions to/from sleeping and dead states. This paper raises new questions that may guide further discussions and research, which may ultimately benefit OSS communities.},
booktitle = {Proceedings of the 2nd International Workshop on Software Health},
pages = {9–16},
numpages = {8},
keywords = {project abandonment, open source, developers turnover, communities},
location = {Montreal, Quebec, Canada},
series = {SoHeal '19}
}

@inproceedings{10.1145/2957792.2957809,
author = {Vaseva, Lyudmila},
title = {Out of Altruism or Because it Reads Well on the CV? The Motivations for Participation in the Freifunk Community Compared to FLOSS},
year = {2016},
isbn = {9781450344517},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2957792.2957809},
doi = {10.1145/2957792.2957809},
abstract = {Motivation of free, libre and open source software developers has been widely studied over the years. The reasons people engage in this seemingly altruistic behavior have been elaborated and classified. The present work addresses a slightly different issue: what motivates individuals to participate in community network projects? Are the reasons similar to or quite distinct from these relevant to contributors to free software? Based on recently conducted interviews with community network activists from the Germany based project Freifunk and established FLOSS motivation research, we will analyse the specifics of the Freifunk project and the factors which spur its members to action. The obtained insights could then hopefully be used to understand the underlying group processes and help build sustainable communities.},
booktitle = {Proceedings of the 12th International Symposium on Open Collaboration},
articleno = {5},
numpages = {4},
keywords = {motivation, freifunk, floss, community networks},
location = {Berlin, Germany},
series = {OpenSym '16}
}

@inproceedings{10.1145/2491055.2491085,
author = {Azarbakht, Amir},
title = {Drawing the big picture: analyzing FLOSS collaboration with temporal social network analysis},
year = {2013},
isbn = {9781450318525},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2491055.2491085},
doi = {10.1145/2491055.2491085},
abstract = {How can we understand FOSS collaboration better? Can social issues that emerge be identified and addressed before it is too late? Can the community heal itself, become more transparent and inclusive, and promote diversity? We propose a technique to address these issues by quantitative analysis of social dynamics in FOSS communities. We propose using social network analysis metrics to identify growth patterns and unhealthy dynamics; giving the community a heads-up when they can still take action to ensure the sustainability of the project.},
booktitle = {Proceedings of the 9th International Symposium on Open Collaboration},
articleno = {30},
numpages = {1},
keywords = {temporal analysis, social network analysis, social dynamics, reliability, measurement, human factors, free/open source software, forking, FLOSS},
location = {Hong Kong, China},
series = {WikiSym '13}
}

@inproceedings{10.1145/2652524.2652544,
author = {Bosu, Amiangshu and Carver, Jeffrey C.},
title = {Impact of developer reputation on code review outcomes in OSS projects: an empirical investigation},
year = {2014},
isbn = {9781450327749},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2652524.2652544},
doi = {10.1145/2652524.2652544},
abstract = {<u>Context:</u> Gaining an identity and building a good reputation are important motivations for Open Source Software (OSS) developers. It is unclear whether these motivations have any actual impact on OSS project success. <u>Goal:</u> To identify how an OSS developer's reputation affects the outcome of his/her code review requests. <u>Method:</u> We conducted a social network analysis (SNA) of the code review data from eight popular OSS projects. Working on the assumption that core developers have better reputation than peripheral developers, we developed an approach, Core Identification using K-means (CIK) to divide the OSS developers into core and periphery groups based on six SNA centrality measures. We then compared the outcome of the code review process for members of the two groups. <u>Results:</u> The results suggest that the core developers receive quicker first feedback on their review request, complete the review process in shorter time, and are more likely to have their code changes accepted into the project codebase. Peripheral developers may have to wait 2 - 19 times (or 12 - 96 hours) longer than core developers for the review process of their code to complete. <u>Conclusion:</u> We recommend that projects allocate resources or create tool support to triage the code review requests to motivate prospective developers through quick feedback.},
booktitle = {Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement},
articleno = {33},
numpages = {10},
keywords = {social network analysis, peer impression, open source, network structure, code review},
location = {Torino, Italy},
series = {ESEM '14}
}

@inproceedings{10.1109/ICSM.2013.45,
author = {Gharehyazie, Mohammad and Posnett, Daryl and Filkov, Vladimir},
title = {Social Activities Rival Patch Submission for Prediction of Developer Initiation in OSS Projects},
year = {2013},
isbn = {9780769549811},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/ICSM.2013.45},
doi = {10.1109/ICSM.2013.45},
abstract = {Maintaining a productive and collaborative team of developers is essential to Open Source Software (OSS) success, and hinges upon the trust inherent among the team. Whether a project participant is initiated as a developer is a function of both his technical contributions and also his social interactions with other project participants. One\^{a}€™s online social footprint is arguably easier to ascertain and gather than one\^{a}€™s technical contributions e.g., gathering patch submission information requires mining multiple sources with different formats, and then merging the aliases from these sources. In contrast to prior work, where patch submission was found to be an essential ingredient to achieving developer status, here we investigate the extent to which the likelihood of achieving that status can be modeled solely as a social network phenomenon. For 6 different OSS projects we compile and integrate a set of social measures of the communications network among OSS project participants and a set of technical measures, i.e. OSS developers patch submission activities. We use these sets to predict whether a project participant will become a developer. We find that the social network metrics, in particular the amount of two-way communication a person participates in, are more significant predictors of one\^{a}€™s likelihood to becoming a developer. Further, we find that this is true to the extent that other predictors, e.g. patch submission info, need not be included in the models. In addition, we show that future developers are easy to identify with great fidelity when using the first three months of data of their social activities. Moreover, only the first month of their social links are a very useful predictor, coming within 10\% of the three month data\^{a}€™s predictions. Finally, we find that it is easier to become a developer earlier in the projects lifecycle than it is later as the project matures. These results should provide insight on the social nature of gaining trust and advancing in status in distributed projects.},
booktitle = {Proceedings of the 2013 IEEE International Conference on Software Maintenance},
pages = {340–349},
numpages = {10},
series = {ICSM '13}
}

@inproceedings{10.1109/ICSE43902.2021.00096,
author = {Huang, Yu and Ford, Denae and Zimmermann, Thomas},
title = {Leaving My Fingerprints: Motivations and Challenges of Contributing to OSS for Social Good},
year = {2021},
isbn = {9781450390859},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/ICSE43902.2021.00096},
doi = {10.1109/ICSE43902.2021.00096},
abstract = {When inspiring software developers to contribute to open source software, the act is often referenced as an opportunity to build tools to support the developer community. However, that is not the only charge that propels contributions--- growing interest in open source has also been attributed to software developers deciding to use their technical skills to benefit a common societal good. To understand how developers identify these projects, their motivations for contributing, and challenges they face, we conducted 21 semi-structured interviews with OSS for Social Good (OSS4SG) contributors. From our interview analysis, we identified themes of contribution styles that we wanted to understand at scale by deploying a survey to over 5765 OSS and Open Source Software for Social Good contributors. From our quantitative analysis of 517 responses, we find that the majority of contributors demonstrate a distinction between OSS4SG and OSS. Likewise, contributors described definitions based on what societal issue the project was to mitigate and who the outcomes of the project were going to benefit. In addition, we find that OSS4SG contributors focus less on benefiting themselves by padding their resume with new technology skills and are more interested in leaving their mark on society at statistically significant levels. We also find that OSS4SG contributors evaluate the owners of the project significantly more than OSS contributors. These findings inform implications to help contributors identify high societal impact projects, help project maintainers reduce barriers to entry, and help organizations understand why contributors are drawn to these projects to sustain active participation.},
booktitle = {Proceedings of the 43rd International Conference on Software Engineering},
pages = {1020–1032},
numpages = {13},
location = {Madrid, Spain},
series = {ICSE '21}
}

@inproceedings{10.5555/2337223.2337284,
author = {Zhou, Minghui and Mockus, Audris},
title = {What make long term contributors: willingness and opportunity in OSS community},
year = {2012},
isbn = {9781467310673},
publisher = {IEEE Press},
abstract = {To survive and succeed, software projects need to attract and retain contributors. We model the individual's chances to become a valuable contributor through their capacity, willingness, and the opportunity to contribute at the time of joining. Using issue tracking data of Mozilla and Gnome, we find that the probability for a new joiner to become a Long Term Contributor (LTC) is associated with her willingness and environment. Specifically, during their first month, future LTCs tend to be more active and show more community-oriented attitude than other joiners. Joiners who start by commenting on instead of reporting an issue or ones who succeed to get at least one reported issue to be fixed, more than double their odds of becoming an LTC. The macro-climate with high project relative sociality and the micro-climate with a large, productive, and clustered peer group increase the odds. On the contrary, the macro-climate with high project popularity and the micro-climate with low attention from peers reduce the odds. This implies that the interaction between individual's attitude and project's climate are associated with the odds that an individual would become a valuable contributor or disengage from the project. Our findings may provide a basis for empirical approaches to design a better community architecture and to improve the experience of contributors.},
booktitle = {Proceedings of the 34th International Conference on Software Engineering},
pages = {518–528},
numpages = {11},
location = {Zurich, Switzerland},
series = {ICSE '12}
}

@inproceedings{10.5555/1260984.1261217,
author = {Bird, Christian and Gourley, Alex and Devanbu, Prem},
title = {Detecting Patch Submission and Acceptance in OSS Projects},
year = {2007},
isbn = {0769528309},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.},
booktitle = {Proceedings of the 29th International Conference on Software Engineering Workshops},
pages = {26},
series = {ICSEW '07}
}

@inproceedings{10.1109/MSR.2007.6,
author = {Bird, Christian and Gourley, Alex and Devanbu, Prem},
title = {Detecting Patch Submission and Acceptance in OSS Projects},
year = {2007},
isbn = {076952950X},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/MSR.2007.6},
doi = {10.1109/MSR.2007.6},
abstract = {The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.},
booktitle = {Proceedings of the Fourth International Workshop on Mining Software Repositories},
pages = {26},
series = {MSR '07}
}

@inproceedings{10.5555/977397.977723,
author = {Capiluppi, Andrea and Morisio, Maurizio and Lago, Patricia},
title = {Evolution of understanding in OSS projects},
year = {2004},
isbn = {076952107X},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Empirical papers on Open Source software should tryand formulate reasons for successes as Linux, Apacheand some other flagship projects.What we need to understand about this topic is on the process ofproducing software through cooperation of differentefforts.Albeit many success reasons for these projectsare inherently due to the application domain that theproject develops, architectural and conceptual views ofthe code have to be considered as key factors whenconsidering community efforts and joint decisions.In this work we focus our attention on what isperceived of a source code when investigating itsstructure.We do this considering that structure as aproxy for the conceptual architecture of theapplication.A metric is developed based on somecurrent assumptions, and it is test over a sample ofOpen Source projects.What is interesting to note, isthat refactoring efforts are clearly visible whenintended as reduction of complexity of source code.Our second observation is that, based on what an OpenSource software currently does, i.e. its applicationdomain, there's a threshold value that several projectstend to.},
booktitle = {Proceedings of the Eighth Euromicro Working Conference on Software Maintenance and Reengineering (CSMR'04)},
pages = {58},
series = {CSMR '04}
}

@inproceedings{10.1109/ICCGI.2006.36,
author = {Kim, Dae-Woo and Lim, Hyun-Min and Lee, Sang-Kon},
title = {Performing Verification and Validation for KT-OSS Development},
year = {2006},
isbn = {0769526292},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/ICCGI.2006.36},
doi = {10.1109/ICCGI.2006.36},
abstract = {This paper describes verification and validation activities in KT-OSS (Korea Telecom Operations Supports System) development. In this paper, the verification and verification phases for KT-OSS development are based on the general software development lifecycle and add an additional phase to the lifecycle. To success KT-OSS development, we needed appropriate tests which focused on functionality, reliability, usability, efficiency in the development process of KT-OSS. This paper describes various tests performed in the KT-OSS development process and tests for maintaining the developed system according to the phases. And to control the quality for KT-OSS, we organized a testing \& evaluation department which is independent from a development department. Through these testing activities, we have developed KT-OSS and released it successfully.},
booktitle = {Proceedings of the International Multi-Conference on Computing in the Global Information Technology},
pages = {37},
keywords = {Verification, Validation, Testing, Software Development Lifecycle, OSS},
series = {ICCGI '06}
}

@inproceedings{10.1145/2652524.2652549,
author = {Al Alam, S. M. Didar and Shahnewaz, S. M. and Pfahl, Dietmar and Ruhe, Guenther},
title = {Monitoring bottlenecks in achieving release readiness: a retrospective case study across ten OSS projects},
year = {2014},
isbn = {9781450327749},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2652524.2652549},
doi = {10.1145/2652524.2652549},
abstract = {Context: Not releasing software on time can cause substantial loss in revenue. Continuous awareness of the product release status is required. Release readiness is a time-dependent attribute of the status of the product release, which aggregates the degree of satisfaction of a portfolio of release process and product measures.Goal: At different stages of a release cycle, the goal is to understand frequencies and pattern of occurrence of factors affecting project success by restricting the status of release readiness (called bottlenecks).Method: As a form of explorative case study research, we analyzed ten open source software (OSS) projects taken from the GitHub repository. As a retrospective study covering a period of 28 weeks, we monitored eight release readiness attributes and identified their impact on release readiness over time across the ten projects.Results: Feature completion rate, Bug fixing rate, and Features implemented were observed as the most frequent bottlenecks. The most frequent transition between bottlenecks is from Pull-request completion rate to Bug fixing rate. With the exception of Pull-request completion rate, no significant differences were found in occurrence of bottleneck factors between early and late stage of the release cycle.Conclusions: We received an initial understanding of the most frequent bottleneck factors for release readiness and their likelihood of subsequent occurrence. This is intended to guide the effort spent on improving release engineering.},
booktitle = {Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement},
articleno = {60},
numpages = {4},
keywords = {retrospective analysis, release readiness, exploratory case study, bottleneck identification},
location = {Torino, Italy},
series = {ESEM '14}
}

@inproceedings{10.5555/1260984.1261214,
author = {Rigby, Peter C. and Hassan, Ahmed E.},
title = {What can OSS mailing lists tell us? A preliminary psychometric text analysis of the Apache developer mailing list},
year = {2007},
isbn = {0769528309},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.},
booktitle = {Proceedings of the 29th International Conference on Software Engineering Workshops},
pages = {23},
series = {ICSEW '07}
}

@inproceedings{10.1109/MSR.2007.35,
author = {Rigby, Peter C. and Hassan, Ahmed E.},
title = {What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List},
year = {2007},
isbn = {076952950X},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/MSR.2007.35},
doi = {10.1109/MSR.2007.35},
abstract = {Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.},
booktitle = {Proceedings of the Fourth International Workshop on Mining Software Repositories},
pages = {23},
series = {MSR '07}
}