Rust's GSoC 2026 Projects: Your Questions Answered

Google Summer of Code (GSoC) 2026 is underway for the Rust Project, and we're thrilled to share that 13 outstanding proposals have been accepted. With 96 submissions this year—a 50% increase from last year—the selection process was both exciting and challenging. Below, we answer your most common questions about the program, the projects, and what comes next.

1. What is Google Summer of Code and why does Rust participate?

How are proposals selected? Google Summer of Code is a global, paid internship program that pairs newcomers with open-source organizations. The Rust Project participates to bring fresh talent into our ecosystem, reduce barriers for new contributors, and accelerate development on key tools and libraries. GSoC offers a structured environment where contributors develop real-world skills under the guidance of experienced mentors. For Rust, this means tackling projects that might otherwise remain on the back burner—everything from GPU offloading support to improving serial port safety. The program is a win-win: contributors gain invaluable experience, and the Rust community gets meaningful improvements.

2. How did the Rust Project select proposals for GSoC 2026?

Proposals were evaluated on multiple criteria: the applicant’s prior interactions with the community, the quality and depth of their submitted proposal, and the project’s importance to the Rust ecosystem. Mentors also considered the contributor’s existing contributions—some even made non-trivial patches before the official GSoC start. Limited mentor bandwidth forced tough trade-offs; we had to cancel a few projects due to mentor funding losses. After careful review, we produced an ordered list of the strongest proposals and submitted it to Google. Ultimately, 13 were accepted.

3. How many proposals were submitted and what challenges arose?

We received 96 proposals this year, a 50% increase over 2025. While we were pleased by the enthusiasm, the surge came with challenges. Like many GSoC organizations, we encountered AI-generated proposals and low-quality contributions produced by AI agents. Although manageable, these forced mentors to spend extra time verifying authenticity. We also had to navigate limited mentor availability—some mentors lost their funding for Rust work shortly before selection, forcing us to drop viable projects. Despite these hurdles, we narrowed the list to the best proposals we could realistically support.

4. Which projects were accepted and who are the mentors?

Google accepted 13 projects on April 30. Below are six of them (alphabetically):

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

The remaining seven projects cover other areas of the Rust ecosystem. Full details will be shared as work progresses.

5. What impact will these projects have on the Rust ecosystem?

The selected projects target critical areas: safe GPU offloading will enable high-performance computing directly in Rust, while WebAssembly linking support in Wild advances WebAssembly tooling. Integrating autodiff and offload into CI automates testing of numerical libraries. A debugger for Miri will simplify undefined behavior detection. Impl and mut restrictions aim to improve language safety, and improvements to serialport-rs will make hardware communication more ergonomic and secure. Together, these contributions strengthen Rust’s position as a reliable systems language for diverse domains—from embedded systems to scientific computing. Mentors will guide contributors to produce production-ready code that benefits the entire community.

6. How can the community follow or contribute to these projects?

You can follow progress on the Rust Zulip in the GSoC stream, where contributors and mentors post regular updates. Each project will have its own tracking issue in the relevant repository. If you're interested in contributing, watch those repositories or join the Zulip discussions—mentors often welcome community feedback and testing. The final deliverables will be code merged into official Rust repositories, so you can also track changes in the commit history.

7. What lessons were learned from this year's GSoC experience?

The surge in proposals highlighted both the growing interest in Rust and the need for robust proposal vetting. AI-generated content required manual inspection, so future editions may add an initial contribution checkpoint before proposal evaluation. Mentor funding instability remains a risk; we plan to diversify funding sources to guarantee mentor support. Despite these challenges, the 50% increase in proposals and 13 accepted projects show that structured mentoring programs like GSoC are vital for sustaining Rust’s growth. We’re excited to see these projects come to life and encourage newcomers to apply next year.