[SoC] Fwd: Midterm Evaluations Next Week

[Wolf Bergenheim]

Heads up everyone!

Next week between Monday the 12th and Friday the 16th 1900 UTC you
shall submit your mid-term evaluations.  If you miss your deadline it
means you are out. So I hope for your sake you will make it on time.
;) This is also true for mentors. If the mentors don't submit the
mid-term evaluations on time, it means that the student is out. I will
fill in any pending mentor mid-term evaluations, however: unless other
arrangements have been made I WILL file a FAILing report. I realize
that this seems awfully harsh, but it is meant to be a wakeup call!

I've waited patiently the last three weeks to see if the weekly
reports would start coming in on time, meaning that you are getting
used to the idea, but the opposite seems to be true. Last week for
instance only HALF of you sent in a report at all, and NONE on time!
This cannot go on. Reading your reports it seems that you think that
you should hold off writing the weekly report until you have completed
a feature. Well, that is WRONG! Zero points and an F for that thought.
The whole point is to get sort of a timed snapshot of what is going on
with your projects. It's not a snapshot if we wait for feature
completeness. So please don't do anything before you have fired off
that report. I expect to see a whole lot of: I did this and that, now
working on this and plan to start working on that after I finish this.
Ok? That way we get a more active dynamic picture on what you are
doing and since the reports always come at the same time we can much
more easily see if you are struggling, and help out. THAT is the whole
point of the weekly reports.

Any questions?

Remember to fill in those mid-term evaluations by 19:00 UTC on July
16th. Here is a handy countdown timer:
http://timeanddate.com/counters/customcounter.html?day=16&month=7&year=2010&hour=19&min=00&sec=00&p0=0

Read below for instructions. If you have any problems or questions, please ask!

Regards,
Wolf Bergenheim
OSGeo GSoC 2010 Administrator

---------- Forwarded message ----------
From: Carol Smith <carols at google.com>
Date: Mon, Jul 5, 2010 at 21:21
Subject: Midterm Evaluations Next Week
To: Google Summer of Code Mentors List
<google-summer-of-code-mentors-list at googlegroups.com>


Hi GSoC 2010 Mentors and Org Admins,
Per the program timeline [0], starting next week 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
12 July you will be able to submit an evaluation for your student(s).
The deadline is 19:00 UTC on 16 July. You can find the evaluation
linked in red in the left-hand nav of Melange once the evaluation
window opens. 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.
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 alloted.  Only
primary mentors or org admins may submit evaluations of their
students.
You must submit an evaluation for every student you are the primary
mentor for this year. We want an evaluation on file for every student.
You must fill out the entire survey in one session as there's no
auto-save in Melange yet. You may submit, modify, and resubmit an
evaluation as many times as you choose up until the deadline.
**Students must have an evaluation on file from both themselves *and*
their mentors in order to receive their midterm payments.** Please be
mindful of this and submit your evaluations on time so your students'
payments are not delayed.
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. In fact, why not read the
whole thing? IMHO it's quite a useful manual on being a GSoC mentor.
Please let me know directly if you have questions or concerns.
[0] - http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline
[1] - http://socghop.appspot.com
[2] - http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#evaluations
[3] - http://en.flossmanuals.net/GSoCMentoring/Evaluations
Cheers,
Carol
------------------------

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

This is my first year
2-3 years
More than 3 years

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

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

Voice (phone, Skype, etc.)
IM/IRC
Private emails
Mailing Lists
Student blog updates
In-person meeting(s)

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 timezones 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

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
Good
Bad

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

Very Good
Good
Bad

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

Give an example of a very good or very bad interaction you had with
your student.
What one thing could you do to improve the quality of interaction and
communications 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 List" group.
To post to this group, send email to
google-summer-of-code-mentors-list at googlegroups.com.
To unsubscribe from this group, send email to
google-summer-of-code-mentors-list+unsubscribe at googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-summer-of-code-mentors-list?hl=en.



-- 
<8  )---- Wolf Bergenheim ----(  3>