Jump to navigation Jump to search

Summer of Code/Application/2014

4,550 bytes added, 15:21, 14 February 2014
|Organization administrator: || strangerke
|Organization co-administrator: || sev
|Backup administrator: || wjpalenstijn
* [[User:Digitall|David Turner]], Google Account: digitall AT link_id: digitall
* [[User:Somaen | Einar Johan Trøan Sømåen]], Google Account: somaen AT link_id: somaen
* [[User:Md5|Filippos Karapetis]], Google Account: md5 AT link_id: md5
* [[User:Dreammaster|Paul Gilbert]]
|Backup Mentors: ||
=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===
==== Mentors ====# djwillis# Strangerkedreammaster# DJWillis (TBC)lordhoto# md5# sev (TBC)# somaen (TBC)# strangerke
==== Backup Mentors ====
# wjp
# fuzzie
# aquadran(TBC)
<span style="color:red">TO BE DONE</span>=== Description ====We have 10 potential (co) mentors or backup mentors this year.
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.
# <span style="color:red"> Be regularly present on our #scummvm-gsoc channel, where we continuously inform each others of the progresses and issues of the students </span>
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. <span style="color:red">Some of them have been GSoC students one of the previous years. </span> 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.
;<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? ===
The development team actively uses the project resources, including 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 mentorsWe consider our students to be special, but also the entire development team, are developers nonetheless. Each developer including our students is encouraged to communicate with take part in discussions, whatever the studentsmeans these discussions occur. The students are marked with As a special flag pragmatic fact, on our IRC channelany student will be able to get support literally 24/7, so everyone knows who they as our developers are. And we require scattered all over 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)globe.
;Support and feedback is not only a function provided by the mentors, but the entire development team and community, are encouraged to communicate constructively with the students. The students are marked with a special flag on our IRC channel (voice), so everyone knows who they are. We require the students to write introductory letters to our development list and their blog so everyone will have a sensible background 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 key pieces of documentation for them. In particular, we have an exhaustive 'developer central ' on our Wiki where we describe the all-important internals of ScummVMand finding your way around the project. This is highly 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>
=== 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.===
<span style="color:red">We'd like to vouch for ResidualVM.</span>
<span style="color:red">This project is a sister project of ScummVM, dealing with 3D Adventure games. We share a lot of common code and developers (and even mentors). </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. ===
We have participated in the GSoC program for the last seven years. From 2007-2013. Below are details of the successes and challenges we have encountered grouped by year. '''2013:''' 4 students mentored by 6 team members. Each mentor was also co-mentor of another task.  All the students passed, and 2 students are still actively contributing the project and one student is still regularly on our IRC channel. One of the active students would also like to participate again in GSoC this year as a student. Merging code earlier gave excellent results and we'll do the same if possible this year in order to build on the great results of this year. '''2012:''' 4 students mentored by 5 team members. Each mentor was also the co-mentor of another task. 3 students passed, and one failed at mid-term. One student is still actively contributing to the project and volunteered to be a mentor for GSoC 2013<span style="color:red">TO BE DONEand GSoC 2014</span>, which is really awesome. Based on discussion with other projects and our experience one of the key outcomes from this year was to look at merging student code earlier in the GSoC process and encouraging students to be much closer to mainline development. We modified our processes accordingly for the next year. '''2011:''' 2 students mentored by 4 team members. Each mentor was also the co-mentor of another task. 1 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. '''2010:''' 4 students mentored by 6 team members. Each mentor was also the co-mentor of another task. 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 this was a very good year for the project. '''2009:''' 5 students mentored by 6 team members. Some co-mentoring happened. 4 of our students passed, and one failed the finals. The year was a the success and all the students' code was merged within three months into the main development line. We considered this to be a good outcome. '''2008:''' 6 students mentored by 7 mentors.  5 of our students were so successful that their code is included in the mainline of ScummVM, and we consider it a great achievement that 4 of the students continued to contribute to the project afterwards. '''2007:''' 7 students mentored by 4 mentors. 5 of our students passed. Two of our students continued to become active, regular developers in the team after having their respective code contributions integrated in the codebase. Two of the students did not succeeded in their projects. All in all, we maintain that we have been refining our method of student selection and balancing the workload and commitment required to achieve great outcomes in the past years and this refinement leads to generally better results each year.  The discussions, testimonials and proposed actions which the mentor summit has raised - and which we have participated in during our involvement with GSoC - have helped us a great deal. Our new wider management organization has also proven its efficiency during these last 2 years, and we hope to continue improving the experience for all parties in the future. Summary pass/fail: <span style="color:red">2013: 4/0</span> 2012: 3/1 2011: 1/1 2010: 4/0 2009: 4/1 2008: 5/1 2007: 5/2
=== 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>

Navigation menu