I think it's time for a quick check-in/status report.
Students, please provide the group with a short (i.e. one paragraph)
status of your project.
The deadline for completion is fast approaching (evaluations must be
completed by August 24); it's time to start wrapping up the current
phase of your project.
Students, please keep in mind that this is an open source community
and that your continued contributions to Eclipse projects after GSoC
2012 completes are most welcome.
-------- Original Message --------
This is a friendly reminder that Monday, 13 August is our soft
"pencils down" date. We suggest that students have completed their projects
by this date and spend a week writing documentation and wrapping up their
projects. We require that students stop all coding on 20 August.
Monday, 20 August at 19:00 UTC is also when final evaluations open. Please
consider this your reminder to submit your final evaluation by 24 August at
19:00 UTC so that you don't delay your students' final payments or possibly
jeopardize your organization's attendance at the mentor summit.
I have updated the code submission guidelines  and posted it on
Melange for your reference. Code submission begins once students have
received a passing grade on their final evaluations (after 24 August). The
deadline is 14 September. One question students ask a lot is what portion
of their code to submit if they made changes to an existing code base or
their code interacts a lot with a system they didn't write. The answer is:
use your best discretion. Have them submit the code that makes the most
sense from a user's perspective. If students need help with code submission
they should contact the Melange team at melange-soc-dev@xxxxxxxxxxxxxxxx.
I have posted the questions for the final evaluations below as well for
 - *
1. How would you rate the studentâ€™s performance on his/her project since
the midterm evaluations?
1. It has improved since the midterm
2. It has stayed the same since the midterm
3. It has gotten worse since the midterm
2. Considering your studentâ€™s original project proposal, how closely
does the project produced reflect the project proposed?
1. Itâ€™s almost exactly the same - there have been very few changes to
2. Itâ€™s similar - there have been some changes over the course of the
3. Itâ€™s different - we changed the goals or scope of the project
4. Itâ€™s different - the student diverged from the project plan
3. How much time have you spent on Google Summer of Code since the
midterm evaluations (again, take into consideration both time mentoring the
student and working on the program as a whole)?
1. 10-15 hours per week
2. 15-20 hours per week
3. 20-25 hours per week
4. 25-30 hours per week
5. 30-35 hours per week
6. 35-40 hours per week
7. 40+ hours per week
4. How does this amount of time spent on the program compare to before
1. Itâ€™s less than before the midterms
2. Itâ€™s about the same
3. Itâ€™s more than before the midterms
5. How would you rate your studentâ€™s performance overall?
1. Excellent - amongst the best performers Iâ€™ve ever worked with
2. Strong, solid performance
6. How would you rate your experience with the program overall?
1. Excellent - one of the best programs Iâ€™ve ever participated in
2. Very good
7. Did you have a co-mentor in the program this year? If so, would you
consider this a help or a hindrance? Why?
8. What one thing would you tell mentors for your organization to do in
the future to help the studentsâ€™ experience with the program?
9. What was the most rewarding and/or difficult part of the program for
you this year?
10. Anything else youâ€™d like to tell us?
You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group.
To post to this group, send email to google-summer-of-code-mentors-list@xxxxxxxxxxxxxxxx.
To unsubscribe from this group, send email to google-summer-of-code-mentors-list+unsubscribe@xxxxxxxxxxxxxxxx.
For more options, visit this group at http://groups.google.com/group/google-summer-of-code-mentors-list?hl=en.