Skip to content

Commit e346c5e

Browse files
authored
[Documentation] update to 2026 application instructions (#727)
draft of 2026 GSOC contributor application template Co-authored-by: Barb Cutler <Barb Cutler>
1 parent 8aac7b8 commit e346c5e

File tree

3 files changed

+48
-15
lines changed

3 files changed

+48
-15
lines changed

_docs/developer/google_summer_of_code/GSoC_application.md

Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,17 @@ title: GSoC Application
33
category: Developer > Google Summer of Code
44
---
55

6-
## How to Apply to Submitty for Google Summer of Code 20XX
6+
7+
---
8+
9+
_Submitty has applied for acceptance to [Google Summer of Code (GSoC) 2026](https://summerofcode.withgoogle.com/).
10+
The organizations selected for Summer 2026 Google Summer of Code will be announced in
11+
[late February](https://developers.google.com/open-source/gsoc/timeline)._
12+
13+
---
14+
15+
16+
## How to Apply to Submitty for Google Summer of Code 2026
717

818
1. Read the GSOC information for contributors to confirm your eligibility:
919

@@ -27,19 +37,20 @@ category: Developer > Google Summer of Code
2737
issues and help answer technical questions from other new developers if
2838
you think you can help. Your engagement in the community discussion
2939
during the application period (both asking and answering questions) will
30-
31-
3240
be taken into account as we evaluate your application.
3341

3442
NOTE: The Submitty mentors for Google Summer of Code are on our
35-
Zulip server. Please communicate through the public streams and
43+
Zulip server. Please communicate through the public channels/streams and
3644
do not direct message (DM) / private message any mentors.
3745
Mentors will generally not respond to private messages.
3846

39-
New developers should start with an issue labeled "Good First Issue".
47+
6. New developers should start with an issue labeled "Good First Issue".
4048
To understand the existing functionality/bug, reproduce and test this feature on your development VM.
4149
Inspect the relevant system files and database contents.
42-
50+
Carefully read through all messages posted under the issue, and read through
51+
other issues or pull requests that are linked to the issue.
52+
New developers can also get up to speed by reviewing and testing the pull requests
53+
of other developers that aim to solve and close issues labeled "Good First Issue".
4354

4455
NOTE: More recent issues in the Submitty Github database tagged "Awaiting Triage"
4556
have not yet been reviewed by the Submitty Project administrators.
@@ -49,8 +60,8 @@ category: Developer > Google Summer of Code
4960
project team by creating a new discussion thread about the issue on our [Zulip server](/contact).
5061

5162
7. Submit a pull request to solve an open issue.
52-
[https://submitty.org/developer/getting_started/make_a_pull_request](/developer/getting_started/make_a_pull_request)
53-
63+
[https://submitty.org/developer/getting_started/make_a_pull_request](/developer/getting_started/make_a_pull_request)
64+
5465
8. Help test and review [open pull requests](https://github.com/Submitty/Submitty/pulls) contributed by other developers.
5566
[https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request)
5667

@@ -60,6 +71,8 @@ category: Developer > Google Summer of Code
6071
help review these PRs. Contributing to the review process is
6172
beneficial to everyone.
6273

74+
[Submitty Open Pull Request Project Board](https://github.com/orgs/Submitty/projects/1)
75+
6376
9. Begin work on your GSoC Project application. We recommend
6477
prospective contributors focus on one of our suggested projects
6578
from the [project ideas](/developer/getting_started/project_ideas)
@@ -85,11 +98,10 @@ category: Developer > Google Summer of Code
8598
authoring of new pull requests (both in progress and merged), and
8699
detailed and constructive reviews of PRs from other developers.
87100

88-
89-
11. The application window for Google Summer of Code closes on April XXth, 20XX at 18:00 UTC.
101+
11. The application window for Google Summer of Code closes on March 31st, 2026 at 18:00 UTC.
90102
Please carefully read all of the program requirements.
91103

92-
* [Google Summer of Code 20XX Timeline](https://developers.google.com/open-source/gsoc/timeline)
104+
* [Google Summer of Code 2026 Timeline](https://developers.google.com/open-source/gsoc/timeline)
93105

94106
* [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)
95107

_docs/developer/google_summer_of_code/applicant_template.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,23 @@ title: Applicant Template
33
category: Developer > Google Summer of Code
44
---
55

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

11+
12+
13+
_Submitty has applied for acceptance to [Google Summer of Code (GSoC) 2026](https://summerofcode.withgoogle.com/).
14+
The organizations selected for Summer 2026 Google Summer of Code will be announced in
15+
[late February](https://developers.google.com/open-source/gsoc/timeline)._
16+
17+
---
18+
19+
1020
To ensure that the Submitty Org Admins and Mentors have all of the
1121
information about your ideas, project plan, and availability for
12-
Google Summer of Code 20XX, we ask you to use the Submitty Applicant
22+
Google Summer of Code 2026, we ask you to use the Submitty Applicant
1323
Template.
1424

1525
The template will include:
@@ -36,6 +46,13 @@ The template will include:
3646
not merged before the GSoC application deadline._
3747

3848
* Links to all Submitty PRs authored by other developers that you have
39-
reviewed. _NOTE: reviews should be thoughtful and substantive. PR
40-
reviews that simply comment "LGTM" are not as helpful._
49+
reviewed. _NOTE: reviews should be thoughtful and substantive with
50+
specific details about how the code was manually tested and whether
51+
any improvements to the code for readability/maintainability are
52+
suggested. PR reviews that simply comment "LGTM" are not as
53+
helpful._
54+
55+
56+
See also: [How to Apply to Submitty for Google Summer of Code 2026](/developer/google_summer_of_code/GSoC_application)
57+
4158

_docs/developer/google_summer_of_code/index.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ redirect_from:
2424
[comment]: <> are from 20XX and will be updated if Submitty is accepted!_
2525

2626

27-
[comment]: <> [Google Summer of Code Application](/developer/google_summer_of_code/GSoC_application)
27+
2828

2929

3030
----
@@ -35,6 +35,10 @@ Project reports from participants in previous summers are linked below. The org
3535
2026 Google Summer of Code will be announced in
3636
[late February](https://developers.google.com/open-source/gsoc/timeline)._
3737

38+
39+
_[How to Apply to Submitty for Google Summer of Code 2026](/developer/google_summer_of_code/GSoC_application)_
40+
41+
3842
---
3943

4044

0 commit comments

Comments
 (0)