Difference between revisions of "Summer of Code/Application/2014"

Summer of Code/Application/2014 (view source)

368 bytes added , 12:08, 5 February 2014

1,190

edits

@@ Line 107: / Line 107: @@
 ;We all have exchanged sufficient contact information (including cell phone numbers etc.) to be able to discover our whereabouts. Should something really bad happen which precludes a mentor from fulfilling his duties (including personal reasons), we will attempt to shift students to new mentors among the existing mentors, or drawn from our backup pool of mentors. This will depend on the number of students we have to mentor.
-;We also defined for the last two years a co-mentoring system so the students have a primary and a secondary mentor, which comfort us in the idea that, in any case, the students will not be left hanging for any reason at all, no matter what happens.
+;We also defined for the last three years a co-mentoring system so the students have a primary and a secondary mentor, which comfort us in the idea that, in any case, the students will not be left hanging for any reason at all, no matter what happens.
+<span style="color:red">;On top of that, we have a specific #scummvm-gsoc channel on IRC where mentors (and only them) are connected all the time. We use this channel to keep ourselves informed constantly of the situation of each task, each student and eventually each mentor. A mentor wouldn't disappear without being noticed very quickly by this mean too.</span>
 ===  What steps will you take to encourage students to interact with your project's community before and during the program? ===