Sophia Vargas

Sophia Vargas is an Analyst, Researcher, and Program Manager in Google’s Open Source Programs Office. In this role she leads research efforts that investigate open source project health, contributor experience, operational models, and the sustainability of open source ecosystems.

Research Areas

Authored Publications
Sort By
  • Title
  • Title, descending
  • Year
  • Year, descending
Mentorship, Interrupted: How AI Disrupts the GSoC Pipeline and Why Mentors Matter More
Ruizhe Xing
Mary Radomile
Zixuan Feng
Stephanie Taylor
Anita Sarma
2026
Preview abstract Generative AI (GenAI) can ease software contribution while making contributors and their work harder to assess. We investigate how this tension affects the sustainability of the Google Summer of Code (GSoC) mentoring pipeline and how stakeholders respond, through a sequential qualitative study of mentor mailing-list discussions and interviews with 15 mentors and organization administrators. Participants reported that GenAI helps with onboarding, coordination, and initial review but weakens evidence of mentees’ capability, understanding, and ownership, adding verification and governance work that strains newcomer learning and mentors’ willingness to continue. Drawing on reported strategies that distribute responsibility across mentees, mentors, organizations, and GSoC, we propose a GenAI Mentoring and Governance Decision Framework of five acceptable-use stances. Sustaining OSS mentoring requires protecting newcomer development and mentor capacity together, with governance adapted to local conditions. View details
Preview abstract Open source software is used pervasively, with many citing cost benefits such as time saved in software engineering (SWE) hours. However, the actual costs to use open source software are non-zero and not often discussed or measured. We designed a study to evaluate the effort and cost (in SWE hours) associated with maintaining open source software forks within Google. Our study showed that the majority of updates take 4 hours or less, however the long tail could be days to months. Our results suggest that level of effort may be indicated by custom patches, external dependency volume, and project size, while package age and internal usage levels did not appear to have a consistent impact on update complexity. View details
Preview abstract Usage telemetry can be an effective tool to assess the value and impact of an open source project, as well as enable time-strapped maintainers to prioritize support for features, versions, and/or components that are actively used. However, many open source users see incorporating usage telemetry into a project as an invasion of privacy, especially for projects that did not launch with embedded telemetry. Even with an adequate value proposition, many users will opt out, or choose not to opt in to share their data with a project, organization, or company. Tools are emerging to address this need for usage telemetry, however, many are still met with skepticism by the privacy-minded community members. It is therefore important for many projects and companies that need to show the value and impact of open source projects to have reliable proxy metrics. This proof of concept exercise seeks to form hypotheses regarding the relationship between usage as measured by embedded telemetry and as indicated by proxy metrics to evaluate whether less-invasive proxy metrics are sufficiently reliable in the detection of usage trends in open source projects. View details
Preview abstract While open source ecosystems have fluid membership by nature, explicit boundaries are necessary to conduct research and analysis around projects and their communities as these exercises require a set number of sources to count as part of this effort. The ideal solution to this problem would provide researchers and analysts with a common approach to identify what is part of or affiliated with a project community and ecosystem. View details
Preview abstract In 2022, the research team within Google’s Open Source Programs Office launched a study to better understand open source developers, contributors, and maintainers. Since Alphabet is a large consumer of and contributor to open source, our primary goals were to investigate the evolving needs and motivations of open source contributors, and to learn how we can best support the communities we depend on. We also wanted to share our findings with the community in order to further research efforts and our collective understanding of open source work. View details
×