8,012
edits
Difference between revisions of "Summer of Code/Application/2019"
Jump to navigation
Jump to search
m
Summer of Code/Application/2019 (view source)
Revision as of 00:06, 23 February 2019
, 00:06, 23 February 2019oops - fixed 2010 link
Strangerke (talk | contribs) (→Mentors: Eugene confirmed participation) |
m (oops - fixed 2010 link) |
||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
|Participation in prior SoCs: || Yes | |Participation in prior SoCs: || Yes | ||
|- | |- | ||
|Applications for prior SoCs: || [[Summer of Code/Application/2017|2018]], [[Summer of Code/Application/2017|2017]], [[Summer of Code/Application/2016|2016]], [[Summer of Code/Application/2015|2015]], [[Summer of Code/Application/2014|2014]], [[Summer of Code/Application/2013|2013]], [[Summer of Code/Application/2012|2012]], [[Summer of Code/Application/2011|2011]], [[Summer of Code/Application/2009|2009]], [[Summer of Code/Application/2008|2008]], [[Summer of Code/Application/2007|2007]] | |Applications for prior SoCs: || [[Summer of Code/Application/2017|2018]], [[Summer of Code/Application/2017|2017]], [[Summer of Code/Application/2016|2016]], [[Summer of Code/Application/2015|2015]], [[Summer of Code/Application/2014|2014]], [[Summer of Code/Application/2013|2013]], [[Summer of Code/Application/2012|2012]], [[Summer of Code/Application/2011|2011]], [[Summer of Code/Application/2010|2010]], [[Summer of Code/Application/2009|2009]], [[Summer of Code/Application/2008|2008]], [[Summer of Code/Application/2007|2007]] | ||
|- | |- | ||
|Organization administrator: || strangerke | |Organization administrator: || strangerke | ||
| Line 36: | Line 36: | ||
=== How many potential mentors do you have for this year's program? === | === How many potential mentors do you have for this year's program? === | ||
<span style="color:red"> | 7 (6-10) <span style="color:red">Criezy might be participating too (and hopefully more people, to be updated)</span> | ||
==== Mentors ==== | ==== Mentors ==== | ||
# dreammaster | # aquadran (ResidualVM) | ||
# sev | # botje (ResidualVM) <span style="color:red">(Absent during 3 weeks in summer)</span> | ||
# strangerke | # djwillis (ScummVM) | ||
# dreammaster (ScummVM) | |||
# sev (ScummVM) | |||
# somaen (ResidualVM) | |||
# strangerke (ScummVM) | |||
=== How will you keep mentors engaged with their students? (1000 characters) === | === 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. | 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: | 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. | * 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 | * 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 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. | * 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. | ||
| Line 54: | Line 57: | ||
=== How will you help your students stay on schedule to complete their projects? === | === 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. | 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. | ||
| Line 115: | Line 116: | ||
=== Technology Tags === | === Technology Tags === | ||
C++, SDL, OpenGL, Assembly | C++, SDL, OpenGL, Assembly, Lua | ||
=== Topic Tags === | === Topic Tags === | ||
games, game engines, software preservation | games, game engines, software preservation, software archeology | ||
=== Short Description of the Organization (180 char) === | === Short Description of the Organization (180 char) === | ||
| Line 124: | Line 125: | ||
=== Long Description of the Organization (2000 char) === | === 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. | 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. | 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. | 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. | - 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. | ||
| Line 149: | Line 146: | ||
=== Proposal Tags === | === Proposal Tags === | ||
new game engine, scummvm, residualvm, reverse engineering | new game engine, scummvm, residualvm, reverse engineering, gui, rendering | ||
=== Contact Methods === | === Contact Methods === | ||