How to Get Your Project Selected for Google Summer of Code with the Rust Project

Introduction

Every year, the Rust Project participates in Google Summer of Code (GSoC) to welcome new contributors into open source. The process of selecting projects is competitive and thoughtful. For the 2026 edition, we received 96 proposals—a 50% increase from the previous year—and ultimately accepted 13 outstanding projects. If you're a future applicant or mentor, understanding how proposals are evaluated and selected can help you prepare a strong application. This step-by-step guide walks you through the entire selection journey, from idea to acceptance.

What You Need

Before you start, make sure you have:

• A clear understanding of the Rust Project's goals and ongoing initiatives
• Familiarity with GSoC program rules and timelines
• Access to the Rust Project's Zulip chat for discussions
• Prior experience (or willingness to learn) contributing to open-source Rust repositories
• A well-defined project idea that aligns with the Rust Project's priorities
• Mentor availability and bandwidth (if you're a mentor) — note that some mentors lost funding for Rust work in the weeks before selection
• Ability to produce a high-quality, original proposal (avoid AI-generated content)

Step-by-Step Guide

Step 1: Explore Project Ideas and Start Conversations

The Rust Project publishes a list of GSoC project ideas well before the application deadline. Browse these ideas and pick one that excites you. Then, join the Rust Zulip channel and start discussing the project with the community and potential mentors. Early engagement not only helps you refine your idea but also shows your commitment. Many successful applicants made non-trivial contributions to Rust repositories even before GSoC officially began.

Step 2: Build a Track Record of Contributions

Mentors pay close attention to your prior interactions with the Rust Project. Start contributing early—fix bugs, write documentation, or implement small features. Quality matters more than quantity. Avoid using AI agents to generate contributions, as these are easily spotted and can harm your application. Real, human-coded contributions demonstrate your skills and dedication.

Step 3: Prepare Your Proposal

By the end of March, you must submit a detailed project proposal. Your proposal should include:

• Clear project goals and deliverables
• A realistic timeline (12 weeks)
• How your project benefits the Rust Project and its community
• Your background and relevant experience
• Any prior contributions to the project (link them)

Write in your own words—originality is key. Proposals that appear AI-generated may be rejected or deprioritized.

Step 4: Understand the Selection Criteria

Mentors evaluate proposals based on several factors:

• Prior interactions with the applicant on Zulip or via contributions
• Quality and originality of the proposal
• Importance of the proposed project for the Rust ecosystem
• Mentor bandwidth — mentors cannot supervise more than one project each
• Balance across different project topics; only one proposal per topic is accepted

Note that some projects had to be canceled due to mentors losing funding, so the final list depends on available mentors.

Step 5: Wait for the Ordered List

After reviewing all submissions, mentors compile an ordered list of the best proposals. The Rust Project then submits this list to Google. Google makes the final acceptance decisions. This year, Google accepted 13 of our proposals (out of 96 submitted).

Step 6: Celebrate (or Learn) from the Outcome

If your proposal is accepted, congratulations! If not, use the experience to improve. Many rejected proposals are high quality; they may just not have fit the available mentor slots or project balance. Consider applying again next year with refinements.

Tips for Success

• Start early. The earlier you engage, the more time you have to impress mentors.
• Be authentic. Avoid using AI tools to write your proposal or contributions; mentors value genuine work.
• Communicate actively. Ask questions, seek feedback, and show your interest on Zulip.
• Focus on community impact. Projects that solve real problems for Rust users have higher priority.
• Check mentor availability. If a mentor is overloaded, your project may not be selected even if the proposal is strong.
• Don’t get discouraged by the numbers. With 96 proposals for 13 slots, competition is tough. Each attempt builds your skills.

By following these steps, you'll maximize your chances of having your project selected for Google Summer of Code with the Rust Project. Good luck!