Evaluations occur two times (after 5 weeks and at the end of the 10th week of the coding period). They are your opportunity to evaluate your mentor and your mentoring organization’s performance. This is also your mentor’s opportunity to evaluate you.
The pass or fail decision from an evaluation should not come as a surprise. You and your mentor will already be communicating, and you should be discussing the quality of your code, your participation in the community and your progress on your project to that point. If you aren’t getting this feedback, ask for it.
How Evaluations Work
Evaluations are a survey that both you and your mentor fill in during the evaluation period. Google publishes the evaluation questions for both students and mentors in advance.
Evaluations are administered via the webapp you used to submit your project proposal at the start of the term. Evaluations will take about 10-15 minutes to complete. The questions focus on the scope of your project, the quality of your interactions with your mentor and your community. You, your mentor and org admins will receive an email after the evaluation window closes that tells you whether you’ve passed.
Your evaluations are only visible to your mentoring org admins and program administrators from Google. In some cases, Google’s program administrators may need to share some details of evaluations with you and your mentor. This may happen, for example, when evaluations indicate a payment should not be made.
You are encouraged to complete both evaluations but you are only required to complete the final evaluation, if you do not complete the final evaluation which also includes your link to your work product you will fail the program. Failing an evaluation means you are immediately removed from the GSoC program.
Final Evaluations and Work Product Submission
At the end of the Google Summer of Code term you are required to provide a link to the work you created during your current GSoC participation, in addition to your evaluation. Essentially the target of the link should contain a short description of what work was done, what code got merged, what code didn’t get merged, and what’s left to do.
Depending on what portions of code are included in the scope of your project, you may need to submit diffs between code that you’ve written and others have written, or even include an entire branch of the code base. Discuss this with your mentor and your community and use your best judgement.
Payments - Be Patient
Successful completion of your evaluations triggers the payments to your account or your payment card. This takes a few business days to process. Please be patient.