Google Code In 2017 Mentors

@ 
= 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 	Email 	Country 	OSGeo Project
1 	Vicky Vergara Castillo 	vicky at georepublic.de 	Mexico 	pgRouting, OSGeo-Live
2 	Veronica Andreo 	veroandreo at gmail.com 	Netherlands 	GRASS GIS
3 	Rohith Reddy Sankepally	rohithreddy2219 at gmail.com 	India 	pgRouting
4 	Victoria Rautenbach 	victoria.rautenbach at gmail.com 	South Africa 	
5 	Jeff McKenna 	jmckenna at osgeo.org 	Canada 	MapServer, OSGeo, FOSS4G
6 	Luca Delucchi 	lucadeluge at gmail.com 	Italy 	GRASS GIS
7 	Nadia Chaer 	nadiachaer at gmail.com 	Uruguay 	
8 	Vidhan Jain 	vidhanj1307 at gmail.com 	India 	pgRouting
9 	Carlos I. Colombana 	carlos.colombana at gmail.com 	Uruguay 	gvSIG
10	Arne Schubert 	atd.schubert at gmail.com 	Germany 	Mapbender
11	Daniel Kastl 	daniel at georepublic.de 	Japan 	pgRouting
12	Yewondwossen Assefa 	assefay at gmail.com 	Canada/Nigeria	MapServer, OSGeo
13	Antonio Zito Camacho 	chocamazito at gmail.com 	Uruguay 	
14	Sergio Acosta y Lara 	sergio.acostaylara at mtop.gub.uy	Uruguay 	gvSIG
15	Maoguang Wang 	xjtumg1007 at gmail.com 	China 	pgRouting
16	Giani Carlevaro 	gianimauro at vera.com.uy 	Uruguay 	gvSIG
17	Jody Garnett 	jody.garnett at gmail.com 	Canada 	GeoTools, GeoServer
18	Sandro Santilli 	strk at kbt.io 	Italy 	PostGIS, GEOS
= 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 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)? 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 http://www.osgeo.org/content/faq/how_can_i_help_osgeo.html ! Thank you!
Category:Google Code In