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

Jump to navigation Jump to search
 
(6 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: || <span style="color:red">strangerke</span>
|Organization administrator: || strangerke
|-
|-
|Organization co-administrator: || <span style="color:red">sev</span>
|Organization co-administrator: || sev
|-
|-
|Backup administrator: || <span style="color:red">criezy or djwillis</span>
|Backup administrator: || criezy
|-
|-
|Project License: || GPLv2+
|Project License: || GPLv2+
Line 57: 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 organising their work. This also helps to make sure that the project is achievable and realistic.
<span style="color:red">Text modified to make it fit in 1000 char</span>


We also ask our students to give regular feedback to their mentors during the coding period, at least once every 2 days. We also ask them to blog at least once a week about their progress.
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 strongly encourage the students to ask questions on our IRC channel. As an empirical fact, on IRC any student will be able to get support literally 24/7, as our developers are scattered all over the globe.


With those rules in place, it's very 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.
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, the mentors regularly check on the progress of the student to make sure that the schedule remains realistic. If the student is ahead of schedule, some extra work may be discussed. At the opposite, 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.
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 94: 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 100: 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 112: Line 120:


=== Topic Tags ===
=== Topic Tags ===
Game, Engines, Software Preservation
games, game engines, software preservation


=== Short Description of the Organization (180 char) ===
=== Short Description of the Organization (180 char) ===
TrustedUser
2,147

edits

Navigation menu