Difference between revisions of "Google Code In 2017 Mentors"

From OSGeo
Jump to navigation Jump to search
(Created page with "<center> 400px|link=https://developers.google.com/open-source/gci/ <font size="+3"> @ </font> 300px|link=http://www.osgeo.org <...")
 
Line 5: Line 5:
 
= Mentor Responsibilities =
 
= Mentor Responsibilities =
  
...```to OSGeo gci-admin team```
+
...'''to OSGeo gci-admin team'''
  
 
* Communicate availability and interaction expectations
 
* Communicate availability and interaction expectations
Line 15: Line 15:
 
** Formally evaluate student participation
 
** Formally evaluate student participation
  
...```to your Students```
+
...'''to your Students'''
  
 
* Help and/or teach the student how to
 
* Help and/or teach the student how to

Revision as of 06:48, 5 October 2017

GCI-logo.jpg @ Osgeo-logo.png

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