How midterms/finals work

Ready for review -- AWAITING PEER REVIEW
This lesson helps you to understand how midterms/finals work and what is the procedure that you need to follow in order to make it things well.

Evaluations occur twice: midterm and final. They are the opportunity to evaluate mentor and mentoring organization's performance. This is also mentor's opportunity to evaluate student.

The pass or fail decision from an evaluation should not come as a surprise. Student and mentor will already be communicating, and they should be discussing the quality of the code, the participation in the community and the progress on the project to that point.


Evaluations are administered via Melange and they will take about an hour to complete.

Google will pre-publish the evaluation questions for both students and mentors. Mentors will fill out midterm and final evaluations for their students via the Google Summer of Code 2015 site. These evaluations will be visible in the system to the mentor and the mentoring organization's administrator(s). Students will fill out a midterm and final evaluation of their mentors online as well, and their evaluations will only be visible in the system to the mentoring organization's administrator(s). Program administrators from Google will have access to all evaluation data.

Any student who does not submit an evaluation by the evaluation deadline will fail that evaluation, regardless of the grade the mentor gives the student. If a student submits his or her evaluation on time but the mentor does not, then the student is in an “undecided” state until the program administrators can speak to the mentor and determine the student’s grade.

Students who fail the mid-term are immediately removed from the program: it’s not possible to fail the mid-term, stay in the program, and then have a final evaluation.

Students will never see their mentor's evaluation of their progress, nor will a mentor see a student's evaluation of her/his mentorship. However, in the case where the mentoring organization's administrator and a student's mentor are one and the same, the student's evaluation will be viewable to the mentor/organization administrator. If there is a student in a situation where his/her mentor is also the organization’s administrator and the student would like to discuss an issue with the program, student should contact the Google Summer of Code program administrators. Organization administrators are expected to review midterm and final evaluations and to provide course corrections where necessary.

Any mentor who misses a deadline for an evaluation of his/her student without notifying the program administrators beforehand will not be allowed to attend the Google Summer of Code mentor summit. Any organization that misses two or more evaluation deadlines at the midterm, the final, or the midterm and the final combined, will be uninvited from the mentor summit completely. Timely evaluations of Google Summer of Code students are crucial to organization. Organization administrators can submit student evaluations on their mentors’ behalf, so there really is no excuse for missing an evaluation deadline.