OSGeo - User contributions [en]

Cameron Green

2020-10-12T19:27:28Z

Camerongreen:

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
|Phone=+27833013201
|Website=camgreen.co.za
|Languages=English; Afrikaans;
|Info=Cameron Green is a MSc Geoinformatics student in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria and has actively been involved in OSGeo initiatives and open source technologies since 2017. In 2017, he was selected for the Faculty of Natural and Agricultural Science Undergraduate Mentorship Bursary Program under Prof Serena Coetzee and Dr Victoria Rautenbach. The mentorship bursary was awarded based on academic merit and commitment. Through the program, he assisted with various administrative and technical tasks in the departments. At University, he joined the environmental society, called The Greenline Society. He served on the Executive Council for three years as the Marketing and Publications Manager (2015), Vice-Chairperson (2016) and Chairperson and Residence Director (2017). As part of the Executive Council, he had various responsibilities, such as organised and participated events and coordinating marketing. He is currently the president of the University of Pretoria YouthMappers chapter, and has been instrumental in the arrangements of various mapathons that were held at the University of Pretoria and with school learners in Pretoria.

He was a DST/NRF intern in the Centre for Geoinformation Science under the supervision of Prof Serena Coetzee in 2018. As part of his duties, he was a teaching assistant for GIS310 (Advance GIS), GMT320 (Geoinformatics project) and GIS 311 (Geoinformatics). His main task was to manage and coordinate the practical sessions for the GIS 310 group of 120 students. For GMT 320, he assisted with administration and logistical arrangements with the community of Alaska informal settlement and presents practicals to the students. Through the internship and his honour’s project, he was involved in the Frontiers of Engineering Seed Funding project with King's College London. The aim of the project was to improve the process for collecting volunteered geographic information by interacting with hackathons. For the project, he assisted with the arrangement of mapathons and the development of a wiki for reporting on the process. Additionally, he coordinated with postgraduate students at King's College London to analyse the quality of the data. During this time, he was a facilitator in a UN OpenGIS online course on QGIS and a mentor in the annual Google Code-in.

Currently, he is working as a research assistant in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In the 2019 edition of Google Code-in Cameron was a mentor and administrator for OSGeo during this time where he coordinated directly with the participants, mentors and Google to ensure the smooth running of the competition. During his time at the University, he has assisted with and lead workshops where various open source geospatial topics were covered. He has also participated in a number of community outreach and engagement programs. At his university, Cameron is always assisting students with learning open source software and develops material for open source GIS applications that students use and works not only with Geoinformatics students but also students from other degrees. Later this year (2020), Cameron will again be a facilitator in a UN OpenGIS online course on PostGIS.

His current research is an international collaboration between the South African National Research Foundation (NRF) and the Swedish STINT. The focus of this study was to build a collaborative data library for the sharing of fine-grained spatial and non-spatial data. This was achieved by building and configuring a customized GeoNode instance.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Cameron Green

2020-10-12T16:37:36Z

Camerongreen:

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
|Phone=+27833013201
|Website=camgreen.co.za
|Languages=English; Afrikaans;
|Info=Cameron Green is a MSc Geoinformatics student in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In 2017, he was selected for the Faculty of Natural and Agricultural Science Undergraduate Mentorship Bursary Program under Prof Serena Coetzee and Dr Victoria Rautenbach. The mentorship bursary was awarded based on academic merit and commitment. Through the program, he assisted with various administrative and technical tasks in the departments. At University, he joined the environmental society, called The Greenline Society. He served on the Executive Council for three years as the Marketing and Publications Manager (2015), Vice-Chairperson (2016) and Chairperson and Residence Director (2017). As part of the Executive Council, he had various responsibilities, such as organised and participated events and coordinating marketing. He is currently the president of the University of Pretoria YouthMappers chapter, and has been instrumental in the arrangements of various mapathons that were held at the University of Pretoria and with school learners in Pretoria.

He was a DST/NRF intern in the Centre for Geoinformation Science under the supervision of Prof Serena Coetzee in 2018. As part of his duties, he was a teaching assistant for GIS310 (Advance GIS), GMT320 (Geoinformatics project) and GIS 311 (Geoinformatics). His main task was to manage and coordinate the practical sessions for the GIS 310 group of 120 students. For GMT 320, he assisted with administration and logistical arrangements with the community of Alaska informal settlement and presents practicals to the students. Through the internship and his honour’s project, he was involved in the Frontiers of Engineering Seed Funding project with King's College London. The aim of the project was to improve the process for collecting volunteered geographic information by interacting with hackathons. For the project, he assisted with the arrangement of mapathons and the development of a wiki for reporting on the process. Additionally, he coordinated with postgraduate students at King's College London to analyse the quality of the data. During this time, he was a facilitator in a UN OpenGIS online course on QGIS and a mentor in the annual Google Code-in.

Currently, he is working as a research assistant in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In the 2019 edition of Google Code-in Cameron was a mentor and administrator for OSGeo during this time where he coordinated directly with the participants, mentors and Google to ensure the smooth running of the competition. During his time at the University, he has assisted with and lead workshops where various open source geospatial topics were covered. He has also participated in a number of community outreach and engagement programs. At his university, Cameron is always assisting students with learning open source software and develops material for open source GIS applications that students use and works not only with Geoinformatics students but also students from other degrees. Later this year (2020), Cameron will again be a facilitator in a UN OpenGIS online course on PostGIS.

His current research is an international collaboration between the South African National Research Foundation (NRF) and the Swedish STINT. The focus of this study was to build a collaborative data library for the sharing of fine-grained spatial and non-spatial data. This was achieved by building and configuring a customized GeoNode instance.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Cameron Green

2020-10-12T16:18:12Z

Camerongreen:

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
|Phone=+27833013201
|Website=camgreen.co.za
|Languages=English; Afrikaans;
|Info=Cameron Green is a MSc Geoinformatics student in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In 2017, he was selected for the Faculty of Natural and Agricultural Science Undergraduate Mentorship Bursary Program under Prof Serena Coetzee and Dr Victoria Rautenbach. The mentorship bursary was awarded based on academic merit and commitment. Through the program, he assisted with various administrative and technical tasks in the departments. At University, he joined the environmental society, called The Greenline Society. He served on the Executive Council for three years as the Marketing and Publications Manager (2015), Vice-Chairperson (2016) and Chairperson and Residence Director (2017). As part of the Executive Council, he had various responsibilities, such as organised and participated events and coordinating marketing. He is currently the president of the University of Pretoria YouthMappers chapter, and has been instrumental in the arrangements of various mapathons that were held at the University of Pretoria and with school learners in Pretoria.

He was a DST/NRF intern in the Centre for Geoinformation Science under the supervision of Prof Serena Coetzee in 2018. As part of his duties, he was a teaching assistant for GIS310 (Advance GIS), GMT320 (Geoinformatics project) and GIS 311 (Geoinformatics). His main task was to manage and coordinate the practical sessions for the GIS 310 group of 120 students. For GMT 320, he assisted with administration and logistical arrangements with the community of Alaska informal settlement and presents practicals to the students. Through the internship and his honour’s project, he was involved in the Frontiers of Engineering Seed Funding project with King's College London. The aim of the project was to improve the process for collecting volunteered geographic information by interacting with hackathons. For the project, he assisted with the arrangement of mapathons and the development of a wiki for reporting on the process. Additionally, he coordinated with postgraduate students at King's College London to analyse the quality of the data. During this time, he was a facilitator in a UN OpenGIS online course on QGIS and a mentor in the annual Google Code-in.

Currently, he is working as a research assistant in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In the 2019 edition of Google Code-in Cameron was a mentor and administrator for OSGeo during this time where he coordinated directly with the participants, mentors and Google to ensure the smooth running of the competition. During his time at the University, he has assisted with and lead workshops where various geospatial topics were covered. He has also participated in a number of community outreach and engagement programs. At his university, Cameron is always assisting students with learning open source software and works not only with Geoinformatics students but also students from other degrees. Later this year (2020), Cameron will again be a facilitator in a UN OpenGIS online course on PostGIS.

His current research is an international collaboration between the South African National Research Foundation (NRF) and the Swedish STINT. The focus of this study was to build a collaborative data library for the sharing of fine-grained spatial and non-spatial data. This was achieved by building and configuring a customized GeoNode instance.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Google Code In 2019 Results Press Release

