Google Summer of Code 2025 - Revision history

Cvvergara: Using discourse category

2025-05-15T18:26:24Z

Using discourse category

Krashish8 at 05:26, 14 February 2025

2025-02-14T05:26:58Z

Krashish8 at 05:26, 14 February 2025

2025-02-14T05:26:30Z

Krashish8 at 05:26, 14 February 2025

2025-02-14T05:26:13Z

Rahulworld: updated

2025-02-10T17:53:02Z

updated

Rahulworld: Created wiki page

2025-02-10T17:51:39Z

Created wiki page

New page

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font>
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2025 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2025 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code Administrative]] page.
* Final Results: [[Google Summer of Code 2025 Results]]

== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

See also older Google Summer of Code
[[Google Summer of Code 2023|2024]]
[[Google Summer of Code 2023|2023]],
[[Google Summer of Code 2022|2022]],
[[Google Summer of Code 2021|2021]],
[[Google Summer of Code 2020|2020]],
[[Google Summer of Code 2019|2019]],
[[Google Summer of Code 2018|2018]],
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

@@ Line 12: / Line 12: @@
 == Recent Modifications in GSoC (Must Read) ==
-* The program is open to all the students who are 18 years and older AND to the beginners in open source development, who might not be
+* The program is open to all the students who are 18 years and older AND to the beginners in open source development, who might not be university students but are 18 years and older. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.
 * GSoC Contributors will be able to choose from multiple-size projects: medium at ~175 hours, large at ~350 hours and small at ~90 hours. This is to remove the barrier of available time that many potential contributors have and open the program to people who want to learn about open source development but can’t dedicate all or even half of their summer to the program.

@@ Line 39: / Line 39: @@
 [[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.
-You can subscribe to the OSGeo Google Summer of Code Mailing List here:
+You can subscribe to the OSGeo Google Summer of Code Category here:
-: http://lists.osgeo.org/mailman/listinfo/soc
+: https://discourse.osgeo.org/c/initiatives/gsoc/42
 [[Category:Google Summer of Code]]

@@ Line 21: / Line 21: @@
 See also older Google Summer of Code
-[[Google Summer of Code 2023|2024]]
+[[Google Summer of Code 2024|2024]],
 [[Google Summer of Code 2023|2023]],
 [[Google Summer of Code 2022|2022]],

@@ Line 8: / Line 8: @@
 * If you are a '''student''', please visit our [[Google Summer of Code 2025 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
 * If you are a '''mentor''' you should go to our [[Google Summer of Code Administrative]] page.
-== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==
+== Recent Modifications in GSoC (Must Read) ==
-* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.
+* The program is open to all the students who are 18 years and older AND to the beginners in open source development, who might not be
-* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.
+* GSoC Contributors will be able to choose from multiple-size projects: medium at ~175 hours, large at ~350 hours and small at ~90 hours. This is to remove the barrier of available time that many potential contributors have and open the program to people who want to learn about open source development but can’t dedicate all or even half of their summer to the program.
-* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.
+* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. This would make it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.