Open main menu

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

 
(16 intermediate revisions by the same user not shown)
Line 26: Line 26:
|Mentors: ||
|Mentors: ||
* [[User:Strangerke|Arnaud Boutonné]], Google Account: arnaud.boutonne AT gmail.com link_id: strangerke
* [[User:Strangerke|Arnaud Boutonné]], Google Account: arnaud.boutonne AT gmail.com link_id: strangerke
* [[User:klusark|Joel Teichroeb]]
* [[USer:djwillis|John Willis]], Google Account: djwillis AT scummvm.org, link_id: djwillis
* [[User:klusark|Joel Teichroeb]], Google Account: joelteichroeb AT gmail.com link_id: joelteichroeb
* [[User:Somaen | Einar Johan Trøan Sømåen]], Google Account: somaen AT scummvm.org link_id: somaen
* <span style="color:red">[[User:Sev|Eugene Sandulenko]], Google Account: sev.mail AT gmail.com link_id: sev</span>
* <span style="color:red">[[User:Sev|Eugene Sandulenko]], Google Account: sev.mail AT gmail.com link_id: sev</span>
* <span style="color:red">[[User:LordHoto|Johannes Schickel]], Google Account: lordhoto AT gmail.com link_id: lordhoto</span>
* <span style="color:red">[[User:LordHoto|Johannes Schickel]], Google Account: lordhoto AT gmail.com link_id: lordhoto</span>
* <span style="color:red">[[User:Digitall|David Turner]], Google Account: digitall AT scummvm.org link_id: digitall</span>
* <span style="color:red">[[User:Digitall|David Turner]], Google Account: digitall AT scummvm.org link_id: digitall</span>
* <span style="color:red">[[User:Somaen | Einar Johan Trøan Sømåen]], Google Account: somaen AT scummvm.org link_id: somaen</span>
* <span style="color:red">[[User:Md5|Filippos Karapetis]], Google Account: md5 AT scummvm.org link_id: md5</span>
* <span style="color:red">[[User:Md5|Filippos Karapetis]], Google Account: md5 AT scummvm.org link_id: md5</span>
* <span style="color:red">[[User:Dreammaster|Paul Gilbert]], Google Account: paulfgilbert AT gmail.com link_id: dreammaster</span>
* <span style="color:red">[[User:Dreammaster|Paul Gilbert]], Google Account: paulfgilbert AT gmail.com link_id: dreammaster</span>
Line 87: Line 88:
2012: 4 students mentored by 5 team members. Each mentor was also the co-mentor of another task.
2012: 4 students mentored by 5 team members. Each mentor was also the co-mentor of another task.


3 students passed, and one failed at mid-term. One student is still actively contributing to the project and volunteered to be a mentor for GSoC 2013 and GSoC 2014, which is really awesome. Based on discussion with other projects and our experience one of the key outcomes from this year was to look at merging student code earlier in the GSoC process and encouraging students to be much closer to mainline development. We modified our processes accordingly for the next year.
3 students passed, and one failed at mid-term. One student is still actively contributing to the project and volunteered each year to be a mentor since GSoC 2013, which is really awesome. Based on discussion with other projects and our experience one of the key outcomes from this year was to look at merging student code earlier in the GSoC process and encouraging students to be much closer to mainline development. We modified our processes accordingly for the next year.


2011: 2 students mentored by 4 team members. Each mentor was also the co-mentor of another task.
2011: 2 students mentored by 4 team members. Each mentor was also the co-mentor of another task.
Line 126: Line 127:
=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===
=== How many potential mentors do you have for this year's program? What criteria did you use to select them? ===
==== Mentors ====
==== Mentors ====
[[User:Sev|Eugene Sandulenko]], Google Account: sev.mail AT gmail.com link_id: sev</span>
# aquadran
# <span style="color:red">djwillis</span>
# clone2727
# <span style="color:red">dreammaster</span>
# djwillis
# klusark
# dreammaster
# <span style="color:red">lordhoto</span>
# joostp
# <span style="color:red">md5</span>
# klusark (joelteichroeb)
# <span style="color:red">sev</span>
# lordhoto</span>
# <span style="color:red">somaen</span>
# md5
# sev
# somaen
# strangerke
# strangerke


