OSGeo - User contributions [en]

Google Summer of Code 2025

2025-02-10T17:53:02Z

Rahulworld: updated

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

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

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

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

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

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

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

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

[[Category:Google Summer of Code]]

Google Summer of Code 2025

2025-02-10T17:51:39Z

Rahulworld: Created wiki page

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

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

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

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

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

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

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

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

[[Category:Google Summer of Code]]

Google Summer of Code 2025 Ideas

2025-02-02T10:53:14Z

Rahulworld:

Google Summer of Code 2025 Ideas

2025-02-02T10:52:44Z

Rahulworld:

Google Summer of Code 2025 Ideas

2025-02-02T10:50:10Z

Rahulworld: Created GSoC 2024 Page

Google Summer of Code Application 2024

2024-02-25T12:32:28Z

Rahulworld: Created GSoC 2024 page

<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
2022: 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 Ideas

2024-01-29T14:42:36Z

Rahulworld: created new page

Google Summer of Code 2023 Results

2023-09-10T15:33:27Z

Rahulworld: updated with minor change

Google Summer of Code 2023 Results

2023-09-10T15:32:21Z

Rahulworld: Created result page

Google Summer of Code Application 2023

2023-02-25T16:00:45Z

Rahulworld: Created GSoC 2023 application page

<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 22, 2023)

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

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

== Old applications ==

