Google Summer of Code 2025 Ideas - Revision history

Maxi: /* The ideas pages */

2025-03-02T20:11:28Z

The ideas pages

Krashish8 at 05:31, 14 February 2025

2025-02-14T05:31:10Z

RajatShinde: /* OSGeo Foundation graduated project */

2025-02-11T01:57:15Z

OSGeo Foundation graduated project

Cvvergara: Using OSGeo website link

2025-02-10T18:06:30Z

Using OSGeo website link

Cvvergara: Rephrasing and fixing link

2025-02-10T18:05:11Z

Rephrasing and fixing link

Cvvergara: unhiding grassgis

2025-02-10T17:50:48Z

unhiding grassgis

Cvvergara: /* OSGeo Foundation Incubation project */

2025-02-10T17:48:02Z

OSGeo Foundation Incubation project

Cvvergara: /* OSGeo Foundation graduated project */

2025-02-10T17:47:19Z

OSGeo Foundation graduated project

Rahulworld at 10:53, 2 February 2025

2025-02-02T10:53:14Z

Rahulworld at 10:52, 2 February 2025

2025-02-02T10:52:44Z

@@ Line 49: / Line 49: @@
 [[Image:ZOO-Project-mini.png|60px|right]]
 * [https://github.com/ZOO-Project/ZOO-Project/wiki/Google%E2%80%90Summer%E2%80%90of%E2%80%90Code%E2%80%902025%E2%80%90Project%E2%80%90Ideas '''ZOO-Project''' Ideas]:  The [https://zoo-project.org/ ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions and is able to handle services implemented in various programming languages.
 <!--

@@ Line 7: / Line 7: @@
 * Back to the main OSGeo [[Google Summer of Code 2025]] wiki page.
-* See also ideas from [[Google Summer of Code 2023 Ideas|2024]], [[Google Summer of Code 2023 Ideas|2023]], [[Google Summer of Code 2022 Ideas|2022]], [[Google Summer of Code 2021 Ideas|2021]],[[Google Summer of Code 2020 Ideas|2020]], [[Google Summer of Code 2019 Ideas|2019]], [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].
+* See also ideas from [[Google Summer of Code 2024 Ideas|2024]], [[Google Summer of Code 2023 Ideas|2023]], [[Google Summer of Code 2022 Ideas|2022]], [[Google Summer of Code 2021 Ideas|2021]],[[Google Summer of Code 2020 Ideas|2020]], [[Google Summer of Code 2019 Ideas|2019]], [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].
 -----
@@ Line 27: / Line 27: @@
 * Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code Administrative]] wiki 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 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 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.
 == The ideas pages ==
@@ Line 43: / Line 43: @@
 [[Image:logo-grass.png|60px|right]]
 * [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2025 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!
 [[Image:Pgrouting-logo.png|60px|right]]
@@ Line 53: / Line 49: @@
 [[Image:ZOO-Project-mini.png|60px|right]]
 * [https://github.com/ZOO-Project/ZOO-Project/wiki/Google%E2%80%90Summer%E2%80%90of%E2%80%90Code%E2%80%902025%E2%80%90Project%E2%80%90Ideas '''ZOO-Project''' Ideas]:  The [https://zoo-project.org/ ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions and is able to handle services implemented in various programming languages.
 === OSGeo Foundation Community project ===
-<!--[[Image:ZOO-Project-mini.png|60px|right]]
+[[Image:ZOO-Project-mini.png|60px|right]]
 * [https://github.com/ZOO-Project/ZOO-Project/wiki/Google-Summer-of-Code-2024-Project-Ideas '''ZOO-Project''' Ideas]:  The [https://zoo-project.org/ ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions and is able to handle services implemented in various programming languages.
-<!--* [https://github.com/istSOS/istsos2/wiki/istSOS-GSoC-2024 '''istSOS''' Ideas]: The [https://www.iatsos.org istSOS] project is sensor data management tool that allows collection, maintenance and publishing of monitoring observations using the Open Geospatial Consortium (OGC) Sensor Observation Service (SOS) standard.
+* [https://github.com/istSOS/istsos2/wiki/istSOS-GSoC-2024 '''istSOS''' Ideas]: The [https://www.iatsos.org istSOS] project is sensor data management tool that allows collection, maintenance and publishing of monitoring observations using the Open Geospatial Consortium (OGC) Sensor Observation Service (SOS) standard.
--->
 === OSGeo Foundation Guest Project ===

@@ Line 50: / Line 50: @@
 [[Image:Pgrouting-logo.png|60px|right]]
 * [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2025 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.
 === OSGeo Foundation Community project ===

@@ Line 23: / Line 23: @@
 * There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.
-* [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.
+* [http://www.osgeo.org OSGeo] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.
 * Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code Administrative]] wiki page.

@@ Line 17: / Line 17: @@
 These ideas are '''*only*''' to motivate you and serve as an example of the kind of hills we want to charge up. Your own ideas are more than welcome - they are encouraged. We view you as the next wave of open-source leaders and the future of the geospatial industry; show us what you've got!
-* '''Contributors: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand successful teamwork and interplay of project, mentors, and students.
+* '''Contributors: check out the [[Google Summer of Code Recommendations for Students]] page.
 * There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.
-* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.
+* [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.
 * Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code Administrative]] wiki page.

@@ Line 39: / Line 39: @@
 === OSGeo Foundation graduated project ===
-<!--[[Image:logo-grass.png|60px|right]]
+[[Image:logo-grass.png|60px|right]]
-* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!
+* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2025 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!
--->
 <!--[[Image:logo-postgis.png|60px|right]]
 * [https://trac.osgeo.org/postgis/wiki/GoogleSummerCode2022 '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

@@ Line 46: / Line 46: @@
 -->
-<!--[[Image:Pgrouting-logo.png|60px|right]]
+[[Image:Pgrouting-logo.png|60px|right]]
-* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2024 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.
+* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2025 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.
 === OSGeo Foundation Incubation project ===