TrustedUser
2,147
edits
Difference between revisions of "Summer of Code/Application/2018"
Jump to navigation
Jump to search
Summer of Code/Application/2018 (view source)
Revision as of 14:10, 16 February 2018
, 14:10, 16 February 2018→Introduction & overview: confirm admins
(First draft of GSoC 2018 application) |
(→Introduction & overview: confirm admins) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 10: | Line 10: | ||
|Applications for prior SoCs: || [[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|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]] | ||
|- | |- | ||
|Organization administrator: || | |Organization administrator: || strangerke | ||
|- | |- | ||
|Organization co-administrator: || | |Organization co-administrator: || sev | ||
|- | |- | ||
|Backup administrator: || | |Backup administrator: || criezy | ||
|- | |- | ||
|Project License: || GPLv2+ | |Project License: || GPLv2+ | ||
| 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) === | ||
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. | 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. | ||
| 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? === | ||
[6-10] | |||
==== Mentors ==== | ==== Mentors ==== | ||
# aquadran | # aquadran | ||
| Line 56: | 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? === | ||
<span style="color:red">Text modified to make it fit in 1000 char</span> | |||
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. | |||
In parallel, | 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? === | === How will you get your students involved in your community during GSoC? === | ||
| Line 93: | Line 95: | ||
*2008: Pass 5 / 1 Fail | *2008: Pass 5 / 1 Fail | ||
*2007: Pass 5 / 2 Fail | *2007: Pass 5 / 2 Fail | ||
=== If your org has applied for GSoC before but not been accepted, select the years: === | |||
*2015 | |||
=== Are you part of a foundation/umbrella organization? === | === Are you part of a foundation/umbrella organization? === | ||
| Line 99: | Line 104: | ||
=== What year was your project started? === | === What year was your project started? === | ||
2001 | 2001 | ||
=== Where does your source code live? === | |||
https://github.com/scummvm/scummvm | |||
https://github.com/residualvm/residualvm | |||
= Part 2 - Organization Profile = | = Part 2 - Organization Profile = | ||
| Line 111: | Line 120: | ||
=== Topic Tags === | === Topic Tags === | ||
games, game engines, software preservation | |||
=== Short Description of the Organization (180 char) === | === Short Description of the Organization (180 char) === | ||