GSoC 2026: Rust Project Welcomes 13 New Contributors Through Google Summer of Code

Introduction

For its third consecutive year, the Rust Project is taking part in the Google Summer of Code (GSoC) 2026—a global initiative by Google that introduces newcomers to open-source development. Earlier this year, the Rust team published a set of project ideas and began engaging with potential contributors on their Zulip chat platform. These preliminary discussions often led to meaningful interactions, with some applicants even making significant contributions to various Rust repositories before the official start of GSoC.

By the end of March, applicants had submitted their detailed proposals. This year saw a remarkable 50% increase in submissions, with 96 proposals received—a testament to growing interest in Rust’s open-source ecosystem. However, like many other GSoC organizations, the Rust team faced challenges with a number of AI-generated proposals and contributions produced by automated agents. While these issues remained manageable, they required careful filtering.

The Selection Journey

Proposal Evaluation

GSoC requires participating organizations to produce an ordered list of the best proposals. For a project as large and diverse as Rust, this is always a demanding task. Mentors evaluated each proposal based on several key factors:

• Prior interactions with the applicant during the discussion phase
• Existing contributions to Rust repositories
• Quality and clarity of the proposal itself
• Importance of the proposed project for the Rust community
• Mentor bandwidth and availability, ensuring mentors could provide adequate support

Unfortunately, the past few weeks saw some mentors lose their funding for Rust-related work, forcing the cancelation of a few potential projects. Despite these setbacks, the remaining mentors worked diligently to assess all submissions.

Selecting the Best

Even when multiple proposals targeted the same project topic, only one could be chosen per topic—a standard GSoC rule. Additionally, the team had to avoid assigning a single mentor to multiple projects to prevent overload. After careful consideration, the Rust Project narrowed the list to the strongest proposals that could realistically be supported by the available mentor pool. This ranked list was submitted to Google, and the team eagerly awaited the final acceptance numbers.

The Accepted Projects

On April 30, 2026, Google announced the officially accepted GSoC projects. The Rust Project is delighted to share that 13 proposals have been greenlit—a significant number that underscores the community enthusiasm and mentor dedication. Below is the complete list of accepted projects, in alphabetical order, along with their authors and assigned mentors.

List of Selected Projects

• 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
• Bringing autodiff and offload into Rust CI – by Shota Sugano, mentored by Manuel Drehwald
• Debugger for Miri – by Mohamed Ali Mohamed, mentored by Oli Scherer
• Implementing impl and mut restrictions – by Ryosuke Yamano, mentored by Jacob Pratt and Urgau
• Improving Ergonomics and Safety of serialport-rs – by Tanmay, mentored by Christian Meusel

Note: The original announcement included a trailing 'l' in the list, which appears to be a formatting artifact; it has been omitted here.

Each of these projects addresses a critical area of Rust development, from GPU offloading and WebAssembly integration to debugging tools and API safety. The Rust community looks forward to seeing these contributors grow and make lasting impacts through their GSoC experience.

For those interested in learning more about the GSoC program or following the progress of these projects, stay tuned to the official Rust blog and Zulip channels. Congratulations to all selected participants!