Participating in Google Summer of Code with Rust: A Step‑by‑Step Guide

Overview

Google Summer of Code (GSoC) is a global program that introduces new contributors to open source. The Rust Project has been an active participant for years, and 2026 marks another exciting chapter. This guide walks you through everything you need to know to prepare, apply, and succeed in GSoC with Rust, using the real 2026 selected projects as concrete examples.

Prerequisites

Before diving in, ensure you meet these prerequisites:

• Rust knowledge: Basic proficiency with the language (ownership, borrowing, generics, unsafe code).
• Open source experience: Familiarity with Git, GitHub, pull requests, and code reviews.
• Community engagement: Willingness to participate in public discussions (e.g., Zulip, GitHub issues).
• Time commitment: Ability to dedicate 10–20 hours per week during the GSoC period.

Step‑by‑Step Guide: From Idea to Accepted Proposal

1. Explore the Project Ideas

The Rust Project publishes a curated list of GSoC project ideas well before the application deadline. In 2026, these ranged from GPU offloading frontends to WebAssembly linking and Miri debuggers. Study each idea carefully, noting required skills and expected outcomes.

2. Engage on Zulip (Rust’s Communication Platform)

All potential applicants are strongly encouraged to join the Rust GSoC Zulip stream. This is where mentors discuss ideas, answer questions, and gauge interest. For example, in 2026, early discussions helped refine concepts like “Bringing autodiff and offload into Rust CI” and “Implementing impl and mut restrictions.” (See the full list in Accepted Projects.)

3. Make Meaningful Contributions

Mentors evaluate applicants not only on their proposals but on prior interactions and contributions. Aim to submit pull requests to the same repositories as your target project. Even small improvements—bug fixes, documentation, test cases—demonstrate your ability to work within the Rust ecosystem.

Example contribution (conceptual):

// Improving ergonomics of serialport-rs (one of the 2026 projects)
// Add a method to safely configure baud rate
pub fn set_baud_rate(&mut self, rate: u32) -> Result<(), Error> {
    // implementation
}

4. Write Your Proposal

By the end of March, prepare a detailed proposal. Include:

• Project overview and why you are passionate.
• Implementation plan with milestones, timeline, and deliverables.
• Background showing relevant contributions.
• Mentor alignment: reference your discussions with the mentor.

Important: Avoid AI‑generated content—mentors reported a 50% increase in proposals for 2026, many of which were low‑quality due to AI tools. Authenticity and personal effort matter.

5. Selection and Prioritisation

Mentors evaluate proposals based on:

• Quality and feasibility of the proposal.
• Strength of prior contributions and interactions.
• Importance of the project to the Rust community.
• Mentor bandwidth (some projects were dropped when mentors lost funding).

Because only one proposal per project topic could be selected, competition was fierce. In 2026, 96 proposals were received, and only 13 were accepted—a 13.5% acceptance rate. The final list (alphabetical) is shown in Accepted Projects.

Accepted Projects (GSoC 2026)

Here are the 13 selected projects, ordered alphabetically:

• A Frontend for Safe GPU Offloading in Rust – Marcelo Domínguez, mentored by Manuel Drehwald
• Adding WebAssembly Linking Support to Wild – Kei Akiyama, mentored by David Lattimore
• Bringing autodiff and offload into Rust CI – Shota Sugano, mentored by Manuel Drehwald
• Debugger for Miri – Mohamed Ali Mohamed, mentored by Oli Scherer
• Implementing impl and mut restrictions – Ryosuke Yamano, mentored by Jacob Pratt and Urgau
• Improving Ergonomics and Safety of serialport-rs – Tanmay, mentored by Christian Meusel

(Other projects omitted for brevity – see the full list on the Rust Blog.)

Common Mistakes to Avoid

Mistake 1: Relying on AI‑Generated Proposals

In 2026, many submissions were generic, copied from AI assistants. Mentors quickly identified these and rejected them. Always write your own proposal.

Mistake 2: Not Engaging Early Enough

Waiting until the last week to join Zulip or submit contributions hurt many applicants. Start discussions at least 4–6 weeks before the deadline.

Mistake 3: Overlooking Mentor Availability

Some excellent projects were rejected simply because the mentor had too many commitments or lost funding. When choosing a project, ask the mentor about their availability.

Mistake 4: Submitting Multiple Proposals in the Same Area

If you send proposals for several related projects, you risk overwhelming mentors. Focus on one well‑prepared proposal per topic.

Mistake 5: Ignoring the Community’s Needs

Proposals that addressed high‑priority Rust issues (like GPU offloading or Miri debugging) were favoured. Make sure your project aligns with the Rust Project’s strategic goals.

Summary

Google Summer of Code with Rust is a rewarding journey, but it requires dedicated preparation. Start early, engage with the community on Zulip, make real contributions, and craft a genuine proposal. Despite a 50% increase in applicants, only 13 projects were accepted in 2026—stand out by showing your passion and skill. Use the examples above to guide your path, and remember: mentors value authenticity and persistence above all. Good luck!