#open-source

Part 1 covered preparation and choosing an organization. This part focuses on contribution and communication -- the habits that make technical skill visible to maintainers. It covers Git and GitHub Flow, keeping forks current, and pull-request hygiene that respects review bandwidth. There is also guidance on reading project guidelines, handling feedback, and using AI responsibly without dumping unowned volume on mentors. The closing thread is how to talk to communities clearly so your work gets noticed for the right reasons.

Over a few years of mentoring for OWASP and the Python Software Foundation, I have watched contributors succeed and stall in Google Summer of Code. This first part starts with what GSoC really is -- remote open-source work under mentors, not a traditional internship -- and what evaluations actually reward. It then covers how to choose and research an organization, including why smaller orgs can be a smarter bet than the most competitive names. From there it walks through joining the community early, making real contributions before proposals are due, and shaping a standout application. The through-line is preparation and relationships, not last-minute proposal writing alone.