2020-02-19T08:35:10Z

Camerongreen:

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

=== Title: Announcing OSGeo’s 2019 Google Code-in winners ===

Google Code-in (GCI) is an annual online competition aimed at introducing pre-university students (13-17 years old) to open source projects, development and communities, through short 3-5 hour tasks [1]. As opposed to the Google Summer of Code program, in GCI students are not selected by the organizations, but freely pick up tasks from one or more mentoring organizations and complete them. Students qualify for different prizes (i.e. certificate, t-shirts, hoodies and the grand prize of visiting Google’s main headquarters in San Francisco) depending on the number of tasks they complete. During GCI, OSGeo project members have a unique opportunity to interact with pre-university students and to encourage them to become part of their respective projects.

The OSGeo team consisted of 16 community members that contributed 110 tasks from 11 projects (e.g. istSOS, GRASS GIS, GeoServer, pgRouting, PostGIS, GeoNode and OpenLayers) and also OSGeo, FOSS4G and GeoForAll.

The 2019 Google Code-in (GCI) took place 2 December 2019 - 21 January 2020 and OSGeo had 401 students that completed a task with us. These 401 students completed 976 tasks [2] which is the most amount of completed tasks to date for OSGeo! This is an improvement from last year and this can be contributed to the change in dates of the competition going back to the original dates. The completed tasks range from designing badges for the OSGeo website, to tests for GRASS GIS, or bug fixes for PostGIS. These tasks might seem simplistic in some cases, but the combined results are of great value to OSGeo.

[[Image:OSGeo_GCI_2019_Winners.png|thumb|right|333px|2019 GCI finalists for OSGeo]]

OSGeo is pleased to announce the 2019 Google Code-in Grand Prize winners, who each receive a free trip to Google headquarters in California, along with a parent/guardian, are students (note that these are the student’s account names, due to privacy concerns):

OSGeo’s Google Code-in Winners:
• Navya Garg
• Pranay

OSGeo’s Google Code-in Runners Up:
• Dhanus SL
• Lucifer

OSGeo’s Google Code-in finalists (who receive Google hoodies) are:
• TanvirSingh
• anishagnihotri

See here: https://codein.withgoogle.com/winners/#winners the winners from all organisations [3].

Congratulations to the winners and finalists! But also a special congratulations to all students that received a certificate and/or t-shirt. We greatly appreciate your contribution to OSGeo!

Lastly, thank you to the OSGeo mentors for the time they spent on the tasks and mentoring the students. Without your commitment this would not have been possible.

Thank you to everyone involved, mentors and students.

Regards,
OSGeo GCI admins 2019

Links:

[1] https://codein.withgoogle.com

[2] https://codein.withgoogle.com/tasks/?sp-search=OSGeo

[3] https://codein.withgoogle.com/winners/#winners

[[Category:Google Code In]]

File:OSGeo GCI 2019 Winners.png

2020-02-19T08:34:45Z

Camerongreen:

Google Code In 2019 Results Press Release

2020-02-19T08:32:43Z

Camerongreen:

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

=== Title: Announcing OSGeo’s 2019 Google Code-in winners ===

Google Code-in (GCI) is an annual online competition aimed at introducing pre-university students (13-17 years old) to open source projects, development and communities, through short 3-5 hour tasks [1]. As opposed to the Google Summer of Code program, in GCI students are not selected by the organizations, but freely pick up tasks from one or more mentoring organizations and complete them. Students qualify for different prizes (i.e. certificate, t-shirts, hoodies and the grand prize of visiting Google’s main headquarters in San Francisco) depending on the number of tasks they complete. During GCI, OSGeo project members have a unique opportunity to interact with pre-university students and to encourage them to become part of their respective projects.

The OSGeo team consisted of 16 community members that contributed 110 tasks from 11 projects (e.g. istSOS, GRASS GIS, GeoServer, pgRouting, PostGIS, GeoNode and OpenLayers) and also OSGeo, FOSS4G and GeoForAll.

The 2019 Google Code-in (GCI) took place 2 December 2019 - 21 January 2020 and OSGeo had 401 students that completed a task with us. These 401 students completed 976 tasks [2] which is the most amount of completed tasks to date for OSGeo! This is an improvement from last year and this can be contributed to the change in dates of the competition going back to the original dates. The completed tasks range from designing badges for the OSGeo website, to tests for GRASS GIS, or bug fixes for PostGIS. These tasks might seem simplistic in some cases, but the combined results are of great value to OSGeo.

[[Image:GCI-2017-results.png|thumb|right|333px|2019 GCI finalists for OSGeo]]

OSGeo is pleased to announce the 2019 Google Code-in Grand Prize winners, who each receive a free trip to Google headquarters in California, along with a parent/guardian, are students (note that these are the student’s account names, due to privacy concerns):

OSGeo’s Google Code-in Winners:
• Navya Garg
• Pranay

OSGeo’s Google Code-in Runners Up:
• Dhanus SL
• Lucifer

OSGeo’s Google Code-in finalists (who receive Google hoodies) are:
• TanvirSingh
• anishagnihotri

See here: https://codein.withgoogle.com/winners/#winners the winners from all organisations [3].

Congratulations to the winners and finalists! But also a special congratulations to all students that received a certificate and/or t-shirt. We greatly appreciate your contribution to OSGeo!

Lastly, thank you to the OSGeo mentors for the time they spent on the tasks and mentoring the students. Without your commitment this would not have been possible.

Thank you to everyone involved, mentors and students.

Regards,
OSGeo GCI admins 2019

Links:

[1] https://codein.withgoogle.com

[2] https://codein.withgoogle.com/tasks/?sp-search=OSGeo

[3] https://codein.withgoogle.com/winners/#winners

[[Category:Google Code In]]

Google Code In 2019 Results Press Release

2020-02-19T08:31:58Z

Camerongreen:

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

=== Title: Announcing OSGeo’s 2019 Google Code-in winners ===

Google Code-in (GCI) is an annual online competition aimed at introducing pre-university students (13-17 years old) to open source projects, development and communities, through short 3-5 hour tasks [1]. As opposed to the Google Summer of Code program, in GCI students are not selected by the organizations, but freely pick up tasks from one or more mentoring organizations and complete them. Students qualify for different prizes (i.e. certificate, t-shirts, hoodies and the grand prize of visiting Google’s main headquarters in San Francisco) depending on the number of tasks they complete. During GCI, OSGeo project members have a unique opportunity to interact with pre-university students and to encourage them to become part of their respective projects.

The OSGeo team consisted of 16 community members that contributed 110 tasks from 11 projects (e.g. istSOS, GRASS GIS, GeoServer, pgRouting, PostGIS, GeoNode and OpenLayers) and also OSGeo, FOSS4G and GeoForAll.

The 2019 Google Code-in (GCI) took place 2 December 2019 - 21 January 2020 and OSGeo had 401 students that completed a task with us. These 401 students completed 976 tasks [2] which is the most amount of completed tasks to date for OSGeo! This is an improvement from last year and this can be contributed to the change in dates of the competition going back to the original dates. The completed tasks range from designing badges for the OSGeo website, to tests for GRASS GIS, or bug fixes for PostGIS. These tasks might seem simplistic in some cases, but the combined results are of great value to OSGeo.

[[Image:GCI-2017-results.png|thumb|right|333px|2017/2018 GCI finalists for OSGeo]]

OSGeo is pleased to announce the 2019 Google Code-in Grand Prize winners, who each receive a free trip to Google headquarters in California, along with a parent/guardian, are students (note that these are the student’s account names, due to privacy concerns):

OSGeo’s Google Code-in Winners:
• Navya Garg
• Pranay

OSGeo’s Google Code-in Runners Up:
• Dhanus SL
• Lucifer

OSGeo’s Google Code-in finalists (who receive Google hoodies) are:
• TanvirSingh
• anishagnihotri

See here: https://codein.withgoogle.com/winners/#winners the winners from all organisations [3].

Congratulations to the winners and finalists! But also a special congratulations to all students that received a certificate and/or t-shirt. We greatly appreciate your contribution to OSGeo!

Lastly, thank you to the OSGeo mentors for the time they spent on the tasks and mentoring the students. Without your commitment this would not have been possible.

Thank you to everyone involved, mentors and students.

Regards,
OSGeo GCI admins 2019

Links:

