Guidelines for Sahana Mentors for Google Summer of Code 2010


  • In general, it is desired that as much communication as practical takes place using the existing project communications media - namely IRC for realtime communications, and the public mailing lists for asynchronous communications. These should be the primary means of project collaboration. Note that due to timezone differences, some coordination may be required to arrange realtime communications.
  • All communications should be replied to in a timely manner.
  • Private emails or chats should only be used for sensitive issues that are best not discussed on public channels such as IRC or maindev.
  • If a mentor will be unreachable for a few day due to, say, travel, they should inform their student as soon as practical. As there will be two mentors assigned to a student, only in significant periods of absence should the Sahana GSOC Admins be notified.


  • Mentors shall complete all activities required by Google (reviews, project selection, etc) no later than 48 hours before the Google deadline to give Administrators enough time to make sure all obligations are followed through.

Progress Tracking

  • Mentors will be responsible for tracking progress by students on a weekly basis as directed by GSOC Administrators


The assigned mentor will be responsible for reviewing project work, and ultimately responsible for approving/denying both mid-term and final GSOC payments. The following guidance is provided:

  • If the project milestones for mid-term review have not been met, then the default position of a mentor will be to fail the project at mid-term reviews. Only under exceptional circumstances will the mentor, after consultation with other Sahana GSOC10 mentors, approve the mid-term review.

QR Code
QR Code community:gsoc:sahana_gsoc10_mentor_guidelines (generated for current page)