OSGeo - User contributions [en]

Google Summer of Code 2026 Accepted

2026-04-30T17:12:42Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

Google Summer of Code Application 2026

2026-03-01T19:23:02Z

Krashish8:

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

== Application Status ==

'''''Accepted as Mentor Org''''' (Updated Feb 19, 2026)

'''''On-going''''' (OSGeo's application submitted on February 3, 2026)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2025|2025]], [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2026_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2026 would be our 20th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 240+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2026 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2026 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2025: 9/9
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code 2026 Ideas

2026-02-04T18:18:30Z

Krashish8:

Google Summer of Code 2026 Ideas

2026-02-03T18:17:59Z

Krashish8:

Google Summer of Code 2026 Ideas

2026-02-03T16:11:16Z

Krashish8:

Google Summer of Code 2026 Ideas

2026-02-03T16:08:29Z

Krashish8:

Google Summer of Code Application 2026

2026-02-03T15:16:31Z

Krashish8:

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

== Application Status ==



'''''On-going''''' (OSGeo's application submitted on February 3, 2026)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2025|2025]], [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2026_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2026 would be our 20th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 240+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2026 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2026 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2025: 9/9
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2026

2026-02-03T15:15:12Z

Krashish8:

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

== Application Status ==



'''''On-going''''' (OSGeo's application submitted on February 3, 2026)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2026_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2026 would be our 20th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 240+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2026 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2026 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2025: 9/9
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2026

2026-02-03T15:13:19Z

Krashish8:

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

== Application Status ==



'''''On-going''''' (OSGeo's application submitted on February 3, 2026)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2026_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2026 would be our 20th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 230+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2026 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2026 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2025: 9/9
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2026

2026-02-03T15:12:11Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.or..."

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

== Application Status ==

<-- '''''Accepted as Mentor Org''''' (Updated Feb 27, 2025) -->

'''''On-going''''' (OSGeo's application submitted on February 3, 2026)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2026_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2026 would be our 20th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 230+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2026 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2026 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2025: 9/9
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Administrative

2026-02-03T15:09:06Z

Krashish8:

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

* Back to the main OSGeo [[Google Summer of Code 2026]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2026 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2026 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 and continuing ahead...(Must Read) ==
(citing from official GSoC 2022 announcement)

* 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.

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [https://discourse.osgeo.org/c/initiatives/soc OSGeo SoC discourse] right away. The list is the central communication channel for mentors, students, and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe to it, you are encouraged to introduce yourself and your role. We look forward to hearing from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* Admins: [[User:RajatShinde|Rajat Shinde]], [[User:Rahulworld|Rahul Chauhan]], [[User:Krashish8|Ashish Kumar]]
[[Image:File-Rajat_iitb_2_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rajatshinde|Rajat Shinde]][[Image:ProfilePhoto.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rahulworld|Rahul Chauhan]]
[[Image:Ashish_Kumar_photo.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Krashish8|Ashish Kumar]]

Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

* Previous Admins (names in alphabetical order): Anne Ghisla, Carolina Arias Muñoz, Margherita Di Leo, Florin-Daniel Cioloboc, Jeff McKenna, Helmut Kudrnovsky, Werner Macho.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read below.


== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have multiple '''backup mentors''', and they should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' The mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filled within these dates. There are '''2 evaluation periods''' where mentors are required to complete an evaluation of their student from GSoC 2022. After the first 5 weeks of coding, and then at the end during submission of the project. The evaluation forms are shorter than previous years so they should take less time to complete.

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Guides for mentors ==

* [https://archive.flossmanuals.net/GSoCMentoring/what-is-gsoc.html The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [https://web.archive.org/web/20190712141549/https://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2025/organizations/osgeo-open-source-geospatial-foundation 2025], [https://summerofcode.withgoogle.com/archive/2024/organizations/osgeo-open-source-geospatial-foundation 2024], [https://summerofcode.withgoogle.com/archive/2023/organizations/osgeo-open-source-geospatial-foundation 2023], [https://summerofcode.withgoogle.com/archive/2022/organizations/osgeo-open-source-geospatial-foundation 2022], [https://summerofcode.withgoogle.com/archive/2021/organizations/5115040503431168/ 2021], [https://summerofcode.withgoogle.com/archive/2020/organizations/5355444958134272/ 2020],[https://summerofcode.withgoogle.com/archive/2019/organizations/6684630290268160/ 2019],[https://summerofcode.withgoogle.com/archive/2018/organizations/4890968767594496/ 2018],[https://summerofcode.withgoogle.com/archive/2017/organizations/4554340639440896/ 2017],[https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016], [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2026|2026]], [[Google Summer of Code 2025|2025]], [[Google Summer of Code 2024|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]]

* OSGeo Applications: [[Google Summer of Code Application 2026|2026]], [[Google Summer of Code Application 2025|2025]], [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]], [[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code Administrative

2026-02-03T15:03:27Z

Krashish8:

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

* Back to the main OSGeo [[Google Summer of Code 2026]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2026 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2026 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 and continuing ahead...(Must Read) ==
(citing from official GSoC 2022 announcement)

* 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.

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [https://discourse.osgeo.org/c/initiatives/soc OSGeo SoC discourse] right away. The list is the central communication channel for mentors, students, and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe to it, you are encouraged to introduce yourself and your role. We look forward to hearing from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* Admins: [[User:RajatShinde|Rajat Shinde]], [[User:Rahulworld|Rahul Chauhan]], [[User:Krashish8|Ashish Kumar]]
[[Image:File-Rajat_iitb_2_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rajatshinde|Rajat Shinde]][[Image:ProfilePhoto.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rahulworld|Rahul Chauhan]]
[[Image:Ashish_Kumar_photo.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Krashish8|Ashish Kumar]]

Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

* Previous Admins (names in alphabetical order): Anne Ghisla, Carolina Arias Muñoz, Margherita Di Leo, Florin-Daniel Cioloboc, Jeff McKenna, Helmut Kudrnovsky, Werner Macho.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read below.


== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have multiple '''backup mentors''', and they should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' The mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filled within these dates. There are '''2 evaluation periods''' where mentors are required to complete an evaluation of their student from GSoC 2022. After the first 5 weeks of coding, and then at the end during submission of the project. The evaluation forms are shorter than previous years so they should take less time to complete.

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2025/organizations/osgeo-open-source-geospatial-foundation 2025], [https://summerofcode.withgoogle.com/archive/2024/organizations/osgeo-open-source-geospatial-foundation 2024], [https://summerofcode.withgoogle.com/archive/2023/organizations/osgeo-open-source-geospatial-foundation 2023], [https://summerofcode.withgoogle.com/archive/2022/organizations/osgeo-open-source-geospatial-foundation 2022], [https://summerofcode.withgoogle.com/archive/2021/organizations/5115040503431168/ 2021], [https://summerofcode.withgoogle.com/archive/2020/organizations/5355444958134272/ 2020],[https://summerofcode.withgoogle.com/archive/2019/organizations/6684630290268160/ 2019],[https://summerofcode.withgoogle.com/archive/2018/organizations/4890968767594496/ 2018],[https://summerofcode.withgoogle.com/archive/2017/organizations/4554340639440896/ 2017],[https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016], [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2026|2026]], [[Google Summer of Code 2025|2025]], [[Google Summer of Code 2024|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]]

* OSGeo Applications: [[Google Summer of Code Application 2026|2026]], [[Google Summer of Code Application 2025|2025]], [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]], [[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2026

2026-02-03T15:01:45Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2026 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2026 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.

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2025|2025]],
[[Google Summer of Code 2024|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 Category here:

: https://discourse.osgeo.org/c/initiatives/soc

[[Category:Google Summer of Code]]

Google Summer of Code 2026 Ideas

2026-02-03T15:00:33Z

Krashish8:

Google Summer of Code 2026

2026-02-03T15:00:12Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2026 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2026 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.

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2025|2025]],
[[Google Summer of Code 2024|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 Category here:

: https://discourse.osgeo.org/c/initiatives/gsoc

[[Category:Google Summer of Code]]

Google Summer of Code Administrative

2026-02-03T14:58:47Z

Krashish8:

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

* Back to the main OSGeo [[Google Summer of Code 2026]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2026 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages

This is the central page for OSGeo administrative information in Google Summer of Code.

== GSoC general information ==

* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]
* [https://developers.google.com/open-source/gsoc/ Official 2026 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 and continuing ahead...(Must Read) ==
(citing from official GSoC 2022 announcement)

* 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.

== Contacts ==

* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students, and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe to it, you are encouraged to introduce yourself and your role. We look forward to hearing from you!

* To contact OSGeo's GSoC admin team directly:
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]
** join the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])

* Admins: [[User:RajatShinde|Rajat Shinde]], [[User:Rahulworld|Rahul Chauhan]], [[User:Krashish8|Ashish Kumar]]
[[Image:File-Rajat_iitb_2_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rajatshinde|Rajat Shinde]][[Image:ProfilePhoto.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Rahulworld|Rahul Chauhan]]
[[Image:Ashish_Kumar_photo.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Krashish8|Ashish Kumar]]

Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

* Previous Admins (names in alphabetical order): Anne Ghisla, Carolina Arias Muñoz, Margherita Di Leo, Florin-Daniel Cioloboc, Jeff McKenna, Helmut Kudrnovsky, Werner Macho.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read below.


== A Mentor's Responsibilities ==

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have multiple '''backup mentors''', and they should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' The mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filled within these dates. There are '''2 evaluation periods''' where mentors are required to complete an evaluation of their student from GSoC 2022. After the first 5 weeks of coding, and then at the end during submission of the project. The evaluation forms are shorter than previous years so they should take less time to complete.

== Tips for mentors ==

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

=== Good ideas ===

* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
* If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
* '''Talking in conferences''' does attract quality students to apply to GSoC
* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc

* ...

=== Bad ideas ===

* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
* If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.

* ...

== Guides for mentors ==

* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]

== Learn more ==

* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2025/organizations/osgeo-open-source-geospatial-foundation 2025], [https://summerofcode.withgoogle.com/archive/2024/organizations/osgeo-open-source-geospatial-foundation 2024], [https://summerofcode.withgoogle.com/archive/2023/organizations/osgeo-open-source-geospatial-foundation 2023], [https://summerofcode.withgoogle.com/archive/2022/organizations/osgeo-open-source-geospatial-foundation 2022], [https://summerofcode.withgoogle.com/archive/2021/organizations/5115040503431168/ 2021], [https://summerofcode.withgoogle.com/archive/2020/organizations/5355444958134272/ 2020],[https://summerofcode.withgoogle.com/archive/2019/organizations/6684630290268160/ 2019],[https://summerofcode.withgoogle.com/archive/2018/organizations/4890968767594496/ 2018],[https://summerofcode.withgoogle.com/archive/2017/organizations/4554340639440896/ 2017],[https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016], [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]

* OSGeo GSoC wiki pages: [[Google Summer of Code 2026|2026]], [[Google Summer of Code 2025|2025]], [[Google Summer of Code 2024|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]]

* OSGeo Applications: [[Google Summer of Code Application 2026|2026]], [[Google Summer of Code Application 2025|2025]], [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]], [[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]], [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]

[[Category: Google Summer of Code]]

Google Summer of Code 2026 Ideas

2026-02-03T14:52:16Z

Krashish8:

Google Summer of Code 2021 Ideas

2026-02-03T14:50:58Z

Krashish8: Undo revision 135324 by Krashish8 (talk)

Google Summer of Code 2021 Ideas

2026-02-03T14:50:29Z

Krashish8:

Google Summer of Code 2026

2026-02-03T14:44:01Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2026 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2026 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.

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2025|2025]],
[[Google Summer of Code 2024|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 Category here:

: https://discourse.osgeo.org/c/initiatives/gsoc/42

[[Category:Google Summer of Code]]

Google Summer of Code 2026

2026-02-03T14:43:36Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2026 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2026 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.

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2025|2025]]
[[Google Summer of Code 2024|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 Category here:

: https://discourse.osgeo.org/c/initiatives/gsoc/42

[[Category:Google Summer of Code]]

Google Summer of Code 2026 Ideas

2026-02-03T14:42:27Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

Google Summer of Code 2025

2026-01-24T08:18:05Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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]]

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2024|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 Category here:

: https://discourse.osgeo.org/c/initiatives/gsoc/42

[[Category:Google Summer of Code]]

Google Summer of Code 2025 Results

2026-01-24T08:17:03Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

File:Ashish Kumar photo.jpg

2026-01-24T04:19:27Z

Krashish8: Krashish8 uploaded a new version of File:Ashish Kumar photo.jpg

Ashish Kumar photo (https://github.com/krashish8)

File:Ashish Kumar photo.jpg

2025-10-20T12:28:57Z

Krashish8: Krashish8 uploaded a new version of File:Ashish Kumar photo.jpg

Ashish Kumar photo (https://github.com/krashish8)

File:Ashish Kumar photo.jpg

2025-05-10T10:04:35Z

Krashish8: Krashish8 uploaded a new version of File:Ashish Kumar photo.jpg

Ashish Kumar photo (https://github.com/krashish8)

Google Summer of Code 2025 Accepted

2025-05-10T09:55:33Z

Krashish8: Create initial page

Google Summer of Code Application 2025

2025-03-01T16:42:46Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.or..."

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

== Application Status ==

'''''Accepted as Mentor Org''''' (Updated Feb 27, 2025)

'''''On-going''''' (OSGeo's application submitted on February 10, 2025)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2024|2024]], [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Which year was your project started?''': 2006
* '''Link to your source code location''': https://github.com/OSGeo
* '''Organization Category''': End user applications, Other
* '''Ideas List URL''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2025_Ideas
* '''Organization Technologies (5 max)''': C, C++, python, javascript, java
* '''Organization Topics (5 max)''': open science, gis, citizen science, geolocation, mapping
* '''Organization Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community-driven development. 

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular: 
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers. 
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS. 
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS. 
* Metadata Catalogues: GeoNetwork, pycsw. 
* Content Management Systems: GeoNode. 
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project. 
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data. 

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Contributor Guidance''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Social Media - X url''': https://x.com/osgeo
* '''Social Media - Facebook''': https://www.facebook.com/OSGeoFoundation/
* '''Social Media - Blog''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2025 would be our 19th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 230+ developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Three of the previous GSoC students with OSGeo are currently serving as the GSoC Org Admins for OSGeo and one of them is serving on the Board of Directors.

In the past years, the majority of the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2025 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2025 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2021 and 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2021 conference - https://www.youtube.com/watch?v=Jjgghz_EzWQ), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''Anything else we should know? (Optional)''': The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

From the last couple of years, all the selected GSoC developers presented their work in a special session of the global FOSS4G conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of our appreciation to the efforts of Google Open Source and the Google GSoC Team, we are sharing the links to the sessions.

Link 1 (Contributor presentations): https://www.youtube.com/watch?v=Jjgghz_EzWQ
Link 2 (Org Admins presentation): https://www.youtube.com/watch?v=Flr1tcrcAvE

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

* '''Is your organization part of any government''': No
* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2024: 7/7
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2024

2025-03-01T16:31:29Z

Krashish8:

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

== Application Status ==

'''''Accepted as Mentor Org''''' (Updated Feb 25, 2024)

'''''On-going''''' (OSGeo's application submitted on February 7, 2024)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C/C++, python, sql, database, java
* '''Topic Tags''': Mapping, geolocation, GIS, citizen science, open science
* '''Ideas List''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2024_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS
* Metadata Catalogues: GeoNetwork, pycsw
* Content Management Systems: GeoNode
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
We have developed a recommendation for students to follow for being successful GSoC candidates. It is available on OSGeo's wiki and can be accessed by following https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students. It contains all the useful information including the template for preparing the Proposal and the community’s expectations from the Students. The Student proposal template is also available at the OSGeo's GSoC Github repository and can be accessed by following the link: https://github.com/OSGeo/gsoc/blob/master/proposal_template.md
</pre>

* '''Proposal Tags''':
Grass GIS, MapMint, PostGIS, pgRouting, QGIS
New Feature, Optimization, Web Mapping, Geospatial Desktop, Geospatial Libraries, Geospatial Metadata Catalogue

* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2023 would be our 17th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 215 developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. One of the previous GSoC Student with OSGeo is currently serving the OSGeo Board of Directors.

Last year, all the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2023 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2023 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2022 conference), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise of new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How many potential mentors have agreed to mentor this year?''' 10 - 15

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''(Deprecated from 2023 Application)How will you keep students involved with your community after GSoC?''': The student application template includes a "Future development" section in their proposal which inhibits the thought process of students to continue developing for the OSGeo after completion of GSoC. It also provides the developer community with new ideas and scope for developments. Some of the OSGeo projects have been encouraging the students even after GSoC by providing them with reasonable financial support to present their work in the geospatial conferences, especially global FOSS4G conferences and local meetups.

* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''What year was your project started?''' 2006

* '''Where does your source code live?''' https://github.com/OSGeo

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

In 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2022 conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of appreciation to the efforts of Google Open Source and Google GSoC Team, we are sharing the links to the sessions.

Link 1 to Contributors FOSS4G 2022 presentations
Link 2 Org Admins FOSS4G 2022 presentation

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code Application 2024

2025-03-01T16:26:55Z

Krashish8:

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

== Application Status ==

'''''Accepted as Mentor Org''''' (Updated Feb 25, 2024)

'''''On-going''''' (OSGeo's application submitted on February 7, 2024)

: Timeline: https://developers.google.com/open-source/gsoc/timeline

== Old applications ==

* Based on [[Google Summer of Code Application 2023|2023]], [[Google Summer of Code Application 2022|2022]], [[Google Summer of Code Application 2021|2021]], [[Google Summer of Code Application 2020|2020]], [[Google Summer of Code Application 2019|2019]],[[Google Summer of Code Application 2018|2018]], [[Google Summer of Code Application 2017|2017]],[[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google Summer of Code Application 2010|2010]],[[Google Summer of Code Application 2009|2009]],[[2008 Google SoC Application|2008]],[[2007 Google SoC Application|2007]]

== Profile ==

* '''Name''': OSGeo
* '''Website URL''': https://www.osgeo.org
* '''Tagline''': The Open Source Geospatial Foundation
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0)
* '''Organization Category''': Other
* '''Technology Tags (5 max)''': C/C++, python, sql, database, java
* '''Topic Tags''': Mapping, geolocation, GIS, citizen science, open science
* '''Ideas List''': http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Ideas
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
* '''Long Description''':
using the recommended "Limited Markdown" syntax:
<pre>
The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.

OSGeo serves as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:
* Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers
* Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS
* Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS
* Metadata Catalogues: GeoNetwork, pycsw
* Content Management Systems: GeoNode
* Community Projects: pgRouting, istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project
* Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeoLive DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
</pre>

* '''Application Instructions''':
using the recommended "Limited Markdown" syntax:
<pre>
We have developed a recommendation for students to follow for being successful GSoC candidates. It is available on OSGeo's wiki and can be accessed by following https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students. It contains all the useful information including the template for preparing the Proposal and the community’s expectations from the Students. The Student proposal template is also available at the OSGeo's GSoC Github repository and can be accessed by following the link: https://github.com/OSGeo/gsoc/blob/master/proposal_template.md
</pre>

* '''Proposal Tags''':
Grass GIS, MapMint, PostGIS, pgRouting, QGIS
New Feature, Optimization, Web Mapping, Geospatial Desktop, Geospatial Libraries, Geospatial Metadata Catalogue

* '''Chat Contact Method''': https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_IRC
* '''Mailing List''': https://www.osgeo.org/community/communications/
* '''General email''': gsoc-admin(at)osgeo(dot)org
* '''Twitter url''': https://twitter.com/osgeo
* '''Blog url''': http://planet.osgeo.org/

== Questionnaire ==

* '''Why does your org want to participate in Google Summer of Code?''': The OSGeo is now a veteran GSoC organization (2023 would be our 17th year participating), and it has been a tremendous journey. The previous editions of GSoC for OSGeo have motivated new great developers, as well as GSoC mentors (we have graduated 215 developers in total through the GSoC program) to contribute towards the development of open-source geospatial projects. One of the previous GSoC Student with OSGeo is currently serving the OSGeo Board of Directors.

Last year, all the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2023 by supporting new developers in their summer projects. OSGeo, acting as an umbrella organization has also tightened the connection with guest software projects (Open Source projects involved with making maps and geospatial data processing but are not yet officially part of OSGeo). We are highly enthusiastic about our participation in GSoC 2023 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful GSoC program?''': The OSGeo foundation believes in encouraging contributors to enhance their acumen for working in a team environment, managing different time schedules, understanding community interactions, presenting their work in conferences (In 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2022 conference), and primarily contributing to leading geospatial tools.

So, a successful GSoC program with OSGeo would comprise of new feature development along with guiding the developers to be future leaders of the open-source geospatial community and open source world, in general.

* '''How many potential mentors have agreed to mentor this year?''' 10 - 15

* '''How will you keep mentors engaged with their students?''': The Mentors for OSGeo GSoC projects have significant prior experience of GSoC, either as a past contributor, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 3 mentors (2 primary & a backup) are required for every project. Usually, the mentors are regular (code) contributors and/or experts in their field, and are enthusiastic to inspire the students in becoming open source geospatial developers. The weekly report submitted by the students is evaluated by the mentors and the Org Admins regularly. An efficient communication channel exists between students, mentors, and the admins, and all the details are frequently summarised in the openly accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Administrative) throughout the GSoC timeline.

* '''How will you keep your GSoC contributors on schedule to complete their projects?''': We have created a student application template for the interested students in participating at the GSoC with OSGeo and it is available at https://github.com/OSGeo/gsoc/blob/master/proposal_template.md. The student application template puts a strong emphasis on the timeline of the project and the expected weekly commitment (in hours) of the contributor. In order to stick to this timeline, it is important for the students to have a clear picture of the project and divide it into smaller and achievable tasks. After mentors evaluation of the projects based on the timeline mentioned, the Org Admins keep track of the project's progress by evaluating the weekly reports. Based on this, the contributors can adjust the timeline and their weekly commitment with the help of their mentors. We have published a Google Summer of Code Recommendations wiki for Students and is available online at https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

* '''How will you get your GSoC Contributors involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the contributors joining the community for GSoC become an inherent part of it. Every participating contributor is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The contributors are required to send weekly reports to the project developer mailing lists along with the GSoC mailing list for necessary feedback. Prior to the commencement of the Coding period, the Community Bonding period plays a significant role in comforting the contributor with the development environment and helping them with the work culture of the project community. We aim to foster closer communication by engaging all our contributors, developers, and community mentors through an accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, and encouraging different perspectives within the open-source geospatial community.

* '''(Deprecated from 2023 Application)How will you keep students involved with your community after GSoC?''': The student application template includes a "Future development" section in their proposal which inhibits the thought process of students to continue developing for the OSGeo after completion of GSoC. It also provides the developer community with new ideas and scope for developments. Some of the OSGeo projects have been encouraging the students even after GSoC by providing them with reasonable financial support to present their work in the geospatial conferences, especially global FOSS4G conferences and local meetups.

* '''Has your org been accepted as a mentoring org in Google Summer of Code before?''' yes
* '''Which years did your org participate in GSoC?''': from 2007 onwards
* '''What is your success/fail rate per year?'''

Year: pass/total
2023: 7/7
2022: 6/7
2021: 12/12
2020: 10/10
2019: 7/7
2018: 10/13
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22
2012: 20/22
2011: 19/21
2010: 7/10
2009: 17/20
2008: 15/19
2007: 13/19

* '''What year was your project started?''' 2006

* '''Where does your source code live?''' https://github.com/OSGeo

* '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC, to help give students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences.

In 2022, all the selected GSoC developers presented their work in a special session of the global FOSS4G 2022 conference. Also, the OSGeo Org Admins Team highlighted the journey of GSoC with OSGeo. As a part of appreciation to the efforts of Google Open Source and Google GSoC Team, we are sharing the links to the sessions.

Link 1 to Contributors FOSS4G 2022 presentations
Link 2 Org Admins FOSS4G 2022 presentation

We participated in the inaugural GSoD 2019 and also in the Google Code-in which successfully helped in inspiring the young students to craft them as the future leaders of the geospatial industry. And most of all: it's super fun!

[Back to [[Google Summer of Code 2022]] @ OSGeo]

[[Category: Google Summer of Code]]
[[Category: Stats]]

Google Summer of Code 2024 Results

2025-02-14T05:52:02Z

Krashish8:

Google Summer of Code 2025 Ideas

2025-02-14T05:31:10Z

Krashish8:

Google Summer of Code 2025

2025-02-14T05:26:58Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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.

== 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 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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2024|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]]

Google Summer of Code 2025

2025-02-14T05:26:30Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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.

== 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
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.

* 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.

See also older Google Summer of Code
[[Google Summer of Code 2024|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]]

Google Summer of Code 2025

2025-02-14T05:26:13Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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.

== 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
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.

* 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.

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]]

Google Summer of Code 2024 Results

2025-02-02T15:33:11Z

Krashish8:

Google Summer of Code 2024 Results

2025-02-02T15:32:58Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

Google Summer of Code 2024

2025-02-02T15:29:12Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2024 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2024 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 2024 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|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]]

Google Summer of Code 2024 Accepted

2024-05-13T09:57:32Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

Google Summer of Code 2024 Ideas

2024-05-13T09:55:51Z

Krashish8:

Google Summer of Code 2024

2024-05-13T09:54:50Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2024 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2024 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) ==

* 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|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]]

