Summer of Code/Application/2019
- 1 Introduction & overview
- 2 Please address all items in RED ;-)
- 3 Part 1 - Application Form
- 3.1 Why does your org want to participate in Google Summer of Code? (1000 characters)
- 3.2 How many potential mentors do you have for this year's program?
- 3.3 How will you keep mentors engaged with their students? (1000 characters)
- 3.4 How will you help your students stay on schedule to complete their projects?
- 3.5 How will you get your students involved in your community during GSoC?
- 3.6 How will you keep students involved with your community after GSoC?
- 3.7 Has your org been accepted as a mentoring org in Google Summer of Code before?
- 3.8 Which years did your org participate in GSoC?
- 3.9 What is your success/fail rate per year?
- 3.10 If your org has applied for GSoC before but not been accepted, select the years:
- 3.11 Are you part of a foundation/umbrella organization?
- 3.12 What year was your project started?
- 3.13 Where does your source code live?
- 4 Part 2 - Organization Profile
- 4.1 Very Short Description of the Organization (80 char)
- 4.2 Organization Category
- 4.3 Technology Tags
- 4.4 Topic Tags
- 4.5 Short Description of the Organization (180 char)
- 4.6 Long Description of the Organization (2000 char)
- 4.7 Application Instructions (1500 char)
- 4.8 Proposal Tags
- 4.9 Contact Methods
- 4.10 Links
Introduction & overview
|Participation in prior SoCs:||Yes|
|Applications for prior SoCs:||2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007|
|Organization co-administrator:||<To be determined>|
|Backup administrator:||<To be determined>|
|Ideas page:||Ideas 2019|
|IRC channel:||#scummvm on irc.freenode.net|
|Development mailing list:||http://lists.scummvm.org/listinfo/scummvm-devel|
Please address all items in RED ;-)
Part 1 - Application Form
Why does your org want to participate in Google Summer of Code? (1000 characters)
Almost every year since 2007, the program has given us the opportunity to have talented and motivated students working with us. It also gave us the opportunity in 2016 to broaden our scope to RPG games, which was something we were looking for for years!
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.
A number of students have stayed involved after the summer to become full team members and continue working on their projects, and we hope to make this happen this year as well.
How many potential mentors do you have for this year's program?
7 (6-10) Criezy might be participating too (and hopefully more people, to be updated)
- aquadran (ResidualVM)
- botje (ResidualVM) (Absent during 3 weeks in summer)
- djwillis (ScummVM)
- dreammaster (ScummVM)
- sev (ScummVM)
- somaen (ResidualVM)
- strangerke (ScummVM)
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 just one, for the highest possible availability.
Then, we want our mentors to have the following qualities:
- Be a volunteer and be able to commit to participating for the entire duration of the program. They have to be available to their students and the mentor team.
- Have a considerable track record hacking on ScummVM or ResidualVM. They can help the students more effectively and in an immediate fashion this way.
- Have the patience and skills to explain to their respective students how to tackle their tasks. Also, to be able to help the students out when they are 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, with of course some freedom movement to the students.
- Be regularly present on our #scummvm-gsoc channel, where we continuously inform each others of the progresses and issues of the students.
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 organizing their work. This also helps to make sure that the project is achievable and realistic.
We also ask our students to give regular feedback to their mentors during the coding period, at least once every 2 days, and to blog at least once a week about their progress.
It's therefore easy for the mentors and the co-mentors to detect any difficulty a student may experience, and help them to fix it or work around it.
In parallel, mentors check the progress to make sure the schedule remains realistic. 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?
Before and during GSoC, we'll consider students as special developers, but developers nonetheless. They will therefore have equivalent rights, privileges and duties. For instance, - We first ask our students to write introductory letters to our development list and their blog so everyone is familiar with their background, skills and assigned task. - We created documentation in order to help the students to familiarize themselves with the project, particularly 'Developer Central' and our wiki. - They are encouraged to take part in discussions, whatever the medium on which these discussions occur. - They will be able to get support from and chat with the team 24/7 on our IRC channels. They are voiced (+v) so that everybody knows who they are. - We noticed during previous summers that merging the student code early make them feel more involved, so we plan to do it again this year.
How will you keep students involved with your community after GSoC?
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. Our past experience told us it 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?
Which years did your org participate in GSoC?
2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2016, 2017, 2018
What is your success/fail rate per year?
- 2018: Pass 3 / 1 Fail
- 2017: Pass 2 / 0 Fail
- 2016: Pass 3 / 1 Fail
- 2014: Pass 5 / 0 Fail
- 2013: Pass 4 / 0 Fail
- 2012: Pass 3 / 1 Fail
- 2011: Pass 1 / 1 Fail
- 2010: Pass 4 / 0 Fail
- 2009: Pass 4 / 1 Fail
- 2008: Pass 5 / 1 Fail
- 2007: Pass 5 / 2 Fail
If your org has applied for GSoC before but not been accepted, select the years:
Are you part of a foundation/umbrella organization?
What year was your project started?
Where does your source code live?
Part 2 - Organization Profile
Very Short Description of the Organization (80 char)
ScummVM is a GSoC umbrella for game preservation projects
End user applications
C++, SDL, OpenGL, Assembly, Lua
games, game engines, software preservation, software archeology
Short Description of the Organization (180 char)
ScummVM is a GSoC umbrella for game preservation projects focused on reliving games by providing a replacement for their executables on modern platforms.
Long Description of the Organization (2000 char)
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. The project started in 2001 and we recently widened our scope to RPG engines.
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 130), working together on a codebase of 2,800,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.
Application Instructions (1500 char)
Your application has two important purposes: It should clearly identify the goals of your project, and it should convince us that you are the right person for this task.
In particular, your application is your opportunity to show us that you understand what you'll be doing for the task, and to demonstrate that you've spent some time thinking about it, its difficulties, strategies for overcoming these, and have a good estimate of how much time they will take. Based on that, we will ask you a realistic planning for the 12 weeks of GSoC, including the deliverables expected at mid-term and at the end of the GSoC. In order to be complete, we also expect you to make a pull request, for example for a bug fix. The purpose is to ensure you know how to use Git, and that you had a look at our coding conventions.
We don't expect you to produce a perfect application without any help at all. We strongly encourage you to discuss your plans and your application with us while you're preparing it, to ensure your ideas align well with our own thoughts on the tasks, and that your objectives are achievable. It is also the perfect chance to already get to know your potential mentors and the rest of the team. Don't hesitate to join the IRC channels and ask questions: keep in mind that there are no stupid questions!
In order to help you structure your application, we summarized our requirements in a template: http://wiki.scummvm.org/index.php/GSoC_Application
new game engine, scummvm, residualvm, reverse engineering, gui, rendering
- IRC Channel: http://wiki.scummvm.org/index.php/Summer_of_Code/GSoC_Contact
- Mailing List: http://wiki.scummvm.org/index.php/Summer_of_Code/GSoC_Contact
- General Email: firstname.lastname@example.org