How to Select and Announce Google Summer of Code Projects: A Step-by-Step Guide for Open Source Organizations

Introduction

Participating in Google Summer of Code (GSoC) is a rewarding way to bring new contributors into your open source project. However, the process of selecting and announcing projects involves careful planning, community engagement, and evaluation. The Rust Project’s experience with GSoC 2026 offers a practical blueprint. This guide walks you through each step, from preparing project ideas to announcing accepted proposals, using real-world examples from the Rust community. By following these steps, your organization can maximize the impact of GSoC while navigating challenges like AI-generated proposals and limited mentor bandwidth.

What You Need

• An open source project accepted into GSoC (Google’s eligibility criteria include having an established open source community and a track record of mentoring).
• A dedicated mentor pool – experienced contributors willing to guide participants for the program duration.
• A communication platform (e.g., Zulip, Slack, Discord) for real-time discussions with applicants.
• A repository of project ideas – clearly defined tasks or features that can be completed in a few months.
• Evaluation criteria – know what matters most: proposal quality, prior contributions, community alignment, and mentor availability.
• Time and bandwidth to review proposals, interact with applicants, and handle administrative tasks.

Step-by-Step Guide

Step 1: Publish Compelling Project Ideas

About two to three months before the application deadline, publish a list of project ideas on your project’s website or wiki. Make each idea specific enough to be achievable, but open enough to allow creativity. For example, the Rust Project published ideas ranging from “Implementing impl and mut restrictions” to “Adding WebAssembly Linking Support to Wild”. Include:

• A clear description of the task.
• Expected outcomes and deliverables.
• Required skills and experience level.
• Potential mentors (if possible).

Promote your ideas on social media, mailing lists, and relevant forums. The Rust team used their Zulip channel to discuss these ideas with potential applicants, which sparked early interest.

Step 2: Actively Engage with Potential Contributors

Encourage applicants to start contributing before the official GSoC start date. The Rust Project saw many contributors making non-trivial contributions to repositories after initial discussions. This early engagement helps you assess their skills and dedication. Respond promptly to questions, provide feedback on small pull requests, and build rapport. Use your communication platform to host Q&A sessions or office hours.

Be aware that some applicants may use AI agents to generate low-quality contributions or proposals. Stay vigilant – look for genuine understanding of the codebase and thoughtful interactions.

Step 3: Collect and Review Proposals

Set a clear deadline for proposal submissions. In 2026, the Rust Project received 96 proposals – a 50% increase from the previous year. This influx requires a systematic review process. Gather mentors and evaluate each proposal based on:

• Prior interactions – Did the applicant engage meaningfully with your community?
• Contributions so far – Quality and relevance of any code, documentation, or tests they’ve provided.
• Proposal quality – Is the plan clear, feasible, and well-structured?
• Importance to your project – Does the work align with your roadmap or solve a critical need?
• Mentor bandwidth – Can you assign a mentor who can dedicate enough time?

Due to mentor availability, the Rust Project had to cancel some project slots when mentors lost funding. Have backup mentors or flexible plans.

Step 4: Prioritize and Narrow Down the List

GSoC requires an ordered list of the best proposals. This is challenging because you must balance multiple factors. Rules include:

• Only one proposal per project topic (even if multiple excellent proposals arrive).
• Balance mentor workload – avoid assigning too many projects to a single mentor.
• Prioritize proposals that are most likely to succeed given your mentor pool.

The Rust team used a combination of mentor votes and project needs. They produced a ranked list that reflected both quality and practical support. Remember that some projects may need to be cut due to funding changes – communicate transparently with affected applicants.

Step 5: Submit Your List to Google

Once your ordered list is finalized, submit it through the GSoC portal before the deadline. Google will review and may adjust the list based on their own criteria. In 2026, the Rust Project submitted a list and then waited for the official acceptance announcement.

Step 6: Announce Accepted Projects

On the announcement date (April 30 for 2026), share the happy news. The Rust Project announced 13 accepted projects – a large number that required careful coordination. Create a blog post or news item listing each project with the author and mentor(s). Use alphabetical order or any logical grouping. For example:

• A Frontend for Safe GPU Offloading in Rust by Marcelo Domínguez, mentored by Manuel Drehwald
• Adding WebAssembly Linking Support to Wild by Kei Akiyama, mentored by David Lattimore
• Debugger for Miri by Mohamed Ali Mohamed, mentored by Oli Scherer
• ... and ten others.

Celebrate the contributors, thank your mentors, and outline next steps for the program.

Tips for Success

• Start early. Engage with applicants months before the deadline to build a strong pipeline.
• Be realistic about mentor capacity. Even with many proposals, it’s better to accept fewer projects than to overload your mentors.
• Watch for AI-generated submissions. Low-quality proposals can waste time; use early contributions to gauge genuine interest.
• Communicate openly. If a project topic cannot be supported (e.g., mentor loss), tell applicants ASAP so they can explore other organizations.
• Document your process. After GSoC, review what worked and improve for next year.
• Leverage your community. Use tools like Zulip, GitHub Discussions, and regular check-ins to maintain momentum.

By following this guide, your open source organization can navigate the GSoC selection process with confidence and bring in talented new contributors who will strengthen your project for years to come.