Difference between revisions of "Summer of Code/Application/2020"

Jump to navigation Jump to search
 
(12 intermediate revisions by 3 users not shown)
Line 14: Line 14:
|Organization co-administrator: || sev
|Organization co-administrator: || sev
|-
|-
|Backup administrator: || <To be determined>
|Backup administrator: || criezy
|-
|-
|Project License: || GPLv2+
|Project License: || GPLv2+
Line 37: Line 37:


=== How many potential mentors do you have for this year's program? ===
=== How many potential mentors do you have for this year's program? ===
8 (7-10) <span style="color:red">Hopefully more people will be added, to be updated</span>
6 (Category 6-10 for Google) <span style="color:red">Hopefully more people will be added, to be updated</span>
==== Mentors ====
==== Mentors ====
# aquadran (ResidualVM)
# aquadran (ResidualVM) <span style="color:red">??</span>
# botje (ResidualVM) <span style="color:red">(Absent during 3 weeks in summer)</span>
# bgK (ScummVM)
# criezy (ScummVM)
# criezy (ScummVM)
# djwillis (ScummVM)
# djwillis (ScummVM) <span style="color:red">??</span>
# dreammaster (ScummVM)
# dreammaster (ScummVM)
# morealrecordings (ScummVM)
# sev (ScummVM)
# sev (ScummVM)
# somaen (ResidualVM)
# somaen (ResidualVM) <span style="color:red">??</span>
# strangerke (ScummVM)
# strangerke (ScummVM)


Line 70: Line 71:
Before and during GSoC, we'll consider students as special developers, but developers nonetheless.
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,
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 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.
* 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 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.
* 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.
* 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? ===
=== How will you keep students involved with your community after GSoC? ===
Line 85: Line 86:


=== What is your success/fail rate per year? ===
=== What is your success/fail rate per year? ===
*2019: Pass 3 / 1 Fail
*2018: Pass 3 / 1 Fail
*2018: Pass 3 / 1 Fail
*2017: Pass 2 / 0 Fail
*2017: Pass 2 / 0 Fail
Line 99: Line 101:
=== If your org has applied for GSoC before but not been accepted, select the years: ===
=== If your org has applied for GSoC before but not been accepted, select the years: ===
*2015
*2015
=== Are you part of a foundation/umbrella organization? ===
No


=== What year was your project started? ===
=== What year was your project started? ===
Line 109: Line 108:
https://github.com/scummvm/scummvm
https://github.com/scummvm/scummvm
https://github.com/residualvm/residualvm
https://github.com/residualvm/residualvm
=== Is your organization part of any government? ===
No


= Part 2 - Organization Profile =
= Part 2 - Organization Profile =
Line 122: Line 124:
=== Topic Tags ===
=== Topic Tags ===
games, game engines, software preservation, software archeology
games, game engines, software preservation, software archeology
=== Idea List ===
https://wiki.scummvm.org/index.php?title=Summer_of_Code/GSoC_Ideas_2020


=== Short Description of the Organization (180 char) ===
=== Short Description of the Organization (180 char) ===
Line 133: Line 138:
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 35 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.
- 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.
Line 140: Line 145:
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.
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.
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 entire GSoC, including the deliverable expected at each partial 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!
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:
In order to help you structure your application, we summarized our requirements in a template:
http://wiki.scummvm.org/index.php/GSoC_Application
https://wiki.scummvm.org/index.php/GSoC_Application


=== Proposal Tags ===
=== Proposal Tags ===
Line 156: Line 161:


=== Links ===
=== Links ===
*Google+: https://plus.google.com/100512255374893262465
*Facebook: https://www.facebook.com/pages/ScummVM/7328341409
*Twitter: https://twitter.com/scummvm
*Twitter: https://twitter.com/scummvm
*Blog URL: http://planet.scummvm.org/
*Blog URL: https://planet.scummvm.org/

Navigation menu