|Organization administrator: || strangerke
|Organization co-administrator: ||
|Backup administrator: || wjpalenstijn
* [[User:Digitall|David Turner]], Google Account: digitall AT scummvm.org link_id: digitall
* [[User:Somaen | Einar Johan Trøan Sømåen]], Google Account: somaen AT scummvm.org link_id: somaen
|Backup Mentors: ||
=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===
== Mentors ==#
Strangerke# DJWillis (TBC)# sev (TBC)# somaen (TBC)
== Backup Mentors ==
<span style= "color:red">TO BE DONE</span>
We want our mentors to have the following qualities:
# 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.
# Be regularly present on our #scummvm-gsoc channel, where we continuously inform each others of the progresses and issues of the students
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 several years. 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 have been GSoC students one of the previous years. 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 again.
=== What is your plan for dealing with disappearing students? ===
;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.
;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? ===
The development team actively uses the forums, IRC, Wiki and the development mailing list during
the entire project development . We consider out students to be special, but developers nonetheless. Each developer including our students is encouraged to take part in discussions, whatever the means these discussions occur. As a pragmatic fact, on IRC any student will be able to get support literally 24/7, as our developers are scattered all over the globe.
;Not only the mentors, but also the entire development team, are encouraged to communicate with the students. The students are marked with a special flag on our IRC channel, so everyone knows who they are . And we require the students to write introductory letters to our development list, so everyone will have an impression about them, their skills and their assigned task (of course).
;In order to help the students
familiarize themselves with the project, we also have created several pieces of documentation for them. In particular, we have an exhaustive developer central where we describe the all-important internals of ScummVM. This is valuable as a quick reference as well as during the initial explorations of the codebase.
=== What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? ===
<span style="color:red">Last year we decided to require the GSoC student code be merged into our Master tree much earlier in the process, if possible. Our past experience was telling it should be very motivating for students to directly interact with our main repository and could potentially make some of them stay after the end of GSoC: it seems we were right as 2 students out of 4 are still actively contributing, while a 3rd one is still present from times to times. This is obviously for us a very positive sign and we plan to proceed the same way this year again.</span>
=== If you chose "veteran" in the organization profile dropdown, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. ===
TO BE DONE</span>
=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===
<span style="color:red">TO BE DONE</span>