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

Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 29: Line 29:
= Part 1 - Application Form =
= Part 1 - Application Form =
=== Why does your org want to participate in Google Summer of Code? (1000 characters) ===
=== Why does your org want to participate in Google Summer of Code? (1000 characters) ===
Every year from 2007 to 2015, the program gave us the opportunity to have talented and motivated students working with us.  
Every year from 2007 to 2014, the program has given us the opportunity to have talented and motivated students working with us.


What we hope to gain is valuable code contributions. In previous years, we've had students take up and complete tasks which had been marked as "to-do" or which were specifically prepared for students (like full new engines ports). But also, some students have come up with a new functionality, proposing and finally implementing it. These have been our favorites.
We are particularly enthusiastic to participate this year as we are broadening our scope to include RPG games for the very first time, which brings with it a whole new group of potentially interested developers, students and users, and the opportunity to relive a new genre of classic games.


In addition, we hope to gain new developers for the project. We hope that after their projects, students will stick around and improve them or work on other interesting tasks. We hope that GSoC brings the students in touch with open source and, in our case, brings them in touch with game development.  
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.


We didn't manage to convince you last year, and therefore didn't benefit the great contributions of GSoC students. Hopefully this year will be our best GSoC ever!
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? ===
=== How many potential mentors do you have for this year's program? ===
Line 84: Line 84:
- 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 our previous participations that merging the student code early make them feel more involved, so we plan to do it again this year.</span>
- 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.</span>


=== How will you keep students involved with your community after GSoC? ===
=== How will you keep students involved with your community after GSoC? ===
<span style="color:red">In our latest two participations, we 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 should be 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.</span>
<span style="color:red">The latest two times we participated, we 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 should be 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.</span>


=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
Line 137: Line 137:
- 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.


- 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 ScummVM OSystem framework.
- 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) ===
=== Application Instructions (1500 char) ===
178

edits

Navigation menu