[1] https://codein.withgoogle.com

[2] https://codein.withgoogle.com/tasks/?sp-search=OSGeo

[3] https://codein.withgoogle.com/winners/#winners

[[Category:Google Code In]]

Google Code In 2019 Results Press Release

2020-02-19T08:31:19Z

Camerongreen:

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

=== Title: Announcing OSGeo’s 2019 Google Code-in winners ===

Google Code-in (GCI) is an annual online competition aimed at introducing pre-university students (13-17 years old) to open source projects, development and communities, through short 3-5 hour tasks [1]. As opposed to the Google Summer of Code program, in GCI students are not selected by the organizations, but freely pick up tasks from one or more mentoring organizations and complete them. Students qualify for different prizes (i.e. certificate, t-shirts, hoodies and the grand prize of visiting Google’s main headquarters in San Francisco) depending on the number of tasks they complete. During GCI, OSGeo project members have a unique opportunity to interact with pre-university students and to encourage them to become part of their respective projects.

The OSGeo team consisted of 16 community members that contributed 110 tasks from 11 projects (e.g. istSOS, GRASS GIS, GeoServer, pgRouting, PostGIS, GeoNode and OpenLayers) and also OSGeo, FOSS4G and GeoForAll.

The 2019 Google Code-in (GCI) took place 2 December 2019 - 21 January 2020 and OSGeo had 401 students that completed a task with us. These 401 students completed 976 tasks [2] which is the most amount of completed tasks to date for OSGeo! This is an improvement from last year and this can be contributed to the change in dates of the competition going back to the original dates. The completed tasks range from designing badges for the OSGeo website, to tests for GRASS GIS, or bug fixes for PostGIS. These tasks might seem simplistic in some cases, but the combined results are of great value to OSGeo.

[[Image:GCI-2017-results.png|thumb|right|333px|2017/2018 GCI finalists for OSGeo]]

OSGeo is pleased to announce the 2019 Google Code-in Grand Prize winners, who each receive a free trip to Google headquarters in California, along with a parent/guardian, are students (note that these are the student’s account names, due to privacy concerns):

OSGeo’s Google Code-in Winners:
• Navya Garg
• Pranay

OSGeo’s Google Code-in Runners Up:
• Dhanus SL
• Lucifer

OSGeo’s Google Code-in finalists (who receive Google hoodies) are:
• TanvirSingh
• anishagnihotri

See here: https://codein.withgoogle.com/winners/#winners the winners from all organisations [3].

Congratulations to the winners and finalists! But also a special congratulations to all students that received a certificate and/or t-shirt. We greatly appreciate your contribution to OSGeo!

Lastly, thank you to the OSGeo mentors for the time they spent on the tasks and mentoring the students. Without your commitment this would not have been possible.

Thank you to everyone involved, mentors and students.

Regards,
OSGeo GCI admins 2019

Links:
[1] https://codein.withgoogle.com
[2] https://codein.withgoogle.com/tasks/?sp-search=OSGeo
[3] https://codein.withgoogle.com/winners/#winners

[[Category:Google Code In]]

Google Code In 2019 Mentors

2020-02-07T06:52:33Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria dot rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Rahul Chauhan || rahulnitsxr at gmail dot com || India || GSoC 2018 student, istSOS
|-
| 3 || Frikan Erwee || ferwee at gmail dot com || South Africa || PostGIS
|-
| 4 || Cameron Green || cameron dot green at tuks dot co dot za || South Africa || GCI 2018
|-
| 5 || Aditya Pratap Singh || adityapratap dot singh28 at gmail dot com || India || pgRouting
|-
| 6 || Xuri Gong || xurigoong at gmail dot com || China || PostGIS
|-
| 7 || Abhinav Kumar || abby37kapoor at gmail dot com || India || istSOS, FOSS4G
|-
| 8 || Luqmaan Hassim || luqmaanhassim1 at gmail dot com || South Africa || GeoForAll
|-
| 9 || Daniel Kastl || daniel at georepublic dot de || Japan || pgRouting
|-
| 10 || Azile Mdleleni || u15099832 at tuks dot co dot za || South Africa || GeoForAll
|-
| 11 || Vicky Vergara Castillo || vicky at georepublic dot de || Mexico || pgRouting
|-
| 12 || Sunveer Singh || singhsunveer54 at gmail dot com || India || Former GCI Winner
|-
| 13 || Martha Carmen Vergara Trejo || mcvtkalli at gmail dot com || Mexico || pgRouting
|-
| 14 || Felicity Brand || felicitybrand at gmail dot com || Australia || OSGeoLive
|-
| 15 || Hang Wu || nike0good at gmail dot com || China || pgRouting
|-
| 16 || Rajat Shinde || rajatshinde2303 at gmail dot com || || pgRouting
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019

2020-02-02T11:11:01Z

Camerongreen: /* Mentor Representation at the Grand Prize Winners Trip */

Google Code In 2019

2020-01-28T17:39:24Z

Camerongreen: /* Mentor Representation at the Grand Prize Winners Trip */

Google Code In 2019

2020-01-28T17:38:25Z

Camerongreen: /* Mentor Representation at the Grand Prize Winners Trip */

Google Code In 2019 Application

2019-10-31T08:56:56Z

Camerongreen: /* Contact Methods */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

== Contact Methods ==

* '''Chat (Link to a web page that describes how to access your realtime chat):''' https://gitter.im/OSGeo-GCI/community

* '''Mailing list (Link to a page describing how to join your organization's mailing list):''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization):''' gci-osgeo at googlegroups dot com

* '''Twitter URL:''' https://twitter.com/osgeo

== Extra Task Information ==

* '''Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions):''' Don't forget to join the OSGeo-GCI Gitter channel to ask mentors questions directly in your browser through: https://www.osgeo.org/community/communications/

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2019#Communication

