Open main menu

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

use scummvm.org alias
(use scummvm.org alias)
 
(6 intermediate revisions by 2 users not shown)
Line 32: Line 32:
|-
|-
|Backup Mentors: ||
|Backup Mentors: ||
* [[User:Aquadran|Paweł Kołodziejski]], Google Account: aquadran AT xtr.net.pl link_id: aquadran
* [[User:Aquadran|Paweł Kołodziejski]], Google Account: aquadran AT scummvm.org link_id: aquadran
|}
|}


Line 56: Line 56:
We have participated in the GSoC program for five years running, in 2007-2011.
We have participated in the GSoC program for five years running, in 2007-2011.


In 2011, 4 team members mentored 2 students. Sadly, one gave up quickly, but the other succeeded in objectifying the CruisE engine, which really needed it. After stepping back to review our processes, we feel we can still consider them to be mature. The problem came from internal tension that we addressed by redefining the project management structure.
In 2011, 4 team members mentored 2 students. One student succeeded in objectifying the CruisE engine, which really needed it. The other student unfortunately gave up fairly quickly after starting work (although the work done was eventually merged into our main repository, after being worked on further by a team member). After stepping back to review our processes, we feel we can still consider them to be mature. Part of the problems which caused the student to quickly give up came from internal tensions, that we have since addressed by redefining the project management structure.


In 2010 we were granted 4 slots and had 6 mentors, thus we had nice backup mentoring for every student. All four passed the finals this time, and we merged in their code. One student still continues to contribute to the project. We addressed several long standing project needs and it was just excellent.
In 2010 we were granted 4 slots and had 6 mentors, thus we had nice backup mentoring for every student. All four passed the finals this time, and we merged in their code. One student still continues to contribute to the project. We addressed several long standing project needs and it was just excellent.
Line 100: Line 100:
* '''Bio''' - Who are you? What makes you the best person to work on this project?
* '''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. ===
===  Who will be your backup organization administrator? ===
* strangerke
* djwillis
 
===  What criteria did you use to select your mentors for this year's program? Please be as specific as possible. ===
We want our mentors to have the following qualities:
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.
# 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.
Line 108: Line 112:


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.
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? ===
* strangerke
* djwillis
===  What criteria did you use to select your mentors for this year's program? Please be as specific as possible. ===
<span style="color:red">To be done</span>
* <span style="color:red">Originator of the task</span>
* <span style="color:red">Technically able to do it him/herself</span>
* <span style="color:red">If possible, previous positive mentorships</span>
* <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>


===  What is your plan for dealing with disappearing students? ===
===  What is your plan for dealing with disappearing students? ===
Line 149: Line 141:
=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===
=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===
N/A
N/A
<span style="color:red">+++++++</span>
152

edits