Skip to content

Latest commit

 

History

History
74 lines (46 loc) · 2.75 KB

File metadata and controls

74 lines (46 loc) · 2.75 KB
title GSoC Applicant Template
category Developer > Google Summer of Code

We are thrilled to announce that Submitty has been accepted
to Google Summer of Code (GSoC) 2026!

See also: How to Apply to Submitty for Google Summer of Code 2026

See also: Reports from previous Google Summer of Code participants


NOTE: The 2026 Submitty GSoC Application Template will be posted here on or before March 1st, 2026. Thanks for your patience.


[comment]: <> NOTE: The 20XX Submitty GSoC Template will be available for download [comment]: <> when Google announces the organizations accepted for Google Summer [comment]: <> of Code 20XX.

[comment]:Submitty has applied for acceptance to Google Summer of Code (GSoC) 2026. [comment]:The organizations selected for Summer 2026 Google Summer of Code will be announced in [comment]:late February.

To ensure that the Submitty Org Admins and Mentors have all of the information about your ideas, project plan, and availability for Google Summer of Code 2026, we ask you to use the Submitty Applicant Template.

The template will include:

  • Your skills, relevant coursework, non-course experience, and future career goals that qualify you to work on this project.

  • Approximate schedule for the summer: start date, end date, and number of hours of work per week.

  • Description of any classes, employment, or other time commitments during that time period.

  • Engagement with the Submitty project team during the application period. This includes participation in public discussions on our Zulip server: asking technical questions about issues and work-in-progress PRs, helping other prospective applicants with installation hiccups and development problems, etc.

  • Links to all GitHub pull requests to the Submitty organization and their current status (submitted, reviewed, revised, approved, merged). NOTE: significant/large pull requests take more time to review for completeness and correctness. It's ok if your work is not merged before the GSoC application deadline.

  • Links to all Submitty PRs authored by other developers that you have reviewed. NOTE: reviews should be thoughtful and substantive with specific details about how the code was manually tested and whether any improvements to the code for readability/maintainability are suggested. PR reviews that simply comment "LGTM" are not as helpful.

See also: How to Apply to Submitty for Google Summer of Code 2026