Summer of Code/Application/2021
Introduction & overview
|Participation in prior SoCs:||Yes|
|Applications for prior SoCs:||2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007|
|Ideas page:||Ideas 2021|
|IRC channel:||#scummvm on irc.freenode.net|
|Discord Server:||Development mailing list:||http://lists.scummvm.org/listinfo/scummvm-devel|
Please address all items in RED ;-)
Part 1 - Application Form
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.
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 functionalities or game engines, proposing and finally implementing them. These have been our favorites.
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.
What would your org consider as a successful summer? (500 Characters)
We consider that having the opportunity of coaching motivated students is already a successful summer. Obviously, it's even better if they stay with us at the end of the summer.
How many potential mentors do you have for this year's program?
6 (Category 6-10 for Google) Hopefully more people will be added, to be updated
- criezy ??
- dreammaster ??
- somaen ??
- strangerke If it's possible without a working communication tool? (as IRC and email seems to be abandoned)
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 for the highest possible availability.
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.
- Have a considerable track record hacking on ScummVM. 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 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.
- Be regularly present on our #scummvm-gsoc channel, where we continuously inform each others of the progresses and issues of the students.
How will you help your students stay on schedule to complete their projects? (1000 characters)
We require students to give a detailed schedule for their project as part of their GSoC application. 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, and help us determine when the student is expected to be working according to the new timeline.
As the GSoC is no longer considered as a full time job, We'll determine with the students the days we expect a feedback in the detailed scheduled, so that the students don't disappear silently. We also ask the students to blog at least once a week about their progress, except if the student planned to take a week off.
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? (1000 characters)
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,
- 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. Google SoD helped us to improve it significantly during the past year.
- 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.
- 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? (1000 characters)
Since GSoC 2014, we have 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 is 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.
Has your org been accepted as a mentoring org in Google Summer of Code before?
Which years did your org participate in GSoC?
2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2016, 2017, 2018, 2019, 2020
How many students did your org accept for 2020
How many of your org's 2020 students have been active in your community those past 60 days
For each year your organization has participated, provide the counts of successful and total students (e.g. 2016: 3/4)
- 2020: 4/4
- 2019: 3/4
- 2018: 3/4
- 2017: 2/2
- 2016: 3/4
- 2014: 5/5
- 2013: 4/4
- 2012: 3/4
- 2011: 1/2
- 2010: 4/4
- 2009: 4/5
- 2008: 5/6
- 2007: 5/7
If your org has applied for GSoC before but not been accepted, select the years:
What year was your project started?
Where does your source code live?
Is your organization part of any government?