{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiefrbysrbyefplsgkwvqxms45qxnvl43fb3uelxg2p2fzvyo2cgbu",
    "uri": "at://did:plc:lujatorbzcq2chhxnvjgc464/app.bsky.feed.post/3mkqzj5q2xqm2"
  },
  "path": "/2026/04/30/gsoc-2026-selected-projects/",
  "publishedAt": "2026-04-30T00:00:00.000Z",
  "site": "https://blog.rust-lang.org",
  "tags": [
    "previously announced",
    "Google Summer of Code (GSoC)",
    "GSoC project ideas",
    "Zulip",
    "A Frontend for Safe GPU Offloading in Rust",
    "Marcelo Domínguez",
    "Manuel Drehwald",
    "Adding WebAssembly Linking Support to Wild",
    "Kei Akiyama",
    "David Lattimore",
    "Bringing autodiff and offload into Rust CI",
    "Shota Sugano",
    "Debugger for Miri",
    "Mohamed Ali Mohamed",
    "Oli Scherer",
    "Implementing impl and mut restrictions",
    "Ryosuke Yamano",
    "Jacob Pratt",
    "Urgau",
    "Improving Ergonomics and Safety of serialport-rs",
    "Tanmay",
    "Christian Meusel",
    "libc: transition differing bit-width time and offset variants and deprecate bug-prone constants",
    "Adam Martinez",
    "Trevor Gross",
    "Link Linux kernel and its Modules with Wild",
    "Vishruth Thimmaiah",
    "Migrating rust-analyzer assists to SyntaxEditor",
    "Shourya Sharma",
    "Chayim Refael Friedman",
    "Lukas Wirth",
    "Port std::arch test suite to rust-lang/rust",
    "Sumit Kumas",
    "Jakub Beránek",
    "Folkert de Vries",
    "Reorganizing tests/ui/issues",
    "Matthew",
    "Teapot",
    "Kivooeo",
    "Utilize debugger APIs to improve debug info test accuracy and error reporting",
    "Anthony Bolden",
    "Jieyou Xu",
    "XDG path support for rustup",
    "Guicheng Liu",
    "rami3l",
    "project idea list",
    "Rust Project Goals"
  ],
  "textContent": "As previously announced, the Rust Project is participating in Google Summer of Code (GSoC) 2026. GSoC is a global program organized by Google that is designed to bring new contributors to the world of open source.\n\nA few months ago, we published a list of GSoC project ideas, and started discussing these projects with potential GSoC applicants on our Zulip. We had many interesting discussions with the potential contributors, and even saw some of them making non-trivial contributions to various Rust Project repositories before GSoC officially started!\n\nThe applicants prepared and submitted their project proposals by the end of March. This year, we received 96 proposals, which is a 50% increase from last year. We are glad that there was again a lot of interest in our projects! Like many other GSoC organizations this year, we somewhat struggled with some AI-generated proposals and low-quality contributions generated using AI agents, but it stayed manageable.\n\nGSoC requires us to produce an ordered list of the best proposals, which is always challenging, as Rust is a big project with many priorities. Our mentors examined the submitted proposals and evaluated them based on their prior interactions with the given applicant, their contributions so far, the quality of the proposal itself, but also the importance of the proposed project for the Rust Project and its wider community. We also had to take mentor bandwidth and availability into account. Unfortunately, we had to cancel some projects due to several mentors losing their funding for Rust work in the past few weeks.\n\nAs is usual in GSoC, even though some project topics received multiple proposals1, we had to pick only one proposal per project topic. We also had to choose between proposals targeting different work to avoid overloading a single mentor with multiple projects. In the end, we narrowed the list down to the best proposals that we could still realistically support with our available mentor pool. We submitted this list and eagerly awaited how many of them would be accepted into GSoC.\n\n##  Selected projects\n\nOn the 30th of April, Google has announced the accepted projects. We are happy to share that **13** Rust Project proposals were accepted by Google for Google Summer of Code 2026. That is a lot of projects! We are really happy and excited about GSoC 2026!\n\nBelow you can find the list of accepted proposals (in alphabetical order), along with the names of their authors and the assigned mentor(s):\n\n  * **A Frontend for Safe GPU Offloading in Rust** by Marcelo Domínguez, mentored by Manuel Drehwald\n  * **Adding WebAssembly Linking Support to Wild** by Kei Akiyama, mentored by David Lattimore\n  * **Bringing autodiff and offload into Rust CI** by Shota Sugano, mentored by Manuel Drehwald\n  * **Debugger for Miri** by Mohamed Ali Mohamed, mentored by Oli Scherer\n  * **Implementing impl and mut restrictions** by Ryosuke Yamano, mentored by Jacob Pratt and Urgau\n  * **Improving Ergonomics and Safety of serialport-rs** by Tanmay, mentored by Christian Meusel\n  * **libc: transition differing bit-width time and offset variants and deprecate bug-prone constants** by Adam Martinez, mentored by Trevor Gross\n  * **Link Linux kernel and its Modules with Wild** by Vishruth Thimmaiah, mentored by David Lattimore\n  * **Migrating rust-analyzer assists to SyntaxEditor** by Shourya Sharma, mentored by Chayim Refael Friedman and Lukas Wirth\n  * **Port std::arch test suite to rust-lang/rust** by Sumit Kumas, mentored by Jakub Beránek and Folkert de Vries\n  * **Reorganizing tests/ui/issues** by Matthew, mentored by Teapot and Kivooeo\n  * **Utilize debugger APIs to improve debug info test accuracy and error reporting** by Anthony Bolden, mentored by Jakub Beránek and Jieyou Xu\n  * **XDG path support for rustup** by Guicheng Liu, mentored by rami3l\n\n\n\n**Congratulations to all applicants whose project was selected!** Our mentors are looking forward to working with you on these exciting projects to improve the Rust ecosystem. You can expect to hear from us soon, so that we can start coordinating the work on your GSoC projects.\n\nWe are excited to mentor three contributors who already experienced GSoC with us in the previous year. Welcome back, Kei, Marcelo and Shourya!\n\nWe would like to thank all the applicants whose proposal was sadly not accepted, for their interactions with the Rust community and contributions to various Rust projects. There were some great proposals that did not make the cut, in large part because of limited mentorship capacity. However, even if your proposal was not accepted, we would be happy if you would consider contributing to the projects that got you interested, even outside GSoC! Our project idea list is still current and could serve as a general entry point for contributors that would like to work on projects that would help the Rust Project and the Rust ecosystem. Some of the Rust Project Goals are also looking for help.\n\nThere is a good chance we'll participate in GSoC next year as well (though we can't promise anything at this moment), so we hope to receive your proposals again in the future!\n\nThe accepted GSoC projects will run for several months. After GSoC 2026 finishes (in autumn of 2026), we will publish a blog post in which we will summarize the outcome of the accepted projects.\n\n  1. The most popular project topic received fourteen different proposals! ↩\n\n\n",
  "title": "Announcing Google Summer of Code 2026 selected projects",
  "updatedAt": "2026-04-30T00:00:00.000Z"
}