GSoC 2015 application: Difference between revisions
Jump to navigation
Jump to search
| Line 101: | Line 101: | ||
=== What is your plan for dealing with disappearing students? === | === What is your plan for dealing with disappearing students? === | ||
Disappearing students haven't been a problem for us in previous years. To prevent disappearances, we aim to make all reasonable efforts to accommodate the student and make them feel | |||
welcome. We will engage | welcome. We will engage students frequently by email and IRC, provide prompt response to student queries, | ||
and expect periodic | and expect periodic reports from mentors about the project status. We will also | ||
encourage the student to participate | encourage the student to participate on the public mailing list and IRC channel, | ||
with or without the mentor. Their progress should be regularly applied to our source | with or without the mentor. Their progress should be regularly applied to our source | ||
tree, if necessary in a | tree, if necessary in a side branch. All of these have shown to be effective | ||
with students | with students. | ||
Should this fail and | Should this fail and a student disappears for unforeseen reasons (which we | ||
hope will be very unlikely, since it has never happened before and nobody | hope will be very unlikely, since it has never happened before and nobody | ||
vanishes without good reason), make | vanishes without good reason), make | ||
reasonable attempts to contact them via alternative channels up to a private | reasonable attempts to contact them via alternative channels up to a private | ||
phone number. If more than 2 weeks have passed without a response, we will | phone number. If more than 2 weeks have passed without a response, we will consider the student as having dropped out and | ||
analyse the code submitted thus far | analyse the code submitted thus far for integration into our | ||
source tree. | source tree. | ||