Google Summer of Code 2024

2024-05-13T09:54:35Z

Krashish8: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2023 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2024 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) ==

* 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|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]]

Google Summer of Code 2023

2024-05-13T09:54:01Z

Krashish8:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[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] 2023 page ==

* If you are a '''student''', please visit our [[Google Summer of Code 2023 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 2023 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 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]]

User:Krashish8

2024-05-13T09:31:07Z

Krashish8:

{{OSGeo Member
|Name=Ashish Kumar
|JobTitle=Software Engineer
|Company=
|Address=
|Country=India
|State=Karnataka
|City=Bangalore
|Coordinate=12.9716, 77.5946
|LocalChapter=India
|Email=ashishkr23438 AT gmail DOT com
|Phone=
|InstantMessaging=
|SocialMedia=https://www.linkedin.com/in/ashishkr23438/
|Photo=Ashish Kumar photo.jpg
|Languages=English; Hindi
|Info=
* Contributing as OSGeo GSoC Org Administrator and Mentor for pgRouting in the Google Summer of Code since 2022.
* Maintainer of the vrpRouting project, responsible for adding more functionalities to it, and for making the releases of pgRouting.
* Added the VRP functionality with VROOM for pgRouting as a Student Developer in the Google Summer of Code 2021.
* Added two functions in pgRouting v3.2.0 as a Student Developer in the Google Summer of Code 2020.
* Bachelor of Technology Graduate in Computer Science and Engineering from the Indian Institute of Technology (Banaras Hindu University), Varanasi, India.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=Yes
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=No
}}
I am Ashish Kumar, a Bachelor of Technology graduate from IIT (BHU) Varanasi, India in Computer Science and Engineering. My experience with the open source started in 2020 when I contributed to pgRouting through GSoC and added two functions to it from the Boost Graph Library. It was an enriching experience in terms of the learnings that I had, and hence I have been contributing to pgRouting since then. Later, in GSoC 2021, I again contributed to pgRouting and ported the VROOM functionality to the vrpRouting codebase, acting as an initiative to effectively solve real-world Vehicle-Routing problems using some standard library with pgRouting. I'm still an active developer of pgRouting, responsible for making the releases and adding more functionalities to it. I'm currently contributing as OSGeo GSoC Org Administrator and Mentor for pgRouting in the Google Summer of Code and have been doing so since 2022.

User:Krashish8

2024-05-13T09:30:35Z

Krashish8:

Google Summer of Code 2023 Results

2023-09-11T07:31:29Z

Krashish8:

Google Summer of Code 2023 Accepted

2023-05-08T14:48:54Z

Krashish8:

Google Summer of Code 2023 Accepted

2023-05-07T10:44:10Z

Krashish8: Update GSoC 2023 selections

File:Ashish Kumar photo.jpg

2023-05-07T10:38:36Z

Krashish8: Krashish8 uploaded a new version of File:Ashish Kumar photo.jpg

Ashish Kumar photo (https://github.com/krashish8)