|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 ==
We want our mentors to have the following qualities:
=== 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>