Difference between revisions of "Google Code In 2017 Mentors"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
!width="250"|Email | !width="250"|Email | ||
!width="60"|Country | !width="60"|Country | ||
| − | !width="30"|Project | + | !width="30"|OSGeo Project |
|- | |- | ||
| 1 || Shawn Goulet || shawn.goulet at gmail.com || United States || FOSS4G | | 1 || Shawn Goulet || shawn.goulet at gmail.com || United States || FOSS4G | ||
| Line 23: | Line 23: | ||
|- | |- | ||
| 5 || Rohith Reddy Sankepally || rohithreddy2219 at gmail.com || India|| pgRouting | | 5 || Rohith Reddy Sankepally || rohithreddy2219 at gmail.com || India|| pgRouting | ||
| + | |- | ||
| + | | 6 || Aurelien Xavier Payong Djiomegni || aurelienxavier93 at gmail.com || Cameroon || | ||
|+ | |+ | ||
|} | |} | ||
Revision as of 08:03, 5 October 2017
@ 
Mentors
If you're interested in mentoring students for an OSGeo project, please fill out the Google form at: https://docs.google.com/forms/d/1_p46X0aExtGAFGpu4lrVnjitLsqOnqRfa2kfvCm_sI0/
| # | Name | Country | OSGeo Project | |
|---|---|---|---|---|
| 1 | Shawn Goulet | shawn.goulet at gmail.com | United States | FOSS4G |
| 2 | Guido Stein | guido at guidostein.com | United States | OSGeo |
| 3 | Vicky Vergara Castillo | vicky at georepublic.de | Mexico | pgRouting, OSGeo-Live |
| 4 | Veronica Andreo | veroandreo at gmail.com | Netherlands | GRASS GIS |
| 5 | Rohith Reddy Sankepally | rohithreddy2219 at gmail.com | India | pgRouting |
| 6 | Aurelien Xavier Payong Djiomegni | aurelienxavier93 at gmail.com | Cameroon |
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