[Back to [[Google Code In 2019]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T08:12:57Z

Camerongreen: /* Contact Methods */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

== Contact Methods ==

* '''Chat (Link to a web page that describes how to access your realtime chat):''' https://gitter.im/OSGeo-GCI/community

* '''Mailing list (Link to a page describing how to join your organization's mailing list):''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization):''' 

* '''Twitter URL:''' https://twitter.com/osgeo

== Extra Task Information ==

* '''Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions):''' Don't forget to join the OSGeo-GCI Gitter channel to ask mentors questions directly in your browser through: https://www.osgeo.org/community/communications/

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2019#Communication

[Back to [[Google Code In 2019]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:26:30Z

Camerongreen: /* Extra Task Information */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

== Contact Methods ==

* '''Chat (Link to a web page that describes how to access your realtime chat):''' https://gitter.im/OSGeo-GCI/community

* '''Mailing list (Link to a page describing how to join your organization's mailing list):''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization):''' gci-osgeo at googlegroups dot com

* '''Twitter URL:''' https://twitter.com/osgeo

== Extra Task Information ==

* '''Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions):''' Don't forget to join the OSGeo-GCI Gitter channel to ask mentors questions directly in your browser through: https://www.osgeo.org/community/communications/

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2019#Communication

[Back to [[Google Code In 2019]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:24:09Z

Camerongreen: /* Contact Methods */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

== Contact Methods ==

* '''Chat (Link to a web page that describes how to access your realtime chat):''' https://gitter.im/OSGeo-GCI/community

* '''Mailing list (Link to a page describing how to join your organization's mailing list):''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization):''' gci-osgeo at googlegroups dot com

* '''Twitter URL:''' https://twitter.com/osgeo

== Extra Task Information ==

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:23:07Z

Camerongreen:

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

== Contact Methods ==

* '''Chat (Link to a web page that describes how to access your realtime chat)''' https://gitter.im/OSGeo-GCI/community

* '''Mailing list (Link to a page describing how to join your organization's mailing list)''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization)''' gci-osgeo at googlegroups dot com

* '''Twitter URL''' https://twitter.com/osgeo

== Extra Task Information ==

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:15:39Z

Camerongreen: /* Profile */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Public Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

* '''Chat (Link to a web page that describes how to access your realtime chat)''' https://wiki.osgeo.org/wiki/IRC

* '''Mailing list (Link to a page describing how to join your organization's mailing list)''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization)''' gci-admin at osgeo.org

* '''Google+ URL''' https://plus.google.com/communities/105969056638310510633

* '''Twitter URL''' https://twitter.com/osgeo

* '''Blog URL''' http://planet.osgeo.org/

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:14:46Z

Camerongreen: /* Application Questions */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== General Information ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Profile ==



[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:12:31Z

Camerongreen: /* Application Questions */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks

== Profile ==



[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:11:23Z

Camerongreen: /* Application Questions */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==

* '''Why does your organization want to participate in Google Code-in 2019? (500 character limit)''' After participating in GCI the past two years, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2019_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2019_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2018 & 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2019

* '''How many mentors have committed to participate?''' 14

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks

== Profile ==



[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-31T07:10:56Z

Camerongreen:

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==



== Profile ==



[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-24T11:03:16Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria dot rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Rahul Chauhan || rahulnitsxr at gmail dot com || India || GSoC 2018 student, istSOS
|-
| 3 || Frikan Erwee || ferwee at gmail dot com || South Africa || PostGIS
|-
| 4 || Cameron Green || cameron dot green at tuks dot co dot za || South Africa || GCI 2018
|-
| 5 || Aditya Pratap Singh || adityapratap dot singh28 at gmail dot com || India || pgRouting
|-
| 6 || Besfort Guri || besiguri at gmail dot com || Kosovo || QGIS, Geoserver
|-
| 7 || Abhinav Kumar || abby37kapoor at gmail dot com || India || istSOS, FOSS4G
|-
| 8 || Luqmaan Hassim || luqmaanhassim1 at gmail dot com || South Africa || GeoForAll
|-
| 9 || Daniel Kastl || daniel at georepublic dot de || Japan || pgRouting
|-
| 10 || Azile Mdleleni || u15099832 at tuks dot co dot za || South Africa || GeoForAll
|-
| 11 || Vicky Vergara Castillo || vicky at georepublic dot de || Mexico || pgRouting
|-
| 12 || Sunveer Singh || singhsunveer54 at gmail dot com || India || Former GCI Winner
|-
| 13 || Martha Carmen Vergara Trejo || mcvtkalli at gmail dot com || Mexico || pgRouting
|-
| 14 || Anurag Anand || anandhind235 at gmail dot com || India || istSOS
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Cameron Green

2019-10-24T10:57:10Z

Camerongreen:

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
|Website=camcode.xyz
|Languages=English; Afrikaans;
|Info=Cameron Green is a MSc Geoinformatics student in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In 2017, he was selected for the Faculty of Natural and Agricultural Science Undergraduate Mentorship Bursary Program under Prof Serena Coetzee and Dr Victoria Rautenbach. The mentorship bursary was awarded based on academic merit and commitment. Through the program, he assisted with various administrative and technical tasks in the departments. At University, he joined the environmental society, called The Greenline Society. He served on the Executive Council for three years as the Marketing and Publications Manager (2015), Vice-Chairperson (2016) and Chairperson and Residence Director (2017). As part of the Executive Council, he had various responsibilities, such as organised and participated events and coordinating marketing. During his term on Greenline, he was privileged to receive two awards on behalf of the University of Pretoria for the work that Greenline has done. Greenline was also nominated for the Talloires Network MacJannet Prize for the work done in 2017. He is currently the president of the University of Pretoria YouthMappers chapter, and has been instrumental in the arrangements of various mapathons that were held at the University of Pretoria and with school learners in Pretoria. He was a DST/NRF intern in the Centre for Geoinformation Science under the supervision of Prof Serena Coetzee. As part of his duties, he is a teaching assistant for GIS310 (Advance GIS), GMT320 (Geoinformatics project) and GIS 311 (Geoinformatics). His main task is to manage and coordinate the practical sessions for the GIS 310 group of 120 students. For GMT 320, he assists with administration and logistical arrangements with the community of Alaska informal settlement and presents practicals to the students. Through the internship and his honour’s project, he is involved in the Frontiers of Engineering Seed Funding project with King's College London. The aim of the project is to improve the process for collecting volunteered geographic information by interacting with hackathons. For the project, he has assisted with the arrangement of mapathons and the development of a wiki for reporting on the process. Additionally, he coordinates with postgraduate students at King's College London to analyse the quality of the data. During this time, he was a facilitator in a UN OpenGIS online course and a mentor in the annual Google Code-in. Currently, he is working as a research assistant in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Google Code In 2019 Mentors

2019-10-23T13:11:06Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria dot rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Rahul Chauhan || rahulnitsxr at gmail dot com || India || GSoC 2018 student, istSOS
|-
| 3 || Frikan Erwee || ferwee at gmail dot com || South Africa || PostGIS
|-
| 4 || Cameron Green || cameron dot green at tuks dot co dot za || South Africa || GCI 2018
|-
| 5 || Aditya Pratap Singh || adityapratap dot singh28 at gmail dot com || India || pgRouting
|-
| 6 || Besfort Guri || besiguri at gmail dot com || Kosovo || QGIS, Geoserver
|-
| 7 || Abhinav Kumar || abby37kapoor at gmail dot com || India || istSOS, FOSS4G
|-
| 8 || Luqmaan Hassim || luqmaanhassim1 at gmail dot com || South Africa || GeoForAll
|-
| 9 || Daniel Kastl || daniel at georepublic dot de || Japan || pgRouting
|-
| 10 || Azile Mdleleni || u15099832 at tuks dot co dot za || South Africa || GeoForAll
|-
| 11 || Sunveer Singh || singhsunveer54 at gmail dot com || India || Former GCI Winner
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-23T12:54:01Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria dot rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Rahul Chauhan || rahulnitsxr at gmail dot com || India || GSoC 2018 student, istSOS
|-
| 3 || Frikan Erwee || ferwee at gmail dot com || South Africa || PostGIS
|-
| 4 || Cameron Green || cameron dot green at tuks dot co dot za || South Africa || GCI 2018
|-
| 5 || Aditya Pratap Singh || adityapratap dot singh28 at gmail dot com || India || pgRouting
|-
| 6 || Besfort Guri || besiguri at gmail dot com || Kosovo || QGIS, Geoserver
|-
| 7 || Abhinav Kumar || abby37kapoor at gmail dot com || India || istSOS, FOSS4G
|-
| 8 || Luqmaan Hassim || luqmaanhassim1 at gmail dot com || South Africa || GeoForAll
|-
| 9 || Daniel Kastl || daniel at georepublic dot de || Japan || pgRouting
|-
| 10 || Azile Mdleleni || u15099832 at tuks dot co dot za || South Africa || GeoForAll
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-16T11:51:55Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria.rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Rahul Chauhan || rahulnitsxr at gmail dot com || India || GSoC 2018 student, istSOS
|-
| 3 || Frikan Erwee || ferwee at gmail dot com || South Africa || PostGIS
|-
| 4 || Cameron Green || cameron.green at tuks dot co dot za || South Africa || GCI 2018
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-16T11:47:15Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || Victoria Rautenbach || victoria.rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 2 || Victoria Rautenbach || victoria.rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 3 || Victoria Rautenbach || victoria.rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
| 4 || Victoria Rautenbach || victoria.rautenbach at gmail dot com || South Africa || GCI 2017 & 2018
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-16T10:48:17Z

Camerongreen: /* Mentors */

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 |Victoria Rautenbach| |victoria.rautenbach at gmail dot com| |South Africa| |GCI 2017 & 2018|
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019

2019-10-16T09:25:36Z

Camerongreen: /* Administrators */

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



Central page for administering OSGeo participation in Google Code In 2019

= Background =

* Google Code In program has been [https://opensource.googleblog.com/2019/10/google-code-in-2019-org-applications.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 2018 contest [https://codein.withgoogle.com/archive/2018/organization/5912217769738240/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]
* Oct 10 2019: Organizations can start drafting application to be mentoring organizations
* Oct 28 2019: Application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 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)
* Oct 29 2019: Mentoring organizations announced
* Dec 2 2019: Contest opens for entries by student participants ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191202T18&p1=1440 exact time])
* Jan 21 2020: Deadline for students to claim new tasks ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200121T18&p1=1440 exact time])
* Jan 23 2020: All student work must be submitted; contest ends ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200123T18&p1=1440 exact time])
* Jan 24 2020: Mentoring organizations complete all evaluations of students’ work ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200124T18&p1=1440 exact time])
* Jan 30 2020: Mentoring organizations submit list of Winners and Finalists ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200130T18&p1=1440 exact time])
* Feb 10 2020: 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 2019 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)
* Gitter (requires a Github account), https://gitter.im/OSGeo-GCI/community
* Google's "Code-in Discuss" forum (mostly for general program questions, monitored by Google staff): https://groups.google.com/forum/#!forum/gci-discuss

