[haiku-gsoc] Reminders : Mid-term evaluations, Milestone report, providing code, talking regularly.

From: Matt Madia <mattmadia@xxxxxxxxx>
To: haiku-gsoc@xxxxxxxxxxxxx
Date: Thu, 30 Jun 2011 21:14:03 -0400
Howdy

Important Dates
-------------------------

July 11th - Mentors and students can begin submitting mid-term evaluations.
July 15th - Mid-term evaluations deadline

The mid-term evaluation is to be done at the google-melange.com website.


Additionally, there is another milestone report coming up.
       * DUE: Monday, July 11 - Monday, July 18
       * BLOG POST
       * summarize what you have done so far
       * mention next goals (now to 3/4-term)

==================

Here's a snippet from Haiku's students page, to remind all of you ...

Words of Advice
------------------------

Reading and following this advice will do wonders for ensuring that
your Google Summer of Code experience will be something to be proud
of.

   1. Communicate frequently
      This includes both with your mentor and on the haiku-gsoc
mailing list. It is important for your mentors to have a clear picture
of what you are doing, have done, and plan to do. While being
self-sufficient is a worthwhile trait, it is not an ideal trait for a
Google Summer of Code participant -- Haiku expects you to utilize our
mentors, that is why they are there.
   2. Provide code frequently
      There is a saying in open source -- commit often, commit
frequently. Take that advice to heart. Smaller patches and code
snippets are easier for the mentors to review. It also gives them more
chances to suggest better approaches and keep you on target. In turn,
this will make you more productive and more likely to succeed!
   3. When you do not have code, it is even more critical to converse
frequently.
      If you aren't coding, what are you doing? How are you moving
closer to your goal? What problems are you analyzing? What questions
and ideas do you have?


Pass or Fail Criteria
-----------------------------

As you know, Google Summer of Code has two evaluation points --
mid-term (July 15) and final (August 26). If you happen to receive a
failing mark at either point, you are not paid that portion and your
internship comes to an abrupt end. Haiku also introduces a 1/4-term
and 3/4-term milestones, to further help you the student with time
management. While the 1/4-term and 3/4-term are not recognized by
Google, your mentor will use those milestones in determining you
mid-term and final evaluation. There are two areas that are considered
during the evaluation: the code output and communication/interactions.

   1. Code.
      This includes everything from 'commit worthy' patches to all the
code (and non-code, such as design documents or pseudo code) leading
up to that polished patch. In other words, if for some reason you and
your mentor pursue an approach that turns out to be a dead end you
will not be punished.
   2. Communication.
      This includes talking directly with your mentor, engaging the
haiku-gsoc list to seek a larger audience, and posting the Milestone
Blog/Email Reports.

In other words,we expect you to be writing code and talking with one
or more mentors on a daily basis. Anything less will hurt your
mid-term and final evaluation! Do not expect to be able to cram days,
weeks, or months of work into a shorter period and receive a passing
evaluation.

==================



The GSoCStudentGuide has a chapter explaining the evaluations as well
: http://www.booki.cc/gsocstudentguide/evaluation/



In other words, make sure that you are providing your mentor(s) with
code to review & monitor.  Make sure to talk with them, ideally on
this mailing list -- this will allow other people in the mentor pool
to respond.



--mmadia
[haiku-gsoc] Reminders : Mid-term evaluations, Milestone report, providing code, talking regularly.

Other related posts:
