[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Carol Smith] [GSoC Mentors Announce] Re: GSoC 2013 Mentors/Org Admins:

From: Jose E. Marchesi
Subject: [Carol Smith] [GSoC Mentors Announce] Re: GSoC 2013 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching
Date: Mon, 23 Sep 2013 21:10:51 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Hi Mentors.
See below.  Please fill in and send your final evaluations ASAP.

--- Begin Message --- Subject: [GSoC Mentors Announce] Re: GSoC 2013 Mentors/Org Admins: "Pencils Down" and Final Evaluation Dates Approaching Date: Mon, 23 Sep 2013 12:04:23 -0700
Hi GSoC 2013 mentors and org admins,

This is just a friendly reminder that final evaluations are now open and must be submitted by this Friday, 27 September at 19:00 UTC. Don't delay, submit today!


On Thu, Sep 5, 2013 at 10:28 AM, Carol Smith <address@hidden> wrote:
Hi there,

This is a friendly reminder that Monday, 16 September 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 23 September.

Monday, 23 September at 19:00 UTC is also when final evaluations open. Please consider this your reminder to submit your final evaluation by 27 September 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 [0] and posted it on Melange for your reference. Code submission begins once students have received a passing grade on their final evaluations (after 27 September). The deadline is 11 October. 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 address@hidden.

I have posted the questions for the final evaluations below as well for your reference.

[0] -



  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 the project

    2. It’s similar - there have been some changes over the course of the summer

    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 mid term 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 the midterms?

    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

    3. Okay

    4. Poor

  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

    3. Okay

    4. Poor

  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. Is there additional information we should tell future students before applying to future programs?  

  11. 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 Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to address@hidden
Visit this group at
For more options, visit

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]