= Administrators =

* [[Victoria Rautenbach]] <libravatar email="victoria.rautenbach@gmail.com"/> (IRC nickname: "vrautenbach")
* [[Rahul Chauhan]] <libravatar email="rahulnitsxr@gmail.com"/> (IRC nickname: "rahulworld")
* [[Cameron Green]] <libravatar email="cameron.green@tuks.co.za"/> (IRC nickname: "CamGreen")
* [[Frikan Erwee]] <libravatar email="ferwee@gmail.com"/> (IRC nickname: "FrikanRw")
''Contact OSGeo's administrators: gci-admin at osgeo dot org''

= Interested mentors / volunteers =

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

= Recommendations for Students =

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

= Tasks =

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

= Application =

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

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


= 2017 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2017

= 2018 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2018
[[Category:Google Code In]]

Cameron Green

2019-10-16T09:23:55Z

Camerongreen:

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
|Website=cam code.xyz
|Languages=English; Afrikaans;
|Info=Cameron Green is a MSc Geoinformatics student in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria. In 2017, he was selected for the Faculty of Natural and Agricultural Science Undergraduate Mentorship Bursary Program under Prof Serena Coetzee and Dr Victoria Rautenbach. The mentorship bursary was awarded based on academic merit and commitment. Through the program, he assisted with various administrative and technical tasks in the departments. At University, he joined the environmental society, called The Greenline Society. He served on the Executive Council for three years as the Marketing and Publications Manager (2015), Vice-Chairperson (2016) and Chairperson and Residence Director (2017). As part of the Executive Council, he had various responsibilities, such as organised and participated events and coordinating marketing. During his term on Greenline, he was privileged to receive two awards on behalf of the University of Pretoria for the work that Greenline has done. Greenline was also nominated for the Talloires Network MacJannet Prize for the work done in 2017. He is currently the president of the University of Pretoria YouthMappers chapter, and has been instrumental in the arrangements of various mapathons that were held at the University of Pretoria and with school learners in Pretoria. He was a DST/NRF intern in the Centre for Geoinformation Science under the supervision of Prof Serena Coetzee. As part of his duties, he is a teaching assistant for GIS310 (Advance GIS), GMT320 (Geoinformatics project) and GIS 311 (Geoinformatics). His main task is to manage and coordinate the practical sessions for the GIS 310 group of 120 students. For GMT 320, he assists with administration and logistical arrangements with the community of Alaska informal settlement and presents practicals to the students. Through the internship and his honour’s project, he is involved in the Frontiers of Engineering Seed Funding project with King's College London. The aim of the project is to improve the process for collecting volunteered geographic information by interacting with hackathons. For the project, he has assisted with the arrangement of mapathons and the development of a wiki for reporting on the process. Additionally, he coordinates with postgraduate students at King's College London to analyse the quality of the data. During this time, he was a facilitator in a UN OpenGIS online course and a mentor in the annual Google Code-in. Currently, he is working as a research assistant in the Department of Geography, Geoinformatics and Meteorology at the University of Pretoria.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Cameron Green

2019-10-16T09:01:53Z

Camerongreen: Created page with "{{OSGeo Member |Name=Cameron Green |JobTitle=Research Assistant |Company=University of Pretoria |Country=South Africa |City=Pretoria |Coordinate=25.7545° S, 28.2314° E |Loca..."

{{OSGeo Member
|Name=Cameron Green
|JobTitle=Research Assistant
|Company=University of Pretoria
|Country=South Africa
|City=Pretoria
|Coordinate=25.7545° S, 28.2314° E
|LocalChapter=Africa Local Chapter
|Email=cameron.green@tuks.co.za
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
[[Category:OSGeo_Advocate]]

Google Code In 2019

2019-10-16T07:44:25Z

Camerongreen: /* Kickoff (virtual) meeting */

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



Central page for administering OSGeo participation in Google Code In 2019

= Background =

* Google Code In program has been [https://opensource.googleblog.com/2019/10/google-code-in-2019-org-applications.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 2018 contest [https://codein.withgoogle.com/archive/2018/organization/5912217769738240/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]
* Oct 10 2019: Organizations can start drafting application to be mentoring organizations
* Oct 28 2019: Application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 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)
* Oct 29 2019: Mentoring organizations announced
* Dec 2 2019: Contest opens for entries by student participants ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191202T18&p1=1440 exact time])
* Jan 21 2020: Deadline for students to claim new tasks ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200121T18&p1=1440 exact time])
* Jan 23 2020: All student work must be submitted; contest ends ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200123T18&p1=1440 exact time])
* Jan 24 2020: Mentoring organizations complete all evaluations of students’ work ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200124T18&p1=1440 exact time])
* Jan 30 2020: Mentoring organizations submit list of Winners and Finalists ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200130T18&p1=1440 exact time])
* Feb 10 2020: 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 2019 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 =

* [[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 2019 Mentors]]

= Recommendations for Students =

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

= Tasks =

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

= Application =

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

= Communication Platform =

* This year, OSGeo is going to use Gitter.im
* Please search for the Channel 'OSGeo-GCI' or follow this link: https://gitter.im/OSGeo-GCI/community?utm_source=share-link&utm_medium=link&utm_campaign=share-link
* You are required to have a valid Github account in order to join the channel

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


= 2017 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2017

= 2018 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2018
[[Category:Google Code In]]

Google Code In 2019 Tasks

2019-10-15T12:11:16Z

Camerongreen: /* Example Tasks */

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

= Interested Mentors =

Please '''first fill out the Google form''' mentioned at the top of: [[Google Code In 2019 Mentors]]

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;Design
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* OSGeo's 2017 tasks: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/
* OSGeo's 2018 tasks: https://codein.withgoogle.com/archive/2018/organization/5912217769738240/task/
* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

* see shared spreadsheet on Google Drive

= Bulk Uploading Tasks =

'''Documentation'''

* [https://code.googlesource.com/codein/api API]

'''Prep'''

NOTE: the python scripts for bulk uploading are written for Python2, but the instructions below should work for both Python2 & 3:

# git clone https://code.googlesource.com/codein/api api
# cd api
# check your Python version:
#* <code>python -V</code>
# install module "requests" through easy_install or pip:
#* <code>easy_install requests</code>
#* <code>pip install requests</code>
# for Python2, no more changes are needed, proceed to next sections below (export tasks, or list tasks, or upload tasts, etc)
# for Python3, make the following changes:
#* in ''list_tasks.py'' change print command on line# 45 to
#** <code>print ('\t'.join([str(t['id']), t['name']]))</code>
#* in ''list_tasks.py'' convert to an int on line# 52 to
#** <code>next_page = int(result.group(1))</code>
#* in ''csv_uploader.py'' change line# 64 to
#** <code>with open(filename, 'rt') as csvfile:</code>
#* in ''csv_uploader.py'' change print command on line# 83 to
#** <code>print ('\t'.join(['OK', str(t['id']), t['name'], '']))</code>
#* in ''csv_uploader.py'' change print command on line# 86 to
#** <code>print ('\t'.join(['ERROR', '', t['name'], e.response.text]))</code>
#* in ''client.py'' change instances of "urlparse" to "urllib.parse"

'''Export CSV'''

* export your tasks from the Google spreadsheet (assuming you created a new sheet in the shared doc ''Code-in Bulk Upload Spreadsheet'') as CSV (File/Download as/CSV), but before that be sure to:
** make sure that the '''"categories" field''' is comma separated '''INTEGERs''' (see the "column definitions" sheet in ''Code-in Bulk Upload Spreadsheet'')
** verify that your dashboard '''PROFILE email address''' is the EXACT same as what you entered in the '''"mentors" field''' in 'Code-in Bulk Upload Spreadsheet' (otherwise your uploaded tasks will have empty/missing mentor)

'''List Tasks through Commandline'''

# see usage of list_tasks.py
#* <code>python list_tasks.py --help</code>
# get a list of tasks at the commandline
#* <code>python list_tasks.py --apikey [OSGeoKey]'''</code>
#** should return something like:
<pre>
5126447435874304 gvSIG: Make a .....
5172599543824384 gvSIG: Install.....
5702068213907456 MapServer: Find and fix ....
5723293673848832 gvSIG: Make a ....
5761046167945216 gvSIG: Give a talk about ....
5762611012435968 MapServer: Design a ....
5765029615894528 MapServer: Install ....
</pre>

'''Upload Tasks through Commandline'''

# see usage of csv_uploader.py
#* <code>python csv_uploader.py --help</code>
# upload your csv at the commandline
#* <code>python csv_uploader.py -v --apikey [OSGeoKey] project-tasks.csv</code>
#** should return something like:
<pre>
OK 6030299680997376 MapServer: Give a ....
OK 5944469725642752 MapServer: Make a ....
OK 5765029615894528 MapServer: Install ....
OK 5702068213907456 MapServer: Find and fix ....
OK 5770211091283968 MapServer: Fix ....
</pre>
[[Category:Google Code In]]

Google Code In 2019

2019-10-15T12:10:59Z

Camerongreen: /* Tasks */

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



Central page for administering OSGeo participation in Google Code In 2019

= Background =

* Google Code In program has been [https://opensource.googleblog.com/2019/10/google-code-in-2019-org-applications.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 2018 contest [https://codein.withgoogle.com/archive/2018/organization/5912217769738240/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]
* Oct 10 2019: Organizations can start drafting application to be mentoring organizations
* Oct 28 2019: Application deadline ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 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)
* Oct 29 2019: Mentoring organizations announced
* Dec 2 2019: Contest opens for entries by student participants ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191202T18&p1=1440 exact time])
* Jan 21 2020: Deadline for students to claim new tasks ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200121T18&p1=1440 exact time])
* Jan 23 2020: All student work must be submitted; contest ends ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200123T18&p1=1440 exact time])
* Jan 24 2020: Mentoring organizations complete all evaluations of students’ work ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200124T18&p1=1440 exact time])
* Jan 30 2020: Mentoring organizations submit list of Winners and Finalists ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200130T18&p1=1440 exact time])
* Feb 10 2020: 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 2019 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 =

* [[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 2019 Mentors]]

= Recommendations for Students =

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

= Tasks =

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

= Application =

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

= Kickoff (virtual) meeting =

* Admins to select a date and time
* 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 28 Oct)
** 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]


= 2017 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2017

= 2018 pages =
* see https://wiki.osgeo.org/wiki/Google_Code_In_2018
[[Category:Google Code In]]

Google Code In 2019 Tasks

2019-10-15T12:09:11Z

Camerongreen: /* Interested Mentors */

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

= Interested Mentors =

Please '''first fill out the Google form''' mentioned at the top of: [[Google Code In 2019 Mentors]]

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;Design
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* OSGeo's 2017 tasks: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/
* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

* see shared spreadsheet on Google Drive

= Bulk Uploading Tasks =

'''Documentation'''

* [https://code.googlesource.com/codein/api API]

'''Prep'''

NOTE: the python scripts for bulk uploading are written for Python2, but the instructions below should work for both Python2 & 3:

# git clone https://code.googlesource.com/codein/api api
# cd api
# check your Python version:
#* <code>python -V</code>
# install module "requests" through easy_install or pip:
#* <code>easy_install requests</code>
#* <code>pip install requests</code>
# for Python2, no more changes are needed, proceed to next sections below (export tasks, or list tasks, or upload tasts, etc)
# for Python3, make the following changes:
#* in ''list_tasks.py'' change print command on line# 45 to
#** <code>print ('\t'.join([str(t['id']), t['name']]))</code>
#* in ''list_tasks.py'' convert to an int on line# 52 to
#** <code>next_page = int(result.group(1))</code>
#* in ''csv_uploader.py'' change line# 64 to
#** <code>with open(filename, 'rt') as csvfile:</code>
#* in ''csv_uploader.py'' change print command on line# 83 to
#** <code>print ('\t'.join(['OK', str(t['id']), t['name'], '']))</code>
#* in ''csv_uploader.py'' change print command on line# 86 to
#** <code>print ('\t'.join(['ERROR', '', t['name'], e.response.text]))</code>
#* in ''client.py'' change instances of "urlparse" to "urllib.parse"

'''Export CSV'''

* export your tasks from the Google spreadsheet (assuming you created a new sheet in the shared doc ''Code-in Bulk Upload Spreadsheet'') as CSV (File/Download as/CSV), but before that be sure to:
** make sure that the '''"categories" field''' is comma separated '''INTEGERs''' (see the "column definitions" sheet in ''Code-in Bulk Upload Spreadsheet'')
** verify that your dashboard '''PROFILE email address''' is the EXACT same as what you entered in the '''"mentors" field''' in 'Code-in Bulk Upload Spreadsheet' (otherwise your uploaded tasks will have empty/missing mentor)

'''List Tasks through Commandline'''

# see usage of list_tasks.py
#* <code>python list_tasks.py --help</code>
# get a list of tasks at the commandline
#* <code>python list_tasks.py --apikey [OSGeoKey]'''</code>
#** should return something like:
<pre>
5126447435874304 gvSIG: Make a .....
5172599543824384 gvSIG: Install.....
5702068213907456 MapServer: Find and fix ....
5723293673848832 gvSIG: Make a ....
5761046167945216 gvSIG: Give a talk about ....
5762611012435968 MapServer: Design a ....
5765029615894528 MapServer: Install ....
</pre>

'''Upload Tasks through Commandline'''

# see usage of csv_uploader.py
#* <code>python csv_uploader.py --help</code>
# upload your csv at the commandline
#* <code>python csv_uploader.py -v --apikey [OSGeoKey] project-tasks.csv</code>
#** should return something like:
<pre>
OK 6030299680997376 MapServer: Give a ....
OK 5944469725642752 MapServer: Make a ....
OK 5765029615894528 MapServer: Install ....
OK 5702068213907456 MapServer: Find and fix ....
OK 5770211091283968 MapServer: Fix ....
</pre>
[[Category:Google Code In]]

Google Code In 2019 Tasks

2019-10-15T12:08:55Z

Camerongreen:

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

= Interested Mentors =

Please '''first fill out the Google form''' mentioned at the top of: [[Google Code In 2018 Mentors]]

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;Design
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* OSGeo's 2017 tasks: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/
* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

* see shared spreadsheet on Google Drive

= Bulk Uploading Tasks =

'''Documentation'''

* [https://code.googlesource.com/codein/api API]

'''Prep'''

NOTE: the python scripts for bulk uploading are written for Python2, but the instructions below should work for both Python2 & 3:

# git clone https://code.googlesource.com/codein/api api
# cd api
# check your Python version:
#* <code>python -V</code>
# install module "requests" through easy_install or pip:
#* <code>easy_install requests</code>
#* <code>pip install requests</code>
# for Python2, no more changes are needed, proceed to next sections below (export tasks, or list tasks, or upload tasts, etc)
# for Python3, make the following changes:
#* in ''list_tasks.py'' change print command on line# 45 to
#** <code>print ('\t'.join([str(t['id']), t['name']]))</code>
#* in ''list_tasks.py'' convert to an int on line# 52 to
#** <code>next_page = int(result.group(1))</code>
#* in ''csv_uploader.py'' change line# 64 to
#** <code>with open(filename, 'rt') as csvfile:</code>
#* in ''csv_uploader.py'' change print command on line# 83 to
#** <code>print ('\t'.join(['OK', str(t['id']), t['name'], '']))</code>
#* in ''csv_uploader.py'' change print command on line# 86 to
#** <code>print ('\t'.join(['ERROR', '', t['name'], e.response.text]))</code>
#* in ''client.py'' change instances of "urlparse" to "urllib.parse"

'''Export CSV'''

* export your tasks from the Google spreadsheet (assuming you created a new sheet in the shared doc ''Code-in Bulk Upload Spreadsheet'') as CSV (File/Download as/CSV), but before that be sure to:
** make sure that the '''"categories" field''' is comma separated '''INTEGERs''' (see the "column definitions" sheet in ''Code-in Bulk Upload Spreadsheet'')
** verify that your dashboard '''PROFILE email address''' is the EXACT same as what you entered in the '''"mentors" field''' in 'Code-in Bulk Upload Spreadsheet' (otherwise your uploaded tasks will have empty/missing mentor)

'''List Tasks through Commandline'''

# see usage of list_tasks.py
#* <code>python list_tasks.py --help</code>
# get a list of tasks at the commandline
#* <code>python list_tasks.py --apikey [OSGeoKey]'''</code>
#** should return something like:
<pre>
5126447435874304 gvSIG: Make a .....
5172599543824384 gvSIG: Install.....
5702068213907456 MapServer: Find and fix ....
5723293673848832 gvSIG: Make a ....
5761046167945216 gvSIG: Give a talk about ....
5762611012435968 MapServer: Design a ....
5765029615894528 MapServer: Install ....
</pre>

'''Upload Tasks through Commandline'''

# see usage of csv_uploader.py
#* <code>python csv_uploader.py --help</code>
# upload your csv at the commandline
#* <code>python csv_uploader.py -v --apikey [OSGeoKey] project-tasks.csv</code>
#** should return something like:
<pre>
OK 6030299680997376 MapServer: Give a ....
OK 5944469725642752 MapServer: Make a ....
OK 5765029615894528 MapServer: Install ....
OK 5702068213907456 MapServer: Find and fix ....
OK 5770211091283968 MapServer: Fix ....
</pre>
[[Category:Google Code In]]

Google Code In 2019 Recommendations for Students

2019-10-15T12:07:26Z

Camerongreen:

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

== Welcome to OSGeo! ==

[[Image:Geomorphons_in_3D_view_Appearance_tab.png|thumb|right|333px|GRASS GIS software, viewing a map layer in 3D]]
[[Image:Foss4g-2016-boat-cruise.jpg|thumb|right|333px|FOSS4G (OSGeo's annual conference) boat cruise, August 2016, Bonn, Germany]]
[[Image:Grass-gis-sprint-team-paris.jpg|thumb|right|333px|GRASS GIS team at the FOSS4G-Europe code sprint, July 2017 in Paris, France]]
[[Image:Gvsig-code-sprint.jpg|thumb|right|333px|gvSIG-Mobile code sprint team, February 2017 in Valencia, Spain]]
[[Image:Mapserver-sprint-boston.jpg|thumb|right|333px|MapServer code sprint team at FOSS4G-Boston, August 2017 in Boston, U.S.]]
[[Image:PgRouting-team.jpg|thumb|right|333px|pgRouting and QGIS team members at FOSS4G-Seoul, September 2015 in Seoul, South Korea]]
[[Image:Osgeolive-bonn-sprint.jpg|thumb|right|333px|OSGeoLive code sprint at FOSS4G-Bonn, August 2016 in Bonn, Germany]]
[[Image:Sri-lanka-chapter-meeting.jpg|thumb|right|333px|Sri Lanka local chapter meeting, on 2017-11-15]]

We are a fun vibrant community that believes in sharing Open Source software related to making maps.

== How to ask general questions about the Code-in ==

'''Send an Email of questions to OSGeo'''

* subscribe to OSGeo's "gci-discuss" mailing list [https://lists.osgeo.org/mailman/listinfo/gci-discuss here]
* ask your question, and usually within a day someone from the OSGeo Code-in team (mentors or administrators) will reply
* all OSGeo mentors for the Code-in contest follow this "gci-discuss" mailing list

'''Ask on the #osgeo-gci IRC chat channel'''

* IRC-channel: #osgeo-gci channel on freenode.net
** how to connect: choose your favorite IRC client, or go directly through your web browser with [https://webchat.freenode.net/?channels=osgeo-gci webchat]
** enter a nickname and click "I am not a robot" and press "Connect"
** upon entering, ask your questions as you wish (no need to wait, just say "hello, I have a question about the Code-In, how do I..."

== Get to know the OSGeo Community ==

The OSGeo foundation ( http://osgeo.org ) was founded in the year 2006 and contains many different types of Open Source software projects to help make geographical maps.

The OSGeo foundation also holds a super-fun conference each year, all over the world, named FOSS4G ( http://foss4g.org ) for '''F'''ree and '''O'''pen '''S'''ource '''S'''oftware for '''G'''eospatial.

* Follow OSGeo on Twitter: [https://twitter.com/OSGeo @OSGeo]
* Follow FOSS4G on Twitter: [https://twitter.com/foss4g @foss4g]

== Why OSGeo? ==

# the global geospatial (mapping) industry is huge now (400 Billion USD revenue industry, as of September 2017, read [https://www.valueoftheweb.com/reports/the-economic-impact-of-geospatial-services/ report])
# learn skills useful to get jobs in the mapping industry (Open Source is rarely taught at school, yet it is in huge demand by employers around the world)
# OSGeo community members are fun, vibrant, and willing to help!
# we have local chapters (local groups getting together or discussing on their own mailing lists in many languages) all over the world! (see [https://wiki.osgeo.org/wiki/Local_Chapters list])

== Coding Languages ==

OSGeo projects use a variety of coding languages, including:
* C
* C++
* Java
* Python
* JavaScript

== OSGeo Projects & Initiatives Involved in the Code-In ==

* [http://foss4g.org FOSS4G] (global conference event)
* [http://geoserver.org/ GeoServer] (web mapping)
* [http://grass.osgeo.org/ GRASS GIS] (desktop)
* [http://istsos.org/ istSOS] (web mapping)
* [https://leafletjs.com// Leaflet] (web mapping)
* [http://www.mapserver.org/ MapServer] (web mapping)
* [http://live.osgeo.org/ OSGeoLive] (installer for projects)
* [http://pgrouting.org/ pgRouting] (geospatial library)

== Searching for a Project's Mailing list Archives ==

A good trick to search an OSGeo project's mailing list for help, if you are stuck on a coding problem, is to use OSGeo's Nabble Forum: http://osgeo-org.1560.x6.nabble.com/

[[Category:Google Code In]]

Google Code In 2019 Mentors

2019-10-15T12:05:40Z

Camerongreen:

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

= Mentors =

If you're interested in participating in the Code-In as a mentor of an OSGeo project (and creating tasks etc), '''please fill out the Google form''' at: https://docs.google.com/forms/d/e/1FAIpQLSfwyUCLf4PQpA0aLLfceBdsZUG97BVdXR_3sJuMRyjl5x0bEw/viewform?usp=sf_link

(the following table will be populated from the above Google form, by the GCI admins only)

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="200"|Email
!width="60"|Country
!width="100"|OSGeo Project
|-
| 1 || || || ||
|-
|}

= Mentor Responsibilities =

...'''to OSGeo gci-admin team'''

* Communicate availability and interaction expectations
* Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
* Inform gci-admin team when there is an issue with a student
** Lacking communication, activity, visibility (MIA), or progress
** Participant Agreement violations (e.g., plagiarism, harassment, fraud)
** Bad fit or stepping down
** Formally evaluate student participation

...'''to your Students'''

* Help and/or teach the student how to
** be a part of your community
** communicate more effectively and in the open
** work with your org’s preferred communication channel (IRC, Slack, etc)
** use your org’s version control system
** ask good questions and get answers to their questions
** provide convincing technical argument and constructive discussion
** be independently motivated and productive
** solve difficult technical problems
* Keep track of their progress, keep student informed as to their status
* Give constructive feedback, be patient (particularly for GCI), and be respectful
* Respond to questions within 24 hours (occasionally under 36 hours is ok)
* Establish realistic work objectives and timeline expectations
* Re-evaluate scope with student when significantly ahead of or behind expectations
** Give them extra time on a task as warranted
* Work with devs and community to facilitate acceptance of student work

= Unknown Mentors =

Boilerplate text to reply to unknown mentors:

''Thank you a lot for being available as a GCI mentor! OSGeo mentors need to be able to guide students; hence mentors need to be experienced OSGeo contributors and need to know the community and "how things work". Could you please share some information of which specific OSGeo projects you have contributed to and worked on so far? How would you describe your areas of expertise within OSGeo? Are there any public OSGeo contributions you could link to (for example your OSGeo wiki page or your Github activity)? Are you involved in your local OSGeo chapter? This would help us to get a better idea. Thank you! And if you have not contributed to OSGeo yet, we encourage you to start contributing to OSGeo by checking out https://www.osgeo.org/community/getting-started-osgeo/ ! Thank you!''

[[Category:Google Code In]]

Google Code In 2019 Lessons Learned

2019-10-15T11:54:58Z

Camerongreen:

''(see the [[Google_Code_In_2018_Lessons_Learned|2018]] lessons learned page)''

= Purpose =

This is to document things that admins and mentors learned, for the benefit of future Code-In exercises.

[[Category:Google Code In]]

Google Code In 2019 Grand Prize Trip

2019-10-15T11:51:49Z

Camerongreen:

[[Category: Google Code In]]

Google Code In 2019 Foundation Tasks

2019-10-15T09:39:37Z

Camerongreen:

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== ''Join the OSGeo community'' ==

* your name
** link to your user account

== Video of experience with GCI and OSGeo ==

* your name
** link to Youtube video

== Video of what FOSS4G means to you ==

* your name
** link to Youtube video

[[Category:Google Code In]]

Google Code In 2019 Foundation Tasks

2019-10-15T09:39:08Z

Camerongreen: /* video of what FOSS4G means to you */

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== ''Join the OSGeo community'' ==
* your name
** link to your user account

== Video of experience with GCI and OSGeo ==

== Video of what FOSS4G means to you ==

* your first name
** link to Youtube video

[[Category:Google Code In]]

Google Code In 2019 Foundation Tasks

2019-10-15T09:38:57Z

Camerongreen: /* video of experience with GCI and OSGeo */

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== ''Join the OSGeo community'' ==
* your name
** link to your user account

== Video of experience with GCI and OSGeo ==

== video of what FOSS4G means to you ==

* your first name
** link to Youtube video

[[Category:Google Code In]]

Google Code In 2019 Foundation Tasks

2019-10-15T09:38:26Z

Camerongreen:

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== ''Join the OSGeo community'' ==
* your name
** link to your user account

== video of experience with GCI and OSGeo ==

== video of what FOSS4G means to you ==

* your first name
** link to Youtube video

[[Category:Google Code In]]

Google Code In 2019 Foundation Tasks

2019-10-15T09:37:21Z

Camerongreen:

A page for the 2019 Google Code-In initiative (2 December 2019 to 23 January 2020).
== ''Join the OSGeo community'' ==

== video of experience with GCI and OSGeo ==

== video of what FOSS4G means to you ==

* your first name
** link to Youtube video

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-15T09:33:11Z

Camerongreen: /* Profile */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==



== Profile ==



[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-15T09:32:31Z

Camerongreen: /* Application Questions */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==



== Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

* '''Chat (Link to a web page that describes how to access your realtime chat)''' https://wiki.osgeo.org/wiki/IRC

* '''Mailing list (Link to a page describing how to join your organization's mailing list)''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization)''' gci-admin at osgeo.org

* '''Google+ URL''' https://plus.google.com/communities/105969056638310510633

* '''Twitter URL''' https://twitter.com/osgeo

* '''Blog URL''' http://planet.osgeo.org/

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-15T08:52:39Z

Camerongreen: /* Application Deadline */

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

== Application Deadline ==

* Application is due 28 October 2019 ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T16&p1=1440 exact time])

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

== Application Questions ==

* '''Why does your organization want to participate in Google Code-in 2018? (500 character limit)''' After participating in our first GCI experience last year, where students completed 649 tasks, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2018_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2018

* '''How many mentors have committed to participate?''' 10

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks

== Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

* '''Chat (Link to a web page that describes how to access your realtime chat)''' https://wiki.osgeo.org/wiki/IRC

* '''Mailing list (Link to a page describing how to join your organization's mailing list)''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization)''' gci-admin at osgeo.org

* '''Google+ URL''' https://plus.google.com/communities/105969056638310510633

* '''Twitter URL''' https://twitter.com/osgeo

* '''Blog URL''' http://planet.osgeo.org/

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]

Google Code In 2019 Application

2019-10-15T08:51:22Z

Camerongreen:

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

== Application Deadline ==

* application is due 17 September ([https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=09&day=17&hour=16&min=0&sec=0 exact time])

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

== Application Questions ==

* '''Why does your organization want to participate in Google Code-in 2018? (500 character limit)''' After participating in our first GCI experience last year, where students completed 649 tasks, OSGeo believes that it is important to introduce the future young leaders to our vibrant community of over 42 different software projects. We feel that this will be another fun experience for both the mentors and the students, with benefits to the software projects and the whole OSGeo community.

* '''How has your organization prepared for Google Code-in 2018? (500 character limit)''' OSGeo has assembled an admin team, made up of veteran Summer of Code and GCI participants, and have put out a call for mentors (we currently have 10+ mentors so far https://wiki.osgeo.org/wiki/Google_Code_In_2018_Mentors). Mentors have been already recording tasks (https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks) and we will keep adding tasks in the next month.

* '''Has your organization participated in Google Code-in before? (yes or no)''' Yes: 2017

* '''Has your organization participated in Google Summer of Code before? (yes or no)''' Yes

* '''In which years did your organization participate in Google Summer of Code?''' 2007 to 2018

* '''How many mentors have committed to participate?''' 10

* '''How do you plan to deal with any holidays or vacations mentors may have planned during the contest period? (500 character limit)''' We are asking for several mentors for each project, so that several mentors can assist throughout this coming holiday season. We are also making sure to have mentors located in different timezones for each project. We will organize shifts for the days that we foresee scarce presence due to holidays.

* '''How do you plan to deal with unresponsive mentors? (500 character limit)''' We have already setup a private mailing list for discussions with mentors and admins, and we have also asked for all contact details for all mentors. We have also a discrete backup. However, we also try to make sure that our mentors are aware that they commit and take responsibility to carry out the program until the end.

* '''We would like to see 25 example tasks. (URL to sample tasks - Be sure to include tasks from all 5 categories)''' https://wiki.osgeo.org/wiki/Google_Code_In_2018_Tasks

== Profile ==

* '''Short description (200 character limit)''' OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.

* '''Long description (1500 character limit - using "limited markdown" syntax)'''
<pre>
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and several code projects in particular:

## Content Management Systems

GeoNode

## Desktop Applications

GRASS GIS
gvSIG
Marble
QGIS

## Geospatial Libraries

FDO
GDAL/OGR
GEOS
GeoTools
Orfeo ToolBox (OTB)
OSSIM
PostGIS

## Metadata Catalogs

GeoNetwork
pycsw

## Web Mapping

deegree
geomajas
GeoMOOSE
GeoServer
Mapbender
MapFish
MapGuide Open Source
MapServer
OpenLayers
PyWPS

## Incubating Projects

istSOS
MetaCRS
Opticks
Oskari
Team Engine
ZOO-Project

## Outreach Projects

GeoForAll - Education and Curriculum
OSGeo-Live

## OSGeo Community Projects

Geoinformatica
GeoWebCache
MapProxy
pgRouting
Portable GIS
Postal Address Geo-Coder
Proj4php
Pronto Raster
Virtual Terrain Project

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

* '''Tags (enter 5 only - A few keywords to help students find your organization. Examples: Machine Learning, Video, Kernel, Games, Natural Language, Graphics. Do not include programming languages and technologies or your organization's name)''' geospatial, maps, cartography, gis, application

* '''Programming languages and technologies (enter 5 only)''' c, java, python, c++, javascript

* '''Primary Open Source License''' MIT License (MIT)

* '''Chat (Link to a web page that describes how to access your realtime chat)''' https://wiki.osgeo.org/wiki/IRC

* '''Mailing list (Link to a page describing how to join your organization's mailing list)''' https://www.osgeo.org/community/communications/

* '''Contact email (A general purpose contact email for your organization)''' gci-admin at osgeo.org

* '''Google+ URL''' https://plus.google.com/communities/105969056638310510633

* '''Twitter URL''' https://twitter.com/osgeo

* '''Blog URL''' http://planet.osgeo.org/

* '''Extra task information (250 character limit - Short instructions or tips to be displayed with every task. May include limited Markdown. Example: See http://link for information on how to checkout, build, and run the code. Don't forget to join the IRC channel to ask mentors questions)''' Don't forget to join the #osgeo-gci IRC channel to ask mentors questions, on freenode.net (connect directly in your browser through https://webchat.freenode.net/?channels=osgeo-gci).

* '''Common task information link (A URL for a web page that will be linked to from every task as "Working with OSGeo")''' https://wiki.osgeo.org/wiki/Google_Code_In_2018#Communication

[Back to [[Google Code In 2018]] @ OSGeo]

[[Category:Google Code In]]