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

Summer of Code/Application/2012 (view source)

Revision as of 13:04, 7 March 2012

110 bytes removed , 13:04, 7 March 2012

move mentors stuff

Fuzzie

193

edits

@@ Line 99: / Line 99: @@
 * '''Availability''' - How many hours per week can you spend working on this? What other obligations do you have this summer?
 * '''Bio''' - Who are you? What makes you the best person to work on this project?
-===  What criteria did you use to select these individuals as mentors? Please be as specific as possible. ===
-We want our mentors to have the following qualities:
-# Be able to commit to participating for the entire duration of the program. They first and foremost have to be available to their students and the mentor team.
-# Have a considerable track record hacking on ScummVM. They can help the students more effectively and in an immediate fashion this way.
-# Have the patience and skills to explain to their respective students on how to tackle their tasks. Also, to be able to help the students out in sticky situations.
-# Have a clear vision on how a task should proceed, both in broad strokes as well as in the technical details level. Allowing, of course, some freedom of movement to the students, where this is applicable.
-For this year, and this holds for our previous participations too, our mentors have volunteered to work with GSoC. This means that they primarily want to be involved in the program and that they are not dragged in to participate. Moreover, they have all been contributors to ScummVM for a long time. They feel comfortable around the ScummVM code and can guide students to perform their tasks. The majority of the mentors have also participated in past ScummVM GSoCs so they know their way around the procedures and have also refined their mentoring style. Some of them are/have been part of academia, guiding real students. They have seen the student mentalité in-action and have experience helping people along. We are drawing the best available from our pool of developers to mentor GSoC students this year.
 ===  Who will be your backup organization administrator? ===
@@ Line 120: / Line 111: @@
 * <span style="color:red">Availability during GSoC period (exams, ...)</span>
 * <span style="color:red">Having the patience and the ability to explain technical points</span>
+We want our mentors to have the following qualities:
+# Be able to commit to participating for the entire duration of the program. They first and foremost have to be available to their students and the mentor team.
+# Have a considerable track record hacking on ScummVM. They can help the students more effectively and in an immediate fashion this way.
+# Have the patience and skills to explain to their respective students on how to tackle their tasks. Also, to be able to help the students out in sticky situations.
+# Have a clear vision on how a task should proceed, both in broad strokes as well as in the technical details level. Allowing, of course, some freedom of movement to the students, where this is applicable.
+For this year, and this holds for our previous participations too, our mentors have volunteered to work with GSoC. This means that they primarily want to be involved in the program and that they are not dragged in to participate. Moreover, they have all been contributors to ScummVM for a long time. They feel comfortable around the ScummVM code and can guide students to perform their tasks. The majority of the mentors have also participated in past ScummVM GSoCs so they know their way around the procedures and have also refined their mentoring style. Some of them are/have been part of academia, guiding real students. They have seen the student mentalité in-action and have experience helping people along. We are drawing the best available from our pool of developers to mentor GSoC students this year.
 ===  What is your plan for dealing with disappearing students? ===