* Based on [[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
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 2022

2022-03-08T14:00:59Z

Rahulworld: Create gsoc application page

<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 March 7, 2022)

'''''On-going''''' (OSGeo's application submitted on February 21, 2022)

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

== Old applications ==

* Based on [[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_2021_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 (2021 would be our 15th 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 197 students in total through the GSoC program) to contribute towards the development of open-source geospatial projects. Last year, all the accepted projects successfully completed their objectives, and continuing this spirit, the OSGeo community is excited to take this forward in 2021 by supporting new students and 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 2021 and definitely look forward to another geospatial GSoC!

* '''What would your org consider to be a successful summer?''': 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, and primarily contributing to leading geospatial tools. So, a successful summer for GSoC 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 student, as a mentor, or an experienced member of the project community. In order to maintain consistency and availability, 2 mentors 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_2021_Administrative) throughout the GSoC timeline.

* '''How will you help your students stay 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 student. 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 a mentor's evaluation of the projects based on the timeline mentioned, we keep track of the project's progress by evaluating the weekly reports. Based on this, the students 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 students involved in your community during GSoC?''': Over the years, the OSGeo foundation has developed into a great community and the students joining the community for GSoC become an inherent part of it. Every participating student is encouraged to share the proposal with the relevant software developer communities for getting feedback and comments about the same. The students 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 student 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 students, 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.

* '''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
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?''' The Open Source Geospatial Foundation is an umbrella organization comprising multiple projects associated with the geospatial domain. Every project has their own repository on various hosts including Github and SVN. Some of the examples include: OSGeo’s GitHub- https://github.com/OSGeo or OSGeo's hosted git https://git.osgeo.org or SVN https://svn.osgeo.org/

* '''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. 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 2021]] @ OSGeo]

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

Google Summer of Code 2022 Administrative

2022-01-09T13:56:26Z

Rahulworld: Created Google Summer of Code 2022 Administrative

<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 2022]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2022 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 2022.

== 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 2021 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== New Modifications with GSoC 2022 ==
* '''Smaller project size''' - All students participating in the 2021 program will be working on ~175 hour project (instead of 350 hr project).

* '''2 evaluations (instead of 3)''' - There will be an evaluation after 5 weeks and the final evaluation will take place after the 10th week. Also, the students are no longer required to complete their first evaluation (though we encourage them to do so), so if a student doesn’t complete the first evaluation they will not automatically be removed from the program. They are still required to complete the final evaluation.

* '''Eligibility requirements''' - In 2020 there are many ways students are learning and we want to acknowledge that the students who are 18 years old AND currently enrolled (or accepted into) a post-secondary academic program as of May 17, 2021 or have graduated from a post-secondary academic program between December 1, 2020 and May 17, 2021 are eligible to apply to the GSoC program. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here. This means that now the program will be open to folks participating in a variety of different academic programs, not just accredited university programs. This includes licensed coding camps, community colleges, and many other programs that may not be accredited yet but are post-secondary academic programs.

== 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 it, you are encouraged to introduce yourself and your role. We look forward to hear 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]]
[[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]]

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 2021. 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/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 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 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 2022

2022-01-09T13:52:46Z

Rahulworld: Created GSoC 2022 page

<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] 2022 page ==

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

== New Modifications with GSoC 2021 ==
* '''Smaller project size''' - All students participating in the 2021 program will be working on ~175 hour project (instead of 350 hr project).

* '''2 evaluations (instead of 3)''' - There will be an evaluation after 5 weeks and the final evaluation will take place after the 10th week. Also, the students are no longer required to complete their first evaluation (though we encourage them to do so), so if a student doesn’t complete the first evaluation they will not automatically be removed from the program. They are still required to complete the final evaluation.

* '''Eligibility requirements''' - In 2020 there are many ways students are learning and we want to acknowledge that the students who are 18 years old AND currently enrolled (or accepted into) a post-secondary academic program as of May 17, 2021 or have graduated from a post-secondary academic program between December 1, 2020 and May 17, 2021 are eligible to apply to the GSoC program. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here. This means that now the program will be open to folks participating in a variety of different academic programs, not just accredited university programs. This includes licensed coding camps, community colleges, and many other programs that may not be accredited yet but are post-secondary academic programs.

See also older Google Summer of Code
[[Google Summer of Code 2020|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 2022 Ideas

2022-01-09T13:51:54Z

Rahulworld: updated

Google Summer of Code 2022 Ideas

2022-01-09T13:47:43Z

Rahulworld: Created GSoC 2022 page

<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] 2022 page ==

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

== New Modifications with GSoC 2021 ==
* '''Smaller project size''' - All students participating in the 2021 program will be working on ~175 hour project (instead of 350 hr project).

* '''2 evaluations (instead of 3)''' - There will be an evaluation after 5 weeks and the final evaluation will take place after the 10th week. Also, the students are no longer required to complete their first evaluation (though we encourage them to do so), so if a student doesn’t complete the first evaluation they will not automatically be removed from the program. They are still required to complete the final evaluation.

* '''Eligibility requirements''' - In 2020 there are many ways students are learning and we want to acknowledge that the students who are 18 years old AND currently enrolled (or accepted into) a post-secondary academic program as of May 17, 2021 or have graduated from a post-secondary academic program between December 1, 2020 and May 17, 2021 are eligible to apply to the GSoC program. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here. This means that now the program will be open to folks participating in a variety of different academic programs, not just accredited university programs. This includes licensed coding camps, community colleges, and many other programs that may not be accredited yet but are post-secondary academic programs.

See also older Google Summer of Code
[[Google Summer of Code 2020|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:Rahulworld

2020-10-18T08:13:01Z

Rahulworld: Updated

{{OSGeo Member
|Name=Rahul Chauhan
|JobTitle=Student
|Company=National Institute of Technology Srinagar
|Address=Gali No. 4, Nagala Karan Singh, Kotla Road, Firozabad - 283203
|Country=India
|State=Uttar Pradesh
|City=Firozabad
|Coordinate=27.163378, 78.403311
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|College=National Institute of Technology Srinagar
|Info=
* Contributed as GSoC 2020 and GCI 2020 Org Admin for OSGeo
* Contributed as GCI 2020, 2019 and GCI 2018 Mentor for OSGeo
* Added extension "istSOS - Data analysis and statistical tool suite" support for istSOS2 in the Google Summer of Code 2017 as a student.
* Developed plugin "istSOS - Support of Unit Of Measure conversion in istSOS3" support for istSOS3 in the Google Summer of Code 2018 as a student.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan.
My current spatial coordinates are 27°09'48.2" N and 78°24'11.9"E and I reside in Firozabad, Uttar Pradesh, India. I completed my Bachelor’s degree in the specialization of Computer Science & Engineering with 8.199/10 from the National Institute of Technology Srinagar, Srinagar, Jammu & Kashmir, India. I worked on the "istSOS - Data analysis and statistical tool suite" in GSoC 2017 and "istSOS - Support of Unit Of Measure conversion in istSOS3" in GSoC 2018 as a student. I served as the Org Admin for the GSoC 2020, GCI 2020, and also co-mentored GCI 2018, 2019, and 2020 (istSOS) under OSGeo.

Some more information about me can be obtained by following the link: https://rahulworld.github.io

User:Rahulworld

2020-10-18T07:59:29Z

Rahulworld: /* Student's Biography */

{{OSGeo Member
|Name=Rahul Chauhan
|JobTitle=Student
|Company=National Institute of Technology Srinagar
|Address=301, Platinum Castle,, 3rd main, OMBR Layout, Banswadi,
|Country=India
|State=Karnataka
|City=Benglore
|Coordinate=13.010612, 77.651509
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|College=National Institute of Technology Srinagar
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan.
My current spatial coordinates are 27°09'48.2" N and 78°24'11.9"E and I reside in Firozabad, Uttar Pradesh, India. I completed my Bachelor’s degree in the specialization of Computer Science & Engineering with 8.199/10 from the National Institute of Technology Srinagar, Srinagar, Jammu & Kashmir, India. I worked on the "istSOS - Data analysis and statistical tool suite" in GSoC 2017 and "istSOS - Support of Unit Of Measure conversion in istSOS3" in GSoC 2018 as a student. I served as the Org Admin for the GSoC 2020, GCI 2020, and also co-mentored GCI 2018, 2019, and 2020 (istSOS) under OSGeo.

Some more information about me can be obtained by following the link: https://rahulworld.github.io

Google Summer of Code 2020 Improvements

2020-09-10T11:38:27Z

Rahulworld: updated page

Google Summer of Code 2020 Improvements

2020-09-10T11:20:57Z

Rahulworld: Created GSOC_20_improvement_page

Google Summer of Code 2020 Student Status Report

2020-06-08T08:46:41Z

Rahulworld: Updated week 1 reports links

Google Summer of Code 2020 Student Status Report

2020-06-08T08:39:30Z

Rahulworld: update first week report

Google Summer of Code 2020 Ideas

2020-02-05T21:03:19Z

Rahulworld: Updated

Google Summer of Code 2020 Ideas

2020-02-05T21:02:36Z

Rahulworld: Updated

Google Summer of Code 2020 Ideas

2020-02-03T18:43:57Z

Rahulworld: Updated

Google Summer of Code 2020 Ideas

2020-02-03T18:29:15Z

Rahulworld: Updated

Google Summer of Code 2020 Ideas

2020-02-03T18:26:30Z

Rahulworld: updated information

Google Summer of Code 2020 Ideas

2020-02-03T18:06:41Z

Rahulworld: updated Idea page

Google Summer of Code 2020

2020-01-26T18:03:12Z

Rahulworld: updated

Google Summer of Code 2020 Administrative

2020-01-26T18:01:41Z

Rahulworld: Creating Google Summer of Code 2020 Administrative

<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 2020]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2020 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 2020.

== 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 2020 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== 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 it, you are encouraged to introduce yourself and your role. We look forward to hear 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:Madi|Margherita Di Leo]], [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], Carolina Arias Muñoz, [[Jeff McKenna]]. Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]
.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read [https://lists.osgeo.org/pipermail/discuss/2018-January/036977.html here] and fill in the form given in the link.


== 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 a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both 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 filed within these dates. There are '''3 evaluation periods''' where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). 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/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 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 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 2020 Ideas

2020-01-26T17:58:17Z

Rahulworld: created idea page

Google Summer of Code 2020

2020-01-26T17:55:21Z

Rahulworld: Create Google Summer of Code 2020

Rahul Chauhan

2019-12-16T07:05:07Z

Rahulworld:

{{OSGeo Member
|Name=Rahul Chauhan
|JobTitle=Full Stack Developer
|Address=301, Platinum Castle, 3rd main, OMBR Layout, Banswadi,
|Country=India
|State=Karnataka
|City=Banglore
|Coordinate=13.010612, 77.651509
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|Info=Full Stack Developer @IdeaBoard, GSoC 17, 18 @OSGeo, GCI Admin 2019 @OSGeo, GCI Mentor 2018 @OSGeo
|College=National Institute of Technology Srinagar
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan. I am a Full Stack Developer and open source contributor.
Some more information about me can be obtained by following the link: https://rahulworld.github.io

Rahul Chauhan

2019-12-15T07:32:35Z

Rahulworld:

{{OSGeo Member
|Name=Rahul Chauhan
|JobTitle=Full Stack Developer
|Address=301, Platinum Castle, 3rd main, OMBR Layout, Banswadi,
|Country=India
|State=Karnataka
|City=Banglore
|Coordinate=13.010612, 77.651509
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|College=National Institute of Technology Srinagar
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan. I am a Full Stack Developer and open source contributor.
Some more information about me can be obtained by following the link: https://rahulworld.github.io

Google Summer of Code 2019 Administrative

2019-08-12T06:34:57Z

Rahulworld: Added Name

<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 2019]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2019 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 2019.

== 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 2019 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== 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 it, you are encouraged to introduce yourself and your role. We look forward to hear 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:Madi|Margherita Di Leo]], [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], Carolina Arias Muñoz, [[Jeff McKenna]]. Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]
.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read [https://lists.osgeo.org/pipermail/discuss/2018-January/036977.html here] and fill in the form given in the link.


== 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 a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both 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 filed within these dates. There are '''3 evaluation periods''' where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). 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]

== Mentor Summit ==

Each year Google hosts the "Mentor Summit" event at their headquarters, where upto 2 OSGeo delegates can attend. The date for this year's summit is: [https://developers.google.com/open-source/gsoc/2018/mentor-oa-announcements#july_23_2018_the_2018_google_summer_of_code_mentor_summit 12-14 October 2018]. We have developed guidelines for who can represent OSGeo at the summit: see [[Google Summer of Code 2019 Mentor Summit]]

=== GCI Mentor Candidates ===
Google has recently notified the OSGeo admins that Google would like to invite 1 of the OSGeo mentors from GCI 2018 to come to the [https://sites.google.com/view/gsoc-mentorsummit2019/home GSoC 2019 Mentor Summit]. Google will add $1100 to the stipend that is sent in early September, if OSGeo decides to send a GCI mentor to the GSoC 2019 summit.

OSGeo GCI admins have agreed to open the opportunity to attend to the recent OSGeo GCI mentors, using a lottery to decide if need be. Here are the requirements:

Eligibility:
* must comply with Google requirements (must have been a 2018 GCI Mentor for OSGeo);
* must have been a mentor who participated in at least one OSGeo project task instance, working with a student (meaning that you interacted with a student on at least one instance, through the GCI Dashboard)

==== Signup Below ====

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery
* Cameron Green
* Celia Virginia Vergara Castillo (Vicky Vergara)
* Abhinav Kumar
* Rahul Chauhan
* add your name here

==== Draw Time ====

2019-09-12 @ 15:00 UTC https://www.timeanddate.com/worldclock/fixedtime.html?msg=GSoC+summit+2019+lottery+draw&iso=20190812T15&p1=1440

== Learn more ==

* Previous years SoC involvement: [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 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 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 Code In 2018 Grand Prize Trip

2019-08-11T11:45:09Z

Rahulworld: Edit GCI 2018 Trip Report

Author: ([[Rahul Chauhan]] (rahulworld))

== Introduction ==
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I ([[Rahul Chauhan]] (rahulworld)) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

== Day 1 (Reception) ==
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

== Day 2 (Full Day at Google headquarters in Mountain View) ==
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
* Recruiting – Lauren Alpizar
* Android OS: Ally Sillins
* Cloud: Ryan Matsumoto
* Chrome OS – Grant Grundler
* Google Assistant – Daniel Myers
* Google TensorFlow – Paige Bailey
We had Dinner at the same office and then head back to the hotel.

== Day 3 (Fun Day in San Francisco) ==
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

== Day 4 (Closing reception in Google SF office) ==
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

== People who made this possible ==
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

[[Category: Google Code In]]

Google Code In 2018

2019-08-11T11:42:41Z

Rahulworld: Added GCI Grand Trip Report

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

[[Image:GCI-2018-results.png|thumb|right|333px|Top 5 OSGeo students from the GCI 2018 contest]]

Central page for administering OSGeo participation in Google Code In 2018

= Background =

* Google Code In program has been [https://opensource.googleblog.com/2018/09/google-code-in-2018-is-looking-for.html officially announced]
* [https://codein.withgoogle.com/ Google Code In main page]
* [https://developers.google.com/open-source/gci/how-it-works How Google Code-in Works]
* [https://developers.google.com/open-source/gci/resources/example-tasks Examples of Google Code-in Tasks] (also see OSGeo's tasks from the 2017 contest [https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/ here])
* [https://developers.google.com/open-source/gci/resources/media Logo, flyer and presentation]
* [https://developers.google.com/open-source/gci/help/responsibilities Roles and responsibilities of Students, Mentors and Admins]

= Timeline =

* [https://developers.google.com/open-source/gci/timeline Full timeline]
* Sept 7 2018: organizations can start drafting application to be mentoring organizations
* Sept 17 2018: application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=17&hour=16&min=0&sec=0 exact time]) for mentoring organizations (we should have mentors and tasks by then - we need a minimum of 25 tasks by 17 Sept, but we should aim to have between 150 & 500 tasks in total before the contest begins)
* Sept 18 2018: Mentoring organizations announced
* Oct 23 2018: Contest opens for entries by student participants ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=10&day=23&hour=16&min=0&sec=0 exact time])
* Dec 10 2018: Deadline for students to claim new tasks
* Dec 12 2018: All student work must be submitted; contest ends
* Dec 13 2018: Mentoring organizations complete all evaluations of students’ work
* Jan 7 2019: Grand Prize Winners and Finalists announced
* June (exact dates TBD): Grand Prize Winner’s Trip

= Rules =

* [https://codein.withgoogle.com/student-terms/ Contest rules]
** Ineligible individuals (according to the above rules):
*** a resident of a United States embargoed country, Brazil, Italy, or Quebec (see Google's [https://groups.google.com/d/msg/gci-mentors/KOZY6ivqfqA/9NazTL65AgAJ reasons]; [http://www.ce.camcom.it/files/normativa/dpr430_01.pdf link to the Italian law about online contests]),
*** ordinarily resident in a United States embargoed country,
*** participating as a Mentor in the 2018 Contest, or
*** otherwise prohibited by applicable export controls and sanctions programs.

= Communication =

* OSGeo's gci-discuss mailing list, which is for students to ask general questions to OSGeo admins and mentors (subscribe at https://lists.osgeo.org/mailman/listinfo/gci-discuss)
* IRC-channel: #osgeo-gsoc channel on freenode.net
** how to connect: choose your favorite IRC client, or go directly through browser with [https://webchat.freenode.net/?channels=osgeo-gsoc webchat]
* Google's "Code-in Discuss" forum (mostly for general program questions, monitored by Google staff): https://groups.google.com/forum/#!forum/gci-discuss

= Administrators =

* [[Jeff McKenna]] <libravatar email="jmckenna@gatewaygeomatics.com"/> (IRC nickname: "jmckenna")
* [[Victoria Rautenbach]] <libravatar email="victoria.rautenbach@gmail.com"/> (IRC nickname: "vrautenbach")
''Contact OSGeo's administrators: gci-admin at osgeo dot org''

= Interested mentors / volunteers =

* please fill out the Google form mentioned at [[Google Code In 2018 Mentors]]

= Recommendations for Students =

* https://wiki.osgeo.org/wiki/Google_Code_In_2018_Recommendations_for_Students

= Tasks =

* available on the GCI Dashboard when the contest starts on 23 October: https://codein.withgoogle.com/
* see the archive of OSGeo's tasks from the 2017 contest: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/
* mentors: for bulk uploading tasks see steps [https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks#Bulk_Uploading_Tasks here]

= Application =

* our OSGeo application as a mentor organization, see: [[Google Code In 2018 Application]]

= Kickoff (virtual) meeting =

* 2018-09-13 at [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=13&hour=16&min=0 16.00 UTC]
* On IRC in the '''#osgeo-gsoc''' channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])
* agenda:
** discuss ideas for tasks for the students (we need 25 tasks minimum for the application due 17 Sept)
** plan to share mentor invites to all OSGeo projects

= Lessons Learned =

* [https://wiki.osgeo.org/wiki/Google_Code_In_2018_Lessons_Learned 2018], [https://wiki.osgeo.org/wiki/Google_Code_In_2017_Lessons_Learned 2017]

= Mentor Representation at the Grand Prize Winners Trip =

* 1 mentor will represent OSGeo at the GCI Grand Prize Winners trip on June 24-27, 2019 (more information on the [https://sites.google.com/view/2018-grand-prize-trip/home trip site]
* a travel stipend of 2200 USD will be available for flight & travel costs (Google will pay for 4 nights in hotel)
* Please sign your name below if you are interested to represent OSGeo as a mentor at the GCI trip:
** [[Rahul Chauhan]] <libravatar email="rahulnitsxr@gmail.com"/> (IRC nickname: "rahulworld")
**[[Frikan Erwee]] <libravatar email="ferwee@gmail.com"/> (IRC nickname: "FrikanRw")
**[[User:Cvvergara]] <libravatar email="vicky@georepublic.de"/> (IRC nickname: "cvvergara")
** your name here

= Grand Prize Winner Trip Mentor Report =
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I ([[Rahul Chauhan]] (rahulworld)) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

=== Day 1 (Reception) ===
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

=== Day 2 (Full Day at Google headquarters in Mountain View) ===
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
* Recruiting – Lauren Alpizar
* Android OS: Ally Sillins
* Cloud: Ryan Matsumoto
* Chrome OS – Grant Grundler
* Google Assistant – Daniel Myers
* Google TensorFlow – Paige Bailey
We had Dinner at the same office and then head back to the hotel.

=== Day 3 (Fun Day in San Francisco) ===
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

=== Day 4 (Closing reception in Google SF office) ===
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

=== People who made this possible ===
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

= 2017 pages =

* see https://wiki.osgeo.org/wiki/Google_Code_In_2017

[[Category:Google Code In]]

Google Code In 2018 Grand Prize Trip

2019-08-11T11:31:08Z

Rahulworld: Edit GCI 2018 Trip Report

== Introduction ==
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I ([[Rahul Chauhan]] (rahulworld)) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

== Day 1 (Reception) ==
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

== Day 2 (Full Day at Google headquarters in Mountain View) ==
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
* Recruiting – Lauren Alpizar
* Android OS: Ally Sillins
* Cloud: Ryan Matsumoto
* Chrome OS – Grant Grundler
* Google Assistant – Daniel Myers
* Google TensorFlow – Paige Bailey
We had Dinner at the same office and then head back to the hotel.

== Day 3 (Fun Day in San Francisco) ==
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

== Day 4 (Closing reception in Google SF office) ==
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

== People who made this possible ==
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

[[Category: Google Code In]]

Google Code In 2018 Grand Prize Trip

2019-08-11T11:27:16Z

Rahulworld: edit

== Introduction ==
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I (** [[Rahul Chauhan]] <libravatar email="rahulnitsxr@gmail.com"/> (IRC nickname: "rahulworld")) was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

== Day 1 (Reception) ==
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

== Day 2 (Full Day at Google headquarters in Mountain View) ==
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
* Recruiting – Lauren Alpizar
* Android OS: Ally Sillins
* Cloud: Ryan Matsumoto
* Chrome OS – Grant Grundler
* Google Assistant – Daniel Myers
* Google TensorFlow – Paige Bailey
We had Dinner at the same office and then head back to the hotel.

== Day 3 (Fun Day in San Francisco) ==
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

== Day 4 (Closing reception in Google SF office) ==
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

== People who made this possible ==
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

[[Category: Google Code In]]

Google Code In 2018 Grand Prize Trip

2019-08-11T11:21:21Z

Rahulworld: Create GCI 2018 Trip Report

== Introduction ==
Every year Google invites the Grand-Prize winners and their parents, and a mentor to it’s headquarters in San Francisco, California for a 4 days trip. I was offered the opportunity to go and represent OSGeo in the summit and meet these 2 brilliant folks in person. This report covers activities and other things that happened there.

I was visiting Google San Francisco, meeting with the two winner students from Google Code-In as well as the students and mentors from the 14 other organisations participating in GCI.
Our two winning students : Matthew Murzaku from the USA, and Shubham Sharma from India. Both our winners were amazing and did the tasks with great quality. I am still surprised to see their work at such a young age. I am also hoping to see them as GCI mentors or GSoC students in the future.

== Day 1 (Reception) ==
I met with Matthew and Shubham and the other students and mentors in the Hotel lobby where there was a “meet and greet” reception in the evening. Students were given a list of traits (“Did I ride bike last week”, “can speak 3 or more languages fluently”, etc) and had a few minutes to find as much students and mentors as possible matching the traits. This was a good way for the students to get to know each other and the mentors a bit. We then stayed in the hotel lobby for some discussion or hacking.

== Day 2 (Full Day at Google headquarters in Mountain View) ==
This day was special since we were going to explore Googleplex and talk to Google Engineers at Google Cloud office. We were also offered $75 and $150 to mentors and students respectively to buy our choice of Google Merchandise. Students met with Google employees of their home country and parted to have lunch with them. We had a line up of talks by great folks from Google.
* Recruiting – Lauren Alpizar
* Android OS: Ally Sillins
* Cloud: Ryan Matsumoto
* Chrome OS – Grant Grundler
* Google Assistant – Daniel Myers
* Google TensorFlow – Paige Bailey
We had Dinner at the same office and then head back to the hotel.

== Day 3 (Fun Day in San Francisco) ==
Probably the day most of us would remember. We had option to select one of Segway tour or cable car tour. We split into 2 groups for different activities. I Selected the Segway tour. We later met for lunch in a park by the sea, and boarded the bus once again to visit the Golden Gate bridge. The day ended with a Yacht course across the bay, and we could enjoy a beautiful view of San Francisco from there.

== Day 4 (Closing reception in Google SF office) ==
On the last day, we had to go the office a bit early. We had breakfast in the office itself followed by the award ceremony (to grand prize winners). We were given 4 minutes per org time to share something if we wished. A lot of students shared their experience with GCI. we shared a little intro on OSGeo projects and my GCI experience as mentor and Metthew shared his favourite task experience. We had lunch after than and meanwhile a video crew was taking interview of people who signed up for it. I and Matthew went for video interview. We had left the office by 3pm after taking a lot of pictures in front of the San Francisco – Oakland bridge.

== People who made this possible ==
Thanks to every student who participated. Everyone of you were amazing and I hope to see you all.
Thanks to [[Victoria Rautenbach]], [[Jeff McKenna]] and Michael for being there when needed, and keeping the conversation alive. A very special thanks to [[Victoria Rautenbach]] for being the backbone of this. Of course all the mentors, Thank you for giving all the time and I hope to be a part of this along with all of you in the coming years.

[[Category: Google Code In]]

Google Summer of Code 2019 Administrative

2019-08-05T04:49:30Z

Rahulworld: Added Name

<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 2019]] @ OSGeo wiki page.
* Visit our [[Google Summer of Code 2019 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 2019.

== 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 2019 GSoC site]
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]

== 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 it, you are encouraged to introduce yourself and your role. We look forward to hear 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:Madi|Margherita Di Leo]], [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], Carolina Arias Muñoz, [[Jeff McKenna]]. Feel free to email us at gsoc-admin AT osgeo DOT org with questions!

[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]
.

== Mentors ==

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please read [https://lists.osgeo.org/pipermail/discuss/2018-January/036977.html here] and fill in the form given in the link.


== 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 a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both 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 filed within these dates. There are '''3 evaluation periods''' where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). 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]

== Mentor Summit ==

Each year Google hosts the "Mentor Summit" event at their headquarters, where upto 2 OSGeo delegates can attend. The date for this year's summit is: [https://developers.google.com/open-source/gsoc/2018/mentor-oa-announcements#july_23_2018_the_2018_google_summer_of_code_mentor_summit 12-14 October 2018]. We have developed guidelines for who can represent OSGeo at the summit: see [[Google Summer of Code 2018 Mentor Summit]]

=== GCI Mentor Candidates ===
Google has recently notified the OSGeo admins that Google would like to invite 1 of the OSGeo mentors from GCI 2018 to come to the [https://sites.google.com/view/gsoc-mentorsummit2019/home GSoC 2019 Mentor Summit]. Google will add $1100 to the stipend that is sent in early September, if OSGeo decides to send a GCI mentor to the GSoC 2019 summit.

OSGeo GCI admins have agreed to open the opportunity to attend to the recent OSGeo GCI mentors, using a lottery to decide if need be. Here are the requirements:

Eligibility:
* must comply with Google requirements (must have been a 2018 GCI Mentor for OSGeo);
* must have been a mentor who participated in at least one OSGeo project task instance, working with a student (meaning that you interacted with a student on at least one instance, through the GCI Dashboard)

==== Signup Below ====

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery
* Cameron Green
* Celia Virginia Vergara Castillo (Vicky Vergara)
* Abhinav Kumar
* add your name here

==== Draw Time ====

2019-09-12 @ 15:00 UTC https://www.timeanddate.com/worldclock/fixedtime.html?msg=GSoC+summit+2019+lottery+draw&iso=20190812T15&p1=1440

== Learn more ==

* Previous years SoC involvement: [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 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 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]]

Rahul Chauhan

2019-02-14T05:59:39Z

Rahulworld:

{{OSGeo Member
|Name=Rahul Chauhan
|Address=301, Platinum Castle, 3rd main, OMBR Layout, Banswadi,
|Country=India
|State=Karnataka
|City=Banglore
|Coordinate=13.010612, 77.651509
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|College=National Institute of Technology Srinagar
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan. I am a Full Stack Developer and open source contributor.
Some more information about me can be obtained by following the link: https://rahulworld.github.io

Rahul Chauhan

2019-02-14T04:58:15Z

Rahulworld: updated

{{OSGeo Member
|Name=Rahul Chauhan
|Address=301, Platinum Castle,, 3rd main, OMBR Layout, Banswadi,
|Country=India
|State=Karnataka
|City=Banglore
|Coordinate=13.010612, 77.651509
|LocalChapter=India
|Email=rahulnitsxr@gmail.com
|Phone=+918279634070
|Website=https://rahulworld.github.io
|Photo=ProfilePhoto.jpg
|Languages=English; Hindi
|College=National Institute of Technology Srinagar
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
== Student's Biography ==
My name is Rahul Chauhan.
Some more information about me can be obtained by following the link: https://rahulworld.github.io

Google Code In 2018

2019-02-12T06:40:19Z

Rahulworld: updated

Rahul Chauhan

2019-02-12T06:35:49Z

Rahulworld: created new wiki

User:Rahulworld

2019-02-12T06:25:36Z

Rahulworld:

User:Rahulworld

2019-02-12T06:12:18Z

Rahulworld:

User:Rahulworld

2019-02-12T06:07:44Z

Rahulworld:

User:Rahulworld

2019-02-12T06:00:28Z

Rahulworld:

File:ProfilePhoto.jpg

2019-02-12T05:59:46Z

Rahulworld:

User:Rahulworld

2019-02-12T05:58:56Z

Rahulworld: