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

Summer of Code/Application/2016 (view source)

Revision as of 18:07, 14 February 2016

553 bytes added , 18:07, 14 February 2016

no edit summary

Strangerke

Bureaucrats, Administrators

1,190

edits

@@ Line 28: / Line 28: @@
 = Please address all items in <span style="color:red">RED</span> ;-) =
 = Part 1 - Application Form =
+=== 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.
+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.
+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.
+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!
+=== How many potential mentors do you have for this year's program? ===
+==== Mentors ====
+# aquadran
+# criezy
+# djwillis
+# dreammaster
+# joostp
+# <span style="color:red">klusark (joelteichroeb)</span>
+# lordhoto
+# md5
+# sev
+# somaen
+# strangerke
+==== Backup Mentors ====
+# <span style="color:red">botje (dharnie)</span>
+# fuzzie
+# wjp
+<11-15>
+=== 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 and not only one, for the highest possible availability.
+Then, we want our mentors to have the following qualities:
+- Be 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 or ResidualVM. 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? ===
+TODO
+=== How will you get your students involved in your community during GSoC? ===
+TODO
+=== How will you keep students involved with your community after GSoC? ===
+TODO
+=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
+Yes
+=== Which years did your org participate in GSoC? ===
+=== What is your success/fail rate per year? ===
+=== Are you part of a foundation/umbrella organization? ===
+=== What year was your project started? ===
 = Part 2 - Organization Profile =
 === Very Short Description of the Organization (80 char) ===
@@ Line 132: / Line 185: @@
 Summary pass/fail: 2014: 5/0 2013: 4/0 2012: 3/1 2011: 1/1 2010: 4/0 2009: 4/1 2008: 5/1 2007: 5/2
-=== 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.
-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.
-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.
-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!
-=== How many potential mentors do you have for this year's program? ===
-==== Mentors ====
-# aquadran
-# criezy
-# djwillis
-# dreammaster
-# joostp
-# <span style="color:red">klusark (joelteichroeb)</span>
-# lordhoto
-# md5
-# sev
-# somaen
-# strangerke
-==== Backup Mentors ====
-# <span style="color:red">botje (dharnie)</span>
-# fuzzie
-# wjp
-<11-15>
-=== 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 and not only one, for the highest possible availability.
-Then, we want our mentors to have the following qualities:
-- Be 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 or ResidualVM. 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.
 === What is your plan for dealing with disappearing students? ===