1,190
edits
Difference between revisions of "Summer of Code/Application/2015"
Summer of Code/Application/2015 (view source)
Revision as of 17:17, 19 February 2015
, 17:17, 19 February 2015→Description
Strangerke (talk | contribs) |
Strangerke (talk | contribs) |
||
| (25 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: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 | 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 116: | Line 117: | ||
=== Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? === | === Why is your organization applying to participate in Google Summer of Code 2015? What do you hope to gain by participating? === | ||
Each year since 2007, the program gave us the opportunity to have talented and motivated students working with us. We also love the GSoC mentor summit where we have the opportunity to share our knowledge with mentors from other projects and to learn a lot from them. That's why we wait impatiently, each year, for the announcement of a new GSoC program! | Each year since 2007, the program gave us the opportunity to have talented and motivated students working with us. We also love the GSoC mentor summit where we have the opportunity to share our knowledge with mentors from other projects and to learn a lot from them. That's why we wait impatiently, each year, for the announcement of a new GSoC program! | ||
| Line 133: | Line 123: | ||
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 hope these students will add their piece of code to this project, but will also keep on contributing afterwards. | 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 hope these students will add their piece of code to this project, but will also keep on contributing afterwards. | ||
We've been successful in the past | We've been successful in the past eight years, and we're really looking forward to great results from the program this year too. | ||
=== 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 ==== | ||
# aquadran | |||
# clone2727 | |||
# djwillis | # djwillis | ||
# dreammaster | # dreammaster | ||
# lordhoto | # joostp | ||
# klusark (joelteichroeb) | |||
# lordhoto</span> | |||
# md5 | # md5 | ||
# sev | # sev | ||
| Line 146: | Line 140: | ||
==== Backup Mentors ==== | ==== Backup Mentors ==== | ||
# botje (dharnie) | |||
# <span style="color:red">fuzzie</span> | |||
# wjp | # wjp | ||
==== Description ==== | ==== Description ==== | ||
We have | 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: | ||
# Be able to commit to participating for the entire duration of the program. They first and foremost have to be available to their students and the mentor team. | # Be able to commit to participating for the entire duration of the program. They first and foremost 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 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 on how to tackle their tasks. Also, to be able to help the students out in sticky situations. | # Have the patience and skills to explain to their respective students on how to tackle their tasks. Also, to be able to help the students out 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. Allowing, of course, some freedom of movement to the students, where this is applicable. | # Have a clear vision on how a task should proceed, both in broad strokes as well as in the technical details level. Allowing, of course, some freedom of movement to the students, where this is applicable. | ||
# | #Be regularly present on our #scummvm-gsoc channel, where we continuously inform each others of the progresses and issues of the students | ||
For this year, and this holds for our previous participations too, our mentors have volunteered to work with GSoC. This means that they primarily want to be involved in the program and that they are not dragged in to participate. Moreover, they have all been contributors to ScummVM for several years. They feel comfortable around the | For this year, and this holds for our previous participations too, our mentors have volunteered to work with GSoC. This means that they primarily want to be involved in the program and that they are not dragged in to participate. Moreover, they have all been contributors to ScummVM and/or ResidualVM for several years. They feel comfortable around the current code and can guide students to perform their tasks. The majority of the mentors have also participated in past GSoCs so they know their way around the procedures and have also refined their mentoring style. Some of them have been GSoC students one of the previous years. Some of them are/have been part of academia, guiding real students. They have seen the student mentalité in-action and have experience helping people along. We are drawing the best available from our pool of developers to mentor GSoC students this year again. | ||
=== | === What is your plan for dealing with disappearing students? === | ||
We know that the students can do that. We learned this the hard way the first time 'round the GSoC ride :-) The measures we set in place during the previous years almost eradicated this problem. | We know that the students can do that. We learned this the hard way the first time 'round the GSoC ride :-) The measures we set in place during the previous years almost eradicated this problem. | ||
| Line 171: | Line 165: | ||
Of course, comprehensive timelines will be required as usual, and we will accept only those of the students which will set realistic goals, thus minimizing the risk of getting intimidated. This factor too frequently leads to the student disappearing. | Of course, comprehensive timelines will be required as usual, and we will accept only those of the students which will set realistic goals, thus minimizing the risk of getting intimidated. This factor too frequently leads to the student disappearing. | ||
During the program, we will make sure that the students will feel comfortable with their tasks. Our mentors already have experience with that. Moreover, in difficult situations in the past there was not just a single person feeling responsible for a particular student, but rather the whole project was trying to help when needed. These reflexes on behalf of the mentor group but also on behalf of the active team members of ScummVM have proven to be a pretty good "tool" and we are going to do our best this year too. | During the program, we will make sure that the students will feel comfortable with their tasks. Our mentors already have experience with that. Moreover, in difficult situations in the past there was not just a single person feeling responsible for a particular student, but rather the whole project was trying to help when needed. These reflexes on behalf of the mentor group but also on behalf of the active team members of ScummVM and ResidualVM have proven to be a pretty good "tool" and we are going to do our best this year too. | ||
Based on our more negative experience | Based on our more negative experience several years ago, we will also make sure that internal project tensions stay internal and under control, since they were an identified cause of demotivation of our last disappearing student (in 2011). The current umbrella management structures should make sure that it will not as easily happen in the future. | ||
=== | === 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, | 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 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 | ;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? === | ||
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 193: | 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 | === What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes? === | ||
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 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 | |||