From 41b03873c98ee1f1da8783122d1ea9cc6f26a1d5 Mon Sep 17 00:00:00 2001 From: Barb Cutler Date: Sat, 1 Mar 2025 17:54:35 -0500 Subject: [PATCH] google summer of code edit --- .../google_summer_of_code/GSoC_application.md | 95 ++++++++++++++ .../applicant_template.md | 8 +- .../developer/google_summer_of_code/index.md | 117 ++---------------- 3 files changed, 108 insertions(+), 112 deletions(-) create mode 100644 _docs/developer/google_summer_of_code/GSoC_application.md diff --git a/_docs/developer/google_summer_of_code/GSoC_application.md b/_docs/developer/google_summer_of_code/GSoC_application.md new file mode 100644 index 00000000..b2f8efbc --- /dev/null +++ b/_docs/developer/google_summer_of_code/GSoC_application.md @@ -0,0 +1,95 @@ +--- +title: GSoC Application +category: Developer > Google Summer of Code +--- + +## How to Apply to Submitty for Google Summer of Code 20XX + +1. Read the GSOC information for contributors to confirm your eligibility: + + * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) + + * [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) + +2. Read our [Suggestions for New Developers](/developer). + +3. Follow the developer instructions to + [install the Submitty system](/developer/getting_started/vm_install_using_vagrant) + in a virtual machine on your computer. + +4. Review our project ideas list: + [https://submitty.org/developer/getting_started/project_ideas](/developer/getting_started/project_ideas) + +5. Join our Zulip server to ask questions and meet other new developers: + [https://submitty.org/contact](/contact) + + Ask specific technical questions about the Submitty system and open + issues and help answer technical questions from other new developers if + you think you can help. Your engagement in the community discussion + during the application period (both asking and answering questions) will + + + be taken into account as we evaluate your application. + + NOTE: The Submitty mentors for Google Summer of Code are on our + Zulip server. Please communicate through the public streams and + do not direct message (DM) / private message any mentors. + Mentors will generally not respond to private messages. + + New developers should start with an issue labeled "Good First Issue". + To understand the existing functionality/bug, reproduce and test this feature on your development VM. + Inspect the relevant system files and database contents. + + + NOTE: More recent issues in the Submitty Github database tagged "Awaiting Triage" + have not yet been reviewed by the Submitty Project administrators. + These details of these bug reports and feature requests may need editing and revision + to confirm they meet with the long-term needs and goals of the Submitty project. + Before starting to work on one of these issues, we recommend you check with the + project team by creating a new discussion thread about the issue on our [Zulip server](/contact). + +7. Submit a pull request to solve an open issue. + [https://submitty.org/developer/getting_started/make_a_pull_request](/developer/getting_started/make_a_pull_request) + +8. Help test and review [open pull requests](https://github.com/Submitty/Submitty/pulls) contributed by other developers. + [https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request) + + NOTE: We always have a large number of _work-in-progress_ pull + requests from both new and experienced developers. Prospective + developers with any level of experience are welcome and needed to + help review these PRs. Contributing to the review process is + beneficial to everyone. + +9. Begin work on your GSoC Project application. We recommend + prospective contributors focus on one of our suggested projects + from the [project ideas](/developer/getting_started/project_ideas) + list. Successful applicants will be able to expand and enhance the + proposed project idea with a timeline of design and implementation + milestones, and will demonstrate curiosity and motivation for the + topic. + +10. Download and complete the + [Submitty GSoC Applicant Template](/developer/google_summer_of_code/applicant_template). + + You will document your skills, relevant coursework, non-course experience, and future + career goals that qualify you to work on this project. + + The template will also ask for your approximate schedule for the + summer: start date, end date, and number of hours of work per week. + And a description of any classes, employment, or other time + commitments during that time period. + + Most importantly, you will summarize your engagement with the + Submitty project team during the application period. This includes + participation in public discussions on our [Zulip server](/contact), + authoring of new pull requests (both in progress and merged), and + detailed and constructive reviews of PRs from other developers. + + +11. The application window for Google Summer of Code closes on April XXth, 20XX at 18:00 UTC. + Please carefully read all of the program requirements. + + * [Google Summer of Code 20XX Timeline](https://developers.google.com/open-source/gsoc/timeline) + + * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) + diff --git a/_docs/developer/google_summer_of_code/applicant_template.md b/_docs/developer/google_summer_of_code/applicant_template.md index 702f0789..e752710f 100644 --- a/_docs/developer/google_summer_of_code/applicant_template.md +++ b/_docs/developer/google_summer_of_code/applicant_template.md @@ -3,13 +3,13 @@ title: Applicant Template category: Developer > Google Summer of Code --- -**NOTE: The 2025 Submitty GSoC Template will be available for download - when Google announces the organizations accepted for Google Summer - of Code 2025.** +[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.** 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 2025, we ask you to use the Submitty Applicant +Google Summer of Code 20XX, we ask you to use the Submitty Applicant Template. The template will include: diff --git a/_docs/developer/google_summer_of_code/index.md b/_docs/developer/google_summer_of_code/index.md index 46294a0c..eb979bf2 100644 --- a/_docs/developer/google_summer_of_code/index.md +++ b/_docs/developer/google_summer_of_code/index.md @@ -5,125 +5,26 @@ redirect_from: - /developer/google_summer_of_code --- -Submitty has applied for acceptance to -[Google -Summer of Code (GSoC) 2025](https://summerofcode.withgoogle.com/). -Project reports from participants in previous summers are linked -below. - +[comment]: <> Submitty has applied for acceptance to +[comment]: <> [Google Summer of Code (GSoC) 20XX](https://summerofcode.withgoogle.com/). +[comment]: <> Project reports from participants in previous summers are linked +[comment]: <> below. [comment]: <> We are thrilled to announce that Submitty has been accepted to [Google -[comment]: <> Summer of Code (GSoC) 2024](https://summerofcode.withgoogle.com/). +[comment]: <> Summer of Code (GSoC) 20XX](https://summerofcode.withgoogle.com/). [comment]: <> Project reports from participants in previous summers are linked [comment]: <> below. - -
-[comment]: <> _NOTE: The organizations selected for Summer 2024 Google Summer of - -_NOTE: The organizations selected for Summer 2025 Google Summer of -Code will be announced in late February. The instructions below -are from 2024 and will be updated if Submitty is accepted!_ - - -## How to Apply to Submitty for Google Summer of Code 2025 - -1. Read the GSOC information for contributors to confirm your eligibility: - - * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) - - * [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) - - * [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) - -2. Read our [Suggestions for New Developers](/developer). - -3. Follow the developer instructions to - [install the Submitty system](/developer/getting_started/vm_install_using_vagrant) - in a virtual machine on your computer. - -4. Review our project ideas list: - [https://submitty.org/developer/getting_started/project_ideas](/developer/getting_started/project_ideas) - -5. Join our Zulip server to ask questions and meet other new developers: - [https://submitty.org/contact](/contact) - - Ask specific technical questions about the Submitty system and open - issues and help answer technical questions from other new developers if - you think you can help. Your engagement in the community discussion - during the application period (both asking and answering questions) will - be taken into account as we evaluate your application. - - _NOTE: The Submitty mentors for Google Summer of Code are on our - Zulip server. Please communicate through the public streams and - do not direct message (DM) / private message any mentors. - Mentors will generally not respond to private messages._ - -6. Search the Submitty Github for related open issues (bugs and feature requests): - [https://github.com/Submitty/Submitty/issues](https://github.com/Submitty/Submitty/issues) - - New developers should start with an issue labeled "Good First - Issue". To understand the existing functionality/bug, reproduce and - test this feature on your development VM. Inspect the relevant - system files and database contents. - - _NOTE: More recent issues in the Submitty Github database tagged "Awaiting Triage" - have not yet been reviewed by the Submitty Project administrators. - These details of these bug reports and feature requests may need editing and revision - to confirm they meet with the long-term needs and goals of the Submitty project. - Before starting to work on one of these issues, we recommend you check with the - project team by creating a new discussion thread about the issue on our [Zulip server](/contact)._ - -7. Submit a pull request to solve an open issue. - [https://submitty.org/developer/getting_started/make_a_pull_request](/developer/getting_started/make_a_pull_request) - -8. Help test and review [open pull requests](https://github.com/Submitty/Submitty/pulls) contributed by other developers. - [https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request) - - NOTE: We always have a large number of _work-in-progress_ pull - requests from both new and experienced developers. Prospective - developers with any level of experience are welcome and needed to - help review these PRs. Contributing to the review process is - beneficial to everyone. - -9. Begin work on your GSoC Project application. We recommend - prospective contributors focus on one of our suggested projects - from the [project ideas](/developer/getting_started/project_ideas) - list. Successful applicants will be able to expand and enhance the - proposed project idea with a timeline of design and implementation - milestones, and will demonstrate curiosity and motivation for the - topic. - -10. Download and complete the - [Submitty GSoC Applicant Template](/developer/google_summer_of_code/applicant_template). - - You will document your skills, relevant coursework, non-course experience, and future - career goals that qualify you to work on this project. - - The template will also ask for your approximate schedule for the - summer: start date, end date, and number of hours of work per week. - And a description of any classes, employment, or other time - commitments during that time period. - - Most importantly, you will summarize your engagement with the - Submitty project team during the application period. This includes - participation in public discussions on our [Zulip server](/contact), - authoring of new pull requests (both in progress and merged), and - detailed and constructive reviews of PRs from other developers. - - -11. The application window for Google Summer of Code closes on April 8th, 2025 at 18:00 UTC. - Please carefully read all of the program requirements. - - * [Google Summer of Code 2025 Timeline](https://developers.google.com/open-source/gsoc/timeline) +[comment]: <> _NOTE: The organizations selected for Summer 20XX Google Summer of +[comment]: <> Code will be announced in late February. The instructions below +[comment]: <> are from 20XX and will be updated if Submitty is accepted!_ - * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) -  +[comment]: <> [Google Summer of Code Application](/developer/google_summer_of_code/GSoC_application) ## Google Summer of Code 2024