==== Backup Mentors ====
==== Backup Mentors ====
# <span style="color:red">wjp</span>
# botje (dharnie)
# <span style="color:red">fuzzie</span>
# <span style="color:red">fuzzie</span>
# <span style="color:red">aquadran</span>
# wjp


==== Description ====
==== Description ====
<span style="color:red">We have 10 potential (co) mentors or backup mentors this year.</span>
We have 14 potential (co) mentors or backup mentors this year.


We want our mentors to have the following qualities:
We want our mentors to have the following qualities:
Line 167: Line 170:


=== What is your plan for dealing with disappearing mentors? ===
=== What is your plan for dealing with disappearing mentors? ===
For the mentors, the risk is relatively low; our past experiences absolutely verify this claim. In order to be even more efficient this year, <span style="color:red">five</span> of our mentors are project leaders, core team members or project administrators for ScummVM and/or ResidualVM and are reachable virtually 24/7 (in case of emergencies).
;We all have exchanged sufficient contact information (including cell phone numbers etc.) to be able to discover our whereabouts. Should something really bad happen which precludes a mentor from fulfilling his duties (including personal reasons), we will attempt to shift students to new mentors among the existing mentors, or drawn from our backup pool of mentors. This will depend on the number of students we have to mentor.
;We also defined for the last four years a co-mentoring system so the students have a primary and a secondary mentor, which comfort us in the idea that, in any case, the students will not be left hanging for any reason at all, no matter what happens.
;On top of that, we have a specific #scummvm-gsoc channel on IRC where mentors (and only them) and org admins are connected all of the time. We use this channel to keep ourselves informed constantly of the situation of each task, each student and eventually each mentor. A mentor wouldn't disappear without being noticed very quickly by this mean too.
=== What steps will you take to encourage students to interact with your project's community before and during the program? ===
=== What steps will you take to encourage students to interact with your project's community before and during the program? ===
=== What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? ===
=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here ===
=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here ===
=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===
== Answers and Questions from the previous year ==
===  What steps will you take to encourage students to interact with your project's community before and during the program? ===
The development team actively uses the project resources, including forums, IRC, Wiki and the development mailing list during project development.  
The development team actively uses the project resources, including forums, IRC, Wiki and the development mailing list during project development.  


Line 183: Line 187:
;In order to help the students familiarize themselves with the project, we also have created several key pieces of documentation for them. In particular, we have an exhaustive 'developer central' on our Wiki where we describe the all-important internals of ScummVM and finding your way around the project. This is highly valuable as a quick reference as well as during the initial explorations of the codebase.
;In order to help the students familiarize themselves with the project, we also have created several key pieces of documentation for them. In particular, we have an exhaustive 'developer central' on our Wiki where we describe the all-important internals of ScummVM and finding your way around the project. This is highly valuable as a quick reference as well as during the initial explorations of the codebase.


=== What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? ===
=== What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? ===
<span style="color:red">Last year we decided to require the GSoC student code be merged into our Master tree much earlier in the process, if possible. Our past experience was telling it should be very motivating for students to directly interact with our main repository and could potentially make some of them stay after the end of GSoC: it seems we were right as 2 students out of 4 are still actively contributing, while a 3rd one is still present from times to times. This is obviously for us a very positive sign and we plan to proceed the same way this year again.</span>
The two previous years, we decided to require the GSoC student code be merged into our Master tree much earlier in the process, if possible. <span style="color:red">Our past experience was telling it should be very motivating for students to directly interact with our main repository and could potentially make some of them stay after the end of GSoC: it seems we were right as 2 students out of 4 are still actively contributing, while a 3rd one is still present from times to times. This is obviously for us a very positive sign and we plan to proceed the same way this year again.</span>
 
=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.===
<span style="color:red">We'd like to vouch for ResidualVM.</span>
<span style="color:red">This project is a sister project of ScummVM, dealing with 3D Adventure games. We share a lot of common code and developers (and even mentors). </span>


=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here ===
=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here ===
=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===
=== Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ===
We are very grateful for all the benefits we reaped over the previous years thanks to your program and we would like to thank you again