Bridging the Gap: Mentorship Programs for Your Open Source Journey

### Overview In this talk, Stephanie Taylor, a program manager with Google's Open Source Programs Office who has led Google Summer of Code (GSoC) for 10 years, discusses how structured open-source mentorship programs help lower barriers to entry for beginners. Joining open-source projects can be daunting due to the sheer volume of repositories, fear of inadequate expertise, or uncertainty about how to start. Mentorship programs provide dedicated mentors, guided project scoping, structured timelines, and stipends to help newcomers gain real-world experience and become long-term contributors across technical and non-technical domains.

### Key Topics - **Non-Code and Coding Contributions:** While coding in languages such as C++ is prominent, open-source communities actively require technical writers, UX/UI designers, marketing contributors, software testers, event planners, and project managers. - **Preparation and Project Selection:** Beginners are encouraged to examine community chat logs, mailing lists, licenses, and beginner documentation ("first issues") to assess community culture, priorities, and technical fit before applying. Experience requirements for GSoC typically align with roughly six months of coding experience (or three months of intensive bootcamps), rather than expert-level knowledge. - **Comparison of Three Major Programs:** - **Google Summer of Code (GSoC):** An annual, fully virtual program running for over 22 years for adults over 18 who are students or beginners in open source (less than two years of experience). Involves around 190–200 mentoring organizations, ~1,200 contributors annually, and projects structured into 90-hour, 175-hour, or 350-hour scopes (typically spanning 12 weeks from May to August). Requires an application proposal and yields a stipend paid at midpoint and completion. - **Outreachy:** Offers 12-week paid internships across two cohorts annually (mid-year and winter) for individuals facing underrepresentation, systemic bias, or discrimination in their home country's tech industry. Outreachy spans coding and non-coding disciplines (e.g., UX, data science, documentation) with fixed 30-hour/week commitments and a multistage application involving initial essays, a recorded contribution period, and final applications. - **Linux Foundation Mentorship Program (LFMP):** Launched in 2019, running three cohorts a year (spring, summer, fall) with 12-week full-time or 24-week part-time tracks focusing on coding for Linux Foundation ecosystem projects, complete with milestone stipends.

### Technical Details & Program Dynamics - **Project Timelines & Scope:** For GSoC 2026, mentoring organizations are announced February 19, contributor applications open March 16–31, accepted contributors are announced in late April, and coding runs from late May to late August. - **Application Strategy:** Taylor highlights that cold-submitting proposals without community engagement will lead to rejection. Applicants must actively participate in community discussions, submit small pull requests or bug fixes during application windows, and collaborate on proposal ideas. - **Program Rules & Sequencing:** Participants cannot engage in multiple programs simultaneously. Outreachy rules prohibit individuals who have already completed GSoC from participating in Outreachy, whereas contributors often complete Outreachy or LFMP first before joining GSoC. - **Mentoring Org Criteria:** For organizations wishing to mentor in GSoC, they must have an established active community (typically 7–8+ active members) and release code under an Open Source Initiative (OSI)-approved license. GSoC balances focus areas annually, noting an increased emphasis on security and AI.

### Takeaways - Mentorship programs provide guided, real-world ownership of production code and contributions impacting large user bases without requiring prior domain mastery. - Time management and communication are paramount: applicants must select realistic project scopes (e.g., 90 vs. 350 hours) that match their schedule. - Perceived hurdles like language barriers or timezone mismatches are generally non-issues in globally distributed, asynchronous virtual open-source communities.