--- Begin Message ---
|
Subject: |
[GSoC Mentors Announce] Re: 2013 Google Summer of Code Mentor Midterm Evaluations 29 July - 2 August |
|
Date: |
Thu, 1 Aug 2013 11:42:39 -0700 |
Hi everyone,
Just a friendly reminder that there are just about 24 hours left to
submit your midterm evaluation if you are a mentor or org admin for a
GSoC student this year. Don't delay, submit today!
Cheers,
Carol
On Sun, Jul 21, 2013 at 1:49 PM, Carol Smith <address@hidden> wrote:
> Hi GSoC 2013 Mentors and Org Admins,
>
> Per the program timeline [0], starting on Monday, 29 July 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 [1]. Starting at 19:00 UTC on 29
> July 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 (or co-mentor) for. If you are curious about
> who can see evaluations after they are submitted, please check out the FAQ
> on Evaluations [2]. I have also pre-published the evaluation questions below
> in this email so you can prepare. The deadline is 19:00 UTC on Friday, 2
> August.
>
> 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 time allotted. Primary mentors,
> co-mentors, and org admins may all submit evaluations of their
> students.**Students must have an evaluation on file from both themselves
> *and* their mentors in order to receive their midterm payments.** There is
> no excuse for missing the submission of a student's evaluation.
>
> You must submit an evaluation for every student you are the primary mentor
> for this year. You must fill out the entire survey in one session as there's
> no auto-save in Melange. You may submit, modify, and resubmit an evaluation
> as many times as you choose up until the deadline.
>
> 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 [3] helpful as well.
> There's some excellent wisdom in there from your fellow mentors and org
> admins on the evaluation process.
>
> Finally, a reminder: This year we will not allow any mentor who misses an
> evaluation deadline to attend the mentor summit (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 invited to attend the
> mentor summit this year.
>
> Please let me know directly if you have questions or concerns.
>
> [0] - http://www.google-melange.com/gsoc/events/google/gsoc2013
> [1] - http://google-melange.com
> [2] -
> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#9._How_do_evaluations_work
> [3] - http://www.booki.cc/gsoc-mentoring/evaluations/
>
> Cheers,
> Carol
>
> ------
>
> How many years have you been a mentor for Google Summer of Code (Total -
> this doesn’t have to be consecutive)?
>
> This is my first year
>
> 2-3 years
>
> More than 3 years
>
> If you answered 2-3 years or more than 3 years, what years did you
> participate?
>
> How many years have you been a student in Google Summer of Code?
>
> I have never been a student
>
> 1 year
>
> 2 years
>
> 3+ years
>
> If you answered 2 years or 3+ years, what years did you participate?
>
> At what point did you first make contact with your student?
>
> Before the program was announced
>
> After my organization was selected to participate in Google Summer of Code
>
> During the student application/acceptance phase of the program
>
> During the community bonding period
>
> After the start of coding
>
> How often do you and your student interact?
>
> Daily
>
> Every few days
>
> Weekly
>
> Every few weeks
>
> Monthly
>
> Less than once a month
>
> How do you communicate with your student? (Check all that apply)
>
> Google+ Hangout
>
> Voice (phone, Skype, etc.)
>
> IM/IRC
>
> Private emails
>
> Mailing Lists
>
> Student blog updates
>
> In-person meeting(s)
>
> Other
>
> Of the communication methods listed above, which do you use most frequently?
>
> 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-5 hours
>
> 5-10 hours
>
> 10-15 hours
>
> 15-20 hours
>
> More than 20 hours per week
>
> How many time zones apart from your student are you?
>
> Less than 3
>
> 3-6
>
> More than 6
>
> How often do you require status updates from your student?
>
> Daily
>
> Every few days
>
> Weekly
>
> Only when explicitly asked for by me
>
> Please rate the quality of your interactions and communications with the
> student (consider his/her communication with you as well as your responses).
>
> Very Good (Student is regularly responsive and the quality of communication
> is high)
>
> Good (Student is somewhat responsive and the quality of communication is
> okay)
>
> Bad (Student is only somewhat or not at all responsive and the quality of
> communication is low)
>
> Please rate the quality of the student’s interactions with your organization
> and community.
>
> Very Good (Student is regularly responsive and the quality of communication
> is high)
>
> Good (Student is somewhat responsive and the quality of communication is ok)
>
> Bad (Student is only somewhat or not at all responsive and the quality of
> communication is low)
>
> Is your student on track to complete his/her project?
>
> The student has already completed his/her project
>
> He/she is ahead of schedule
>
> He/she is on schedule
>
> He/she is behind schedule
>
> Please rate the quality of code/work the student has produced thus far.
>
> Amongst the best people I’ve ever worked with
>
> Solid-quality performance
>
> Good performance
>
> Mediocre performance
>
> Disappointing or not performing at all
>
> How do you feel about the new Google Summer of Code timeline?
>
> Less accommodating to my school/work schedule
>
> Equally accommodating to my school/work schedule
>
> More accomodating to my school/work schedule
>
> If you answered “less accommodating” above, what would be a better schedule
> for you?
>
> Give an example of a very good or very bad interaction you had with your
> student.
>
> Anything else you’d like to tell us or suggestions on how we could improve
> the program?
>
> For the midterm evaluation, should this student pass or fail?
>
> Pass
>
> Fail
>
>
--
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 http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/groups/opt_out.
--- End Message ---