Fwd: [GSoC Mentors Announce] [GSoC 2014] Mentor Midterm Evaluations 23 June - 27 June

1 view
Skip to first unread message

Ed Cable

unread,
Jun 16, 2014, 1:11:21 PM6/16/14
to mifos-gsoc-mentors
Hi all,

Time is rapidly passing by and we're already nearing midterm evaluations for GSOC.  Please review Carol's email and begin thinking through the evaluation for your student so you can have yours ready by next week.

Please give me a heads up if any of your students are in danger of failing or you have serious concerns about the progress they're making.

Ed

---------- Forwarded message ----------
From: 'Carol Smith' via Google Summer of Code Mentors Announce List <gsoc-mento...@googlegroups.com>
Date: Mon, Jun 16, 2014 at 8:56 AM
Subject: [GSoC Mentors Announce] [GSoC 2014] Mentor Midterm Evaluations 23 June - 27 June
To: GSoC Mentors Announce <gsoc-mento...@googlegroups.com>


Hi GSoC 2014 Mentors and Org Admins,

Per the program timeline, starting on Monday, 23 June you will will be able to submit an evaluation of your student(s)' progress on their projects thus far. Here's some important info on midterm evaluations for those not familiar:

Midterm evaluations are done via Melange. Starting at 19:00 UTC on 23 June you will be able to submit an evaluation for your student(s).You can find the evaluation links on your dashboard under 'Evaluations', one for each student you are a mentor for. If you are curious about who can see evaluations after they are submitted, please check out the FAQ on Evaluations. I have also pre-published the evaluation questions below in this email so you can prepare. The deadline to submit your evaluation is 19:00 UTC on Friday, 27 June.

You may not submit your evaluation before or after the evaluation window. Please ask your org admin to submit your evaluation for you if you absolutely cannot submit yours during the evaluation window. There really is no excuse for missing the submission of a student's evaluation.

You must submit an evaluation for every student you are a mentor for this year. You may submit, modify, and resubmit an evaluation as many times as you choose up until the deadline. You must answer all required questions on the evaluation in order to save submit it.

Please note that failing a student at the midterm evaluation means *this student is immediately removed from the program.* There is no way to fail a student at the midterm and have the student continue with the program to try to "make it up" at the final. If your student fails, your student is out.

You might find the FLOSS manual on GSoC evaluations helpful as well. There's some excellent wisdom in there from your fellow mentors and org admins on the evaluation process.  

Students must have an evaluation on file from both themselves *and* a passing evaluation from their mentor(s) in order to receive their midterm payments.

Finally, a reminder: This year we will not allow any mentor who misses an evaluation deadline to attend the Reunion (assuming no one else submits the evaluation on the mentor's behalf before the deadline either). Also, any org that misses 2 or more evaluation deadlines (for the midterm, final, or midterm and final combined) will not be allowed to attend the Reunion this year.

Please let me know directly if you have questions or concerns.

Cheers,
Carol
---------

  1. How many years have you been a mentor for Google Summer of Code (Total - this doesn’t have to be consecutive)?

    1. This is my first year

    2. 2-3 years

    3. More than 3 years

  2. If you answered “2-3 years” or “more than 3 years” as a mentor, what years did you participate?

  3. How many years have you been a student in Google Summer of Code?

    1. I have never been a student

    2. 1 year

    3. 2 years

    4. 3+ years

  4. If you answered 2 years or 3+ years, what years did you participate as a student?

  5. At what point did you first make contact with your student?

    1. Before the program was announced

    2. After my organization was selected to participate in Google Summer of Code

    3. During the student application/acceptance phase of the program

    4. During the community bonding period

    5. After the start of coding

  6. How often do you and your student interact?

    1. Daily

    2. Every few days

    3. Weekly

    4. Every few weeks

    5. Monthly

    6. Less than once a month

  7. How do you communicate with your student? (Check all that apply)

    1. Google+ Hangout

    2. Voice (phone, Skype, etc.)

    3. IM/IRC

    4. Private emails

    5. Mailing Lists

    6. Student blog updates

    7. In-person meeting(s)

    8. Other

  8. Of the communication methods listed above, which do you use most frequently?

  9. How much time do you spend on Google Summer of Code per week (take into consideration your interactions with your student as well as time working with your org and on your own)?

    1. 1-5 hours

    2. 5-10 hours

    3. 10-15 hours

    4. 15-20 hours

    5. More than 20 hours per week

  10. How many time zones apart from your student are you?

    1. Less than 3

    2. 3-6

    3. More than 6

  11. How often do you require status updates from your student?

    1. Daily

    2. Every few days

    3. Weekly

    4. Only when explicitly asked for by me

  12. Please rate the quality of your interactions and communications with the student (consider his/her communication with you as well as your responses).

    1. Very Good (Student is regularly responsive and the quality of communication is high)

    2. Good (Student is somewhat responsive and the quality of communication is okay)

    3. Bad (Student is only somewhat or not at all responsive and the quality of communication is low)

  13. Please rate the quality of the student’s interactions with your organization and community.

    1. Very Good (Student is regularly responsive and the quality of communication is high)

    2. Good (Student is somewhat responsive and the quality of communication is okay)

    3. Bad (Student is only somewhat or not at all responsive and the quality of communication is low)

  14. Is your student on track to complete his/her project?

    1. The student has already completed his/her project

    2. He/she is ahead of schedule

    3. He/she is on schedule

    4. He/she is behind schedule

  15. Please rate the quality of code/work the student has produced thus far.

    1. Amongst the best people I’ve ever worked with

    2. Solid-quality performance

    3. Good performance

    4. Mediocre performance

    5. Disappointing or not performing at all

  1. Give an example of a very good or very bad interaction you had with your student.

  2. Anything else you’d like to tell us or suggestions on how we could improve the program?

  3. For the midterm evaluation, should this student pass or fail?

    1. Pass

    2. Fail

  4. If you chose “fail” above, please fill in the reason for failure.

--
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 gsoc-mentors-ann...@googlegroups.com.
Visit this group at http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/d/optout.



--
Ed Cable
Mifos Community Manager
Director of Community Programs, Mifos Initiative
edc...@mifos.org | Skype: edcable | Mobile: 484.477.8649

Collectively Creating a World of 3 Billion Maries | http://openmf.org  

Note: As of Jan 1, 2014 my email has changed from edcable@openmf.org to edcable@mifos.org. Please update your address book accordingly.


Reply all
Reply to author
Forward
0 new messages