Jump to navigation Jump to search
|IRC channel: || #scummvm on
|Development mailing list: || https
= Part 1 - Application Form =
=== Why does your org want to participate in Google Summer of Code? (1000 characters) ===
In 2016 and every year from 2007 to 2014, the program has given us the opportunity to have talented and motivated students working with us. <span style="color:red">It also gave us the opportunity in 2016 to broaden our scope to RPG games, which was something we were looking for for years!</span>
What we hope to gain is valuable code contributions, and new developers for the project. In previous years, we've had students take up and complete tasks which were on our Ideas page, including for example full new engines ports. But also, some students have come up with new functionality, proposing and finally implementing it. These have been our favorites.
# <span style="color:red">dreammaster</span>
# fuzzie
# <span style="color:red">joostp</span>
# <span style="color:red">klusark (joelteichroeb)</span>
# <span style="color:red">md5</span>
# somaen
# strangerke
# <span style="color:red">uruk</span>
==== Backup Mentors ====
# <span style="color:red">botje (dharnie)</span>
=== How will you keep mentors engaged with their students? (1000 characters) ===
First of all, we have an internal rule that GSoC students have 2 mentors and not only just one, for the highest possible availability.
Then, we want our mentors to have the following qualities:
=== How will you help your students stay on schedule to complete their projects? ===
First of all we ask that students give a detailed schedule for their project as part of their application for GSoC. We know that this is likely to change after the start of the coding period, but this helps the students in splitting the work into small manageable tasks and organising their work. This also helps to make sure that the project is achievable and realistic. We also ask our student students to give regular feedback to their mentorsduring the coding period, at least once every 2 days. We also ask them to blog at least once a week about their progress.
We also strongly encourage the students to ask questions on our IRC channel. As an empirical fact, on IRC any student will be able to get support literally 24/7, as our developers are scattered all over the globe.
With those rules in place, it's very easy for the mentors and <span style="color:red">the co-mentors</span> to detect any difficulty a student may experience, and help them to fix it or work around it.
In parallel, the mentors regularly check if on the plans are achievable and progress of the student to make sure that the schedule remains realistic. If the student is ahead of schedule, some extra work may be discussed. At the opposite, if the student is behind schedule, discussions will occur very early among the mentors and then with the student to define what can be put in place so that the student completes the projects nevertheless.
=== How will you get your students involved in your community during GSoC? ===
=== How will you keep students involved with your community after GSoC? ===
<span style="color:red">Since GSoC 2014, we have decided to require the GSoC student code to be merged into our Master tree much earlier in the process if possible.</span> Our past experience told us it should be is very motivating for students to directly interact with our main repository and that this could potentially make some of them stay after the end of GSoC: it seems we were right as several former students have kept contributing for more than a year afterwards. This is obviously a very positive sign for us and we plan to proceed in the same way this year again.
=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
Since 2014, ScummVM acts as a GSoC umbrella for game preservation projects, such as its sister project, ResidualVM. The purpose is only to replace the game executable, not to enhance or replace the game assets.
ScummVM is a collection of game engines for playing classic graphical point-and-click adventure games on modern hardware. Recently we have also started adding engines for RPG games.
ResidualVM is a sister project of ScummVM games and was created in 2003. ResidualVM shares large blocks of common code with ScummVM, some developers and even a mentor.
- ScummVM supports classic 2D adventure games such as Monkey Island, Simon the Sorcerer, Space Quest, and many more. We have also started work to support 2D RPG games such as Dungeon Master. To this end, the Virtual Machines (called Engines) are complete reimplementations in C++ of the engines used in the original games. The number of engines is constantly growing thanks to a very agile and diversified development team and ScummVM is currently able to run more than 200 games. The VM approach followed by ScummVM results in efficient code, which has been ported to numerous Operating Systems (over 30). ScummVM has a highly productive team of about 45 currently active developers (out of an all-time pool of over 110130), working together on a codebase of 2,400800,000 lines of code. In addition ScummVM has many non-developer contributors, and a huge and highly active community.
- ResidualVM is a cross-platform 3D game interpreter which allows you to play some 3D adventure games, such as Cyan's Myst 3 and LucasArts' Lua-based 3D adventures: Grim Fandango and Escape from Monkey Island, provided you already have their data files. Like ScummVM, ResidualVM replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed.
- This year, we will also accept that students propose a task for RPG games, in the scope of our soon to be announced sister project RogueVM, also based on the ScummVM OSystem framework.
=== Application Instructions (1500 char) ===
=== Links ===
*Blog URL:

Navigation menu