Google Code In 2017 Lessons Learned

From OSGeo
Revision as of 06:21, 16 November 2017 by Jmckenna (talk | contribs) (Created page with " This is to document things that admins and mentors learned, for the benefit of future Code-In exercises. == Unknown Admins == Be vigilant when receiving initial volunteers...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

Unknown Admins

Be vigilant when receiving initial volunteers as mentors that are unknown, and request background on their OSGeo activity, and if they are new to the community, politely steer them to ways to contribute, and possibly join the contest next year.

 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!