Update 00-what_is_google_summer_of_code.md

stats updates

pages/mentor/00-what_is_google_summer_of_code.md

@@ -10,7 +10,7 @@ Google Summer of Code (GSoC) is a global, online program that brings new contrib
 
 Accepted GSoC Contributors gain exposure to real-world software development while having their mentor(s) ready to help integrate them into the community and help them become stronger developers. Best of all, more source code is created and released for the use and benefit of all; all code produced as part of the program is released under an open source license. The fact that you get to write code that people from all over the world can use - how cool is that!
 
-Since 2005, GSoC has brought together 35,000 students and mentors from over 133 countries worldwide. As of November 2023, over 800 open source projects, from areas as diverse as operating systems and community services, have participated as mentoring organizations for the program. Successful students have widely reported that their participation in GSoC made them more attractive to potential employers and that the program has helped greatly when embarking on their technical careers. Many past students continue to be involved in GSoC by becoming mentors themselves and helping new contributors learn about the exciting things their community is working on and the satisfaction that comes with being a part of a community of dedicated developers in open source.
+Since 2005, GSoC has brought together 41,000 new contributors to open source and mentors from over 138 countries worldwide. As of January 2025, over 1,000 open source projects, from areas as diverse as operating systems and community services, have participated as mentoring organizations for the program. Successful students have widely reported that their participation in GSoC made them more attractive to potential employers and that the program has helped greatly when embarking on their technical careers. Many past GSoC contributors continue to be involved in GSoC by becoming mentors themselves and helping new contributors learn about the exciting things their community is working on and the satisfaction that comes with being a part of a community of dedicated developers in open source.
 
 ## Goals of the Program
 
@@ -23,9 +23,9 @@ The GSoC program has several goals:
 
 ## A Brief History of Google Summer of Code
 
-Google Summer of Code began in 2005 as a complex experiment with a simple goal: helping students find work related to their academic pursuits during their school holidays. In GSoC’s first year, 40 projects and 400 students participated. By the conclusion of the 19th Google Summer of Code in 2023, over 20,000 students/GSoC contributors have been accepted into the program. Best of all, most of the organizations participating over the past 18 years reported that the program helped them find new community members and active committers.
+Google Summer of Code began in 2005 as a complex experiment with a simple goal: helping students find work related to their academic pursuits during their school holidays. In GSoC’s first year, 40 projects and 400 students participated. By the conclusion of the 20th Google Summer of Code in 2024, over 21,000 students/GSoC contributors have been accepted into the program. Best of all, most of the organizations participating over the past 20 years reported that the program helped them find new community members and active committers.
 
-GSoC has grown immensely over the last 18 years and in the process helped participants learn about real world software development while working on exciting open source projects.
+GSoC has grown immensely over the last 20 years and in the process helped participants learn about real world software development while working on exciting open source projects.
 
 You can take a look at the appendix if you’re interested in a more extensive history of the program.
 
@@ -53,7 +53,7 @@ All of the program rules are enumerated in the GSoC Program Rules and Term docum
 
 **Organization Applications**: The GSoC program is announced each year on the [Google Open Source Blog](https://opensource.googleblog.com/) among other places, and this announcement provides application deadlines for projects. Each organization must apply to participate. Organizations usually have about 3 weeks to apply for the program. Google's program administrators then select which organizations will participate in that year's Google Summer of Code.
 
-**GSoC contributor Applications**: Potential GSoC contributors are encouraged to begin talking to the participating organizations as soon as the list of accepted organizations is published. Prior to the opening of applications, it is important to take some time to talk to potential applicants. This helps them refine their ideas so that they will produce a better quality proposal. Each organization is asked to provide a proposal template, but the best applications go far beyond the template and an organization's ideas list. Applicants are given about 2 weeks to complete their applications.
+**GSoC Contributor Applications**: Potential GSoC contributors are encouraged to begin talking to the participating organizations as soon as the list of accepted organizations is published. Prior to the opening of applications, it is important to take some time to talk to potential applicants. This helps them refine their ideas so that they will produce a better quality proposal. Each organization is asked to provide a proposal template, but the best applications go far beyond the template and an organization's ideas list. Applicants are given about 2 weeks to complete their applications.
 
 Following the GSoC contributor application deadline, organizations begin reviewing the proposals they received. During the review phase, organizations maintain an open dialogue with their applicants. This may involve clarifying questions in regards to the final proposals to ensure applicants and organizations have the same understanding of the proposal. It is important to note an applicant's proposal can't be altered after the final submission deadline, and mentor organizations should not attempt to do so during the review period.
 
@@ -63,7 +63,7 @@ Sometimes an applicant has proposals accepted by more than one organization. Goo
 
 **Community Bonding Period**: Before GSoC contributors are expected to start working, there is a three week period built into the program to allow them to get up to speed without the pressure to execute on their proposals. During this time, GSoC contributors are expected to get to know their project communities and participate in project discussion. During this time, GSoC contributors should also set up their development environments, learn how their project's source control works, refine their project plans, read any necessary documentation, and otherwise prepare to complete their project proposals. Mentors should spend this time helping their GSoC contributors understand which resources will be most useful to them, introducing them to the members of the community who will be most helpful with their projects, and generally acculturating them.
 
-For 2022 there is increased flexibility in the timeline for projects. When proposals are submitted they will be selected as a medium (175 hour) or large (350 hour) project. The standard coding period will be 12 weeks. However, GSoC contributors can request (in their proposal) to have a longer coding period to complete their project as they know they may have various other commitments or certain weeks when they will not be able to commit as much time to their GSoC project (up to a 22 week coding period is allowed). This opens it up for the GSoC contributors and mentor to decide together how they want to break up the project. Some folks may choose to stick to a certain number of hours a week schedule with their GSoC contributors, others may factor in a couple of breaks during the program (for GSoC contributor and mentor). This also makes it a lot easier for GSoC contributors with finals or other commitments (weddings, moving across the country, etc.) to adjust their schedules. But the most important thing to remember is that both the GSoC contributor and mentor should agree on a schedule and sign off on it early on during the community bonding period so there is no confusion later on.
+Since 2022 there is increased flexibility in the timeline for projects. When proposals are submitted they will be selected as a small (90 hour), medium (175 hour) or large (350 hour) project. The standard coding period will be 12 weeks for medium and large projects and 8 weeks for small projects. However, GSoC contributors can request (in their proposal) to have a longer coding period to complete their project as they know they may have various other commitments or certain weeks when they will not be able to commit as much time to their GSoC project (up to a 22 week coding period is allowed). This opens it up for the GSoC contributors and mentor to decide together how they want to break up the project. Some folks may choose to stick to a certain number of hours a week schedule with their GSoC contributors, others may factor in a couple of breaks during the program (for GSoC contributor and mentor). This also makes it a lot easier for GSoC contributors with finals or other commitments (weddings, moving across the country, etc.) to adjust their schedules. But the most important thing to remember is that both the GSoC contributor and mentor should agree on a schedule and sign off on it early on during the community bonding period so there is no confusion later on.
 
 **Start of Coding**: Start of coding is the date the program officially begins; GSoC contributors are expected to start executing on their project proposals. At this point, GSoC contributors should begin regular check-ins and regular patch submissions.