116
edits
Difference between revisions of "Summer of Code/Application/2007"
Summer of Code/Application/2007 (view source)
Revision as of 17:44, 5 March 2007
, 17:44, 5 March 2007better keep around the original outline
(Entering: →When things go wrong) |
m (better keep around the original outline) |
||
| Line 51: | Line 51: | ||
== When things go wrong == | == When things go wrong == | ||
* Students. (Q14) | |||
* > Communication breakdown seldom occurs abruptly. Usually, a student losing interest will keep an ever lowering profile. The mentors will regularly query for status (at least once a week). When the student is in trouble, the mentros will go to lengths to support the student actively. The tasks will be planned ahead by the mentor, with informal interim reports (maybe) and milestones. Of course there may be RL problems prohibiting the continuation of the task (unpredictable). | |||
* Mentors. (Q15) | |||
* > There may be unforeseen difficulties for a mentor, leading to unavailability for some periods of time. The students can always turn to the very active irc channel for both general and specific inquiries. Mentors will update their status between them, so no students get left alone if a mentor drops out. | |||
=== Draft === | |||
This section presents the overall strategy used to prevent students and mentors from dropping out of their tasks. | This section presents the overall strategy used to prevent students and mentors from dropping out of their tasks. | ||