Skip to content

Commit 2641d17

Browse files
bmcutlerbmcutler
authored
[Refactor:Developer] March 2025 Edit (#666)
Co-authored-by: Barb Cutler <Barb Cutler>
1 parent 1dc8fc2 commit 2641d17

File tree

3 files changed

+108
-112
lines changed

3 files changed

+108
-112
lines changed

‎_docs/developer/google_summer_of_code/GSoC_application.md

+95
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: GSoC Application
3+
category: Developer > Google Summer of Code
4+
---
5+
6+
## How to Apply to Submitty for Google Summer of Code 20XX
7+
8+
1. Read the GSOC information for contributors to confirm your eligibility:
9+
10+
* [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)
11+
12+
* [https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation](https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation)
13+
14+
2. Read our [Suggestions for New Developers](/developer).
15+
16+
3. Follow the developer instructions to
17+
[install the Submitty system](/developer/getting_started/vm_install_using_vagrant)
18+
in a virtual machine on your computer.
19+
20+
4. Review our project ideas list:
21+
[https://submitty.org/developer/getting_started/project_ideas](/developer/getting_started/project_ideas)
22+
23+
5. Join our Zulip server to ask questions and meet other new developers:
24+
[https://submitty.org/contact](/contact)
25+
26+
Ask specific technical questions about the Submitty system and open
27+
issues and help answer technical questions from other new developers if
28+
you think you can help. Your engagement in the community discussion
29+
during the application period (both asking and answering questions) will
30+
31+
32+
be taken into account as we evaluate your application.
33+
34+
NOTE: The Submitty mentors for Google Summer of Code are on our
35+
Zulip server. Please communicate through the public streams and
36+
do not direct message (DM) / private message any mentors.
37+
Mentors will generally not respond to private messages.
38+
39+
New developers should start with an issue labeled "Good First Issue".
40+
To understand the existing functionality/bug, reproduce and test this feature on your development VM.
41+
Inspect the relevant system files and database contents.
42+
43+
44+
NOTE: More recent issues in the Submitty Github database tagged "Awaiting Triage"
45+
have not yet been reviewed by the Submitty Project administrators.
46+
These details of these bug reports and feature requests may need editing and revision
47+
to confirm they meet with the long-term needs and goals of the Submitty project.
48+
Before starting to work on one of these issues, we recommend you check with the
49+
project team by creating a new discussion thread about the issue on our [Zulip server](/contact).
50+
51+
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+
54+
8. Help test and review [open pull requests](https://github.com/Submitty/Submitty/pulls) contributed by other developers.
55+
[https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request)
56+
57+
NOTE: We always have a large number of _work-in-progress_ pull
58+
requests from both new and experienced developers. Prospective
59+
developers with any level of experience are welcome and needed to
60+
help review these PRs. Contributing to the review process is
61+
beneficial to everyone.
62+
63+
9. Begin work on your GSoC Project application. We recommend
64+
prospective contributors focus on one of our suggested projects
65+
from the [project ideas](/developer/getting_started/project_ideas)
66+
list. Successful applicants will be able to expand and enhance the
67+
proposed project idea with a timeline of design and implementation
68+
milestones, and will demonstrate curiosity and motivation for the
69+
topic.
70+
71+
10. Download and complete the
72+
[Submitty GSoC Applicant Template](/developer/google_summer_of_code/applicant_template).
73+
74+
You will document your skills, relevant coursework, non-course experience, and future
75+
career goals that qualify you to work on this project.
76+
77+
The template will also ask for your approximate schedule for the
78+
summer: start date, end date, and number of hours of work per week.
79+
And a description of any classes, employment, or other time
80+
commitments during that time period.
81+
82+
Most importantly, you will summarize your engagement with the
83+
Submitty project team during the application period. This includes
84+
participation in public discussions on our [Zulip server](/contact),
85+
authoring of new pull requests (both in progress and merged), and
86+
detailed and constructive reviews of PRs from other developers.
87+
88+
89+
11. The application window for Google Summer of Code closes on April XXth, 20XX at 18:00 UTC.
90+
Please carefully read all of the program requirements.
91+
92+
* [Google Summer of Code 20XX Timeline](https://developers.google.com/open-source/gsoc/timeline)
93+
94+
* [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)
95+

‎_docs/developer/google_summer_of_code/applicant_template.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,13 @@ title: Applicant Template
33
category: Developer > Google Summer of Code
44
---
55

6-
**NOTE: The 2025 Submitty GSoC Template will be available for download
7-
when Google announces the organizations accepted for Google Summer
8-
of Code 2025.**
6+
[comment]: <> **NOTE: The 20XX Submitty GSoC Template will be available for download
7+
[comment]: <> when Google announces the organizations accepted for Google Summer
8+
[comment]: <> of Code 20XX.**
99

1010
To ensure that the Submitty Org Admins and Mentors have all of the
1111
information about your ideas, project plan, and availability for
12-
Google Summer of Code 2025, we ask you to use the Submitty Applicant
12+
Google Summer of Code 20XX, we ask you to use the Submitty Applicant
1313
Template.
1414

1515
The template will include:

‎_docs/developer/google_summer_of_code/index.md

+9-108
Original file line numberDiff line numberDiff line change
@@ -5,125 +5,26 @@ redirect_from:
55
- /developer/google_summer_of_code
66
---
77

8-
Submitty has applied for acceptance to
9-
[Google
10-
Summer of Code (GSoC) 2025](https://summerofcode.withgoogle.com/).
11-
Project reports from participants in previous summers are linked
12-
below.
13-
8+
[comment]: <> Submitty has applied for acceptance to
9+
[comment]: <> [Google Summer of Code (GSoC) 20XX](https://summerofcode.withgoogle.com/).
10+
[comment]: <> Project reports from participants in previous summers are linked
11+
[comment]: <> below.
1412

1513
[comment]: <> We are thrilled to announce that Submitty has been accepted to [Google
16-
[comment]: <> Summer of Code (GSoC) 2024](https://summerofcode.withgoogle.com/).
14+
[comment]: <> Summer of Code (GSoC) 20XX](https://summerofcode.withgoogle.com/).
1715
[comment]: <> Project reports from participants in previous summers are linked
1816
[comment]: <> below.
1917

20-
21-
2218
<center>
2319
<a href="https://summerofcode.withgoogle.com"><img src="/images/GSoC-Vertical.png" width="250px"></a>
2420
</center>
2521

26-
[comment]: <> _NOTE: The organizations selected for Summer 2024 Google Summer of
27-
28-
_NOTE: The organizations selected for Summer 2025 Google Summer of
29-
Code will be announced in late February. The instructions below
30-
are from 2024 and will be updated if Submitty is accepted!_
31-
32-
33-
## How to Apply to Submitty for Google Summer of Code 2025
34-
35-
1. Read the GSOC information for contributors to confirm your eligibility:
36-
37-
* [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)
38-
39-
* [https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation](https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation)
40-
41-
* [https://opensource.googleblog.com/2024/02/mentor-organizations-announced-for-google-summer-of-code-2024.html](https://opensource.googleblog.com/2024/02/mentor-organizations-announced-for-google-summer-of-code-2024.html)
42-
43-
2. Read our [Suggestions for New Developers](/developer).
44-
45-
3. Follow the developer instructions to
46-
[install the Submitty system](/developer/getting_started/vm_install_using_vagrant)
47-
in a virtual machine on your computer.
48-
49-
4. Review our project ideas list:
50-
[https://submitty.org/developer/getting_started/project_ideas](/developer/getting_started/project_ideas)
51-
52-
5. Join our Zulip server to ask questions and meet other new developers:
53-
[https://submitty.org/contact](/contact)
54-
55-
Ask specific technical questions about the Submitty system and open
56-
issues and help answer technical questions from other new developers if
57-
you think you can help. Your engagement in the community discussion
58-
during the application period (both asking and answering questions) will
59-
be taken into account as we evaluate your application.
60-
61-
_NOTE: The Submitty mentors for Google Summer of Code are on our
62-
Zulip server. Please communicate through the public streams and
63-
do not direct message (DM) / private message any mentors.
64-
Mentors will generally not respond to private messages._
65-
66-
6. Search the Submitty Github for related open issues (bugs and feature requests):
67-
[https://github.com/Submitty/Submitty/issues](https://github.com/Submitty/Submitty/issues)
68-
69-
New developers should start with an issue labeled "Good First
70-
Issue". To understand the existing functionality/bug, reproduce and
71-
test this feature on your development VM. Inspect the relevant
72-
system files and database contents.
73-
74-
_NOTE: More recent issues in the Submitty Github database tagged "Awaiting Triage"
75-
have not yet been reviewed by the Submitty Project administrators.
76-
These details of these bug reports and feature requests may need editing and revision
77-
to confirm they meet with the long-term needs and goals of the Submitty project.
78-
Before starting to work on one of these issues, we recommend you check with the
79-
project team by creating a new discussion thread about the issue on our [Zulip server](/contact)._
80-
81-
7. Submit a pull request to solve an open issue.
82-
[https://submitty.org/developer/getting_started/make_a_pull_request](/developer/getting_started/make_a_pull_request)
83-
84-
8. Help test and review [open pull requests](https://github.com/Submitty/Submitty/pulls) contributed by other developers.
85-
[https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request)
86-
87-
NOTE: We always have a large number of _work-in-progress_ pull
88-
requests from both new and experienced developers. Prospective
89-
developers with any level of experience are welcome and needed to
90-
help review these PRs. Contributing to the review process is
91-
beneficial to everyone.
92-
93-
9. Begin work on your GSoC Project application. We recommend
94-
prospective contributors focus on one of our suggested projects
95-
from the [project ideas](/developer/getting_started/project_ideas)
96-
list. Successful applicants will be able to expand and enhance the
97-
proposed project idea with a timeline of design and implementation
98-
milestones, and will demonstrate curiosity and motivation for the
99-
topic.
100-
101-
10. Download and complete the
102-
[Submitty GSoC Applicant Template](/developer/google_summer_of_code/applicant_template).
103-
104-
You will document your skills, relevant coursework, non-course experience, and future
105-
career goals that qualify you to work on this project.
106-
107-
The template will also ask for your approximate schedule for the
108-
summer: start date, end date, and number of hours of work per week.
109-
And a description of any classes, employment, or other time
110-
commitments during that time period.
111-
112-
Most importantly, you will summarize your engagement with the
113-
Submitty project team during the application period. This includes
114-
participation in public discussions on our [Zulip server](/contact),
115-
authoring of new pull requests (both in progress and merged), and
116-
detailed and constructive reviews of PRs from other developers.
117-
118-
119-
11. The application window for Google Summer of Code closes on April 8th, 2025 at 18:00 UTC.
120-
Please carefully read all of the program requirements.
121-
122-
* [Google Summer of Code 2025 Timeline](https://developers.google.com/open-source/gsoc/timeline)
22+
[comment]: <> _NOTE: The organizations selected for Summer 20XX Google Summer of
23+
[comment]: <> Code will be announced in late February. The instructions below
24+
[comment]: <> are from 20XX and will be updated if Submitty is accepted!_
12325

124-
* [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)
12526

126-
&nbsp;
27+
[comment]: <> [Google Summer of Code Application](/developer/google_summer_of_code/GSoC_application)
12728

12829

12930
## Google Summer of Code 2024

0 commit comments

Comments
 (0)