1,190
edits
Difference between revisions of "Summer of Code/Application/2013"
Jump to navigation
Jump to search
Summer of Code/Application/2013 (view source)
Revision as of 07:11, 28 March 2013
, 07:11, 28 March 2013→What steps will you take to encourage students to interact with your project's community before, during and after the program?
Strangerke (talk | contribs) (→Introduction & overview: Add somaen in the mentor list) |
Strangerke (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Introduction & overview == | == Introduction & overview == | ||
| Line 29: | Line 25: | ||
|- | |- | ||
|Mentors: || | |Mentors: || | ||
* [[User:Sev|Eugene Sandulenko]], Google Account: sev.mail AT gmail.com link_id: sev | * [[User:Sev|Eugene Sandulenko]], Google Account: sev.mail AT gmail.com link_id: sev | ||
* [[User:LordHoto|Johannes Schickel]], Google Account: lordhoto AT gmail.com link_id: lordhoto | * [[User:LordHoto|Johannes Schickel]], Google Account: lordhoto AT gmail.com link_id: lordhoto | ||
* [[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 | ||
| Line 38: | Line 32: | ||
|- | |- | ||
|Backup Mentors: || | |Backup Mentors: || | ||
* [[User:DrMcCoy|Sven Hesse]], Google Account: drmccoy AT users.sourceforge.net link_id: drmccoy | |||
* [[User:Aquadran|Paweł Kołodziejski]], Google Account: aquadran AT scummvm.org link_id: aquadran | * [[User:Aquadran|Paweł Kołodziejski]], Google Account: aquadran AT scummvm.org link_id: aquadran | ||
* [[User:Fuzzie|Alyssa Milburn ]], Google Account: fuzzie AT scummvm.org link_id: fuzzie | * [[User:Fuzzie|Alyssa Milburn ]], Google Account: fuzzie AT scummvm.org link_id: fuzzie | ||
| Line 57: | Line 52: | ||
As usual, 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", but the main developers had no time to implement them. The students took these up as self-contained GSoC projects and realized them. But also, some students have come up with new functionality, proposing and finally implementing it. These have been our favorite. | As usual, 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", but the main developers had no time to implement them. The students took these up as self-contained GSoC projects and realized them. But also, some students have come up with new functionality, proposing and finally implementing it. These have been our favorite. | ||
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. Last year, a student met all those expectations and even managed to exceed them: Einar Johan Trøan Sømåen is still contributing to the project and is even volunteering to be a mentor this year! | |||
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 | |||
We've been successful in the past six years, and we're really looking forward to great results from the program this year too. | We've been successful in the past six years, and we're really looking forward to great results from the program this year too. | ||
| Line 67: | Line 60: | ||
=== If you answered “yes” to the question above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. === | === If you answered “yes” to the question above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. === | ||
We have participated in the GSoC program for | We have participated in the GSoC program for six years running, in 2007-2012. | ||
In 2012, 5 team members mentored 4 students. Each mentor was also the co-mentor of another task, so the backup mentoring was still working well. 3 students passed, and one failed at mid-term. One student is still contributing to the project and volunteered to be a mentor for GSoC 2013, which is really awesome. Based on discussion with other projects and on our experience, we are considering merging student code earlier in the GSoC process and have modified our processes accordingly for the next year. | |||
In 2012, 5 team members mentored 4 students. Each mentor was also the co-mentor of another task, so the backup mentoring was still working well. 3 students passed, and one failed at mid-term. One student is still contributing to the project and volunteered to be a mentor for GSoC 2013, which is really | |||
In 2011, 4 team members mentored 2 students. One student succeeded in objectifying the CruisE engine, which really needed it. The other student unfortunately gave up fairly quickly after starting work (although the work done was eventually merged into our main repository, after being worked on further by a team member). After stepping back to review our processes, we feel we can still consider them to be mature. Part of the problems which caused the student to quickly give up came from internal tensions, that we have since addressed by redefining the project management structure. | In 2011, 4 team members mentored 2 students. One student succeeded in objectifying the CruisE engine, which really needed it. The other student unfortunately gave up fairly quickly after starting work (although the work done was eventually merged into our main repository, after being worked on further by a team member). After stepping back to review our processes, we feel we can still consider them to be mature. Part of the problems which caused the student to quickly give up came from internal tensions, that we have since addressed by redefining the project management structure. | ||
| Line 79: | Line 70: | ||
In 2009 we had 5 students and 6 mentors. 4 of our students passed, and one failed the finals. That year the success was so big that all the students' code was merged within three months into the main development line. We were considered to be mature in our processes by that time with excellent outcome. | In 2009 we had 5 students and 6 mentors. 4 of our students passed, and one failed the finals. That year the success was so big that all the students' code was merged within three months into the main development line. We were considered to be mature in our processes by that time with excellent outcome. | ||
In 2008 we had 6 students and 7 mentors. 5 of our students were so successful that their code is included in the mainline of ScummVM | In 2008 we had 6 students and 7 mentors. 5 of our students were so successful that their code is included in the mainline of ScummVM, and we consider it a great achievement the fact that 4 of the students continued to contribute to the project. | ||
In 2007 we had 7 students and 4 mentors in total. Two of our students continued to become active, regular developers in the team after having their respective code contributions integrated in the codebase. All but two of the other students succeeded in their projects. | |||
All in all, we maintain that we are refining our method of student selection the past years and this refinement leads to better results each year. The discussions, testimonials and proposed actions which the mentor summit has brought up -and which we have participated in these six years- have helped us a great deal, during this refinement process as well. Our new management organization has also proven its efficiency during these last 2 years, and we expect much of it in the future. | |||
Summary pass/fail: | |||
2012: 3/1 | |||
2011: 1/1 | |||
2010: 4/0 | |||
2009: 4/1 | |||
2008: 5/1 | |||
2007: 5/2 | |||
=== If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? === | === If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? === | ||
| Line 128: | Line 126: | ||
=== What is your plan for dealing with disappearing mentors? Please be as specific as possible. === | === What is your plan for dealing with disappearing mentors? Please be as specific as possible. === | ||
For the mentors, the risk is relatively low; our past experiences absolutely verify this claim. In order to be even more efficient this year, three of our mentors are project leaders, core team members or project administrators and are reachable virtually 24/7 (in case of emergencies). | For the mentors, the risk is relatively low; our past experiences absolutely verify this claim. In order to be even more efficient this year, three of our mentors are project leaders, core team members or project administrators and are reachable virtually 24/7 (in case of emergencies). | ||
| Line 134: | Line 131: | ||
;We also defined for the last two 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. | ;We also defined for the last two 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. | ||
=== What steps will you take to encourage students to interact with your project's community before | === 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 forums, IRC, Wiki and the development mailing list during the entire project development. We consider out students to be special, but developers nonetheless. Each developer including our students is encouraged to take part in discussions, whatever the means these discussions occur. As a pragmatic fact, on IRC any student will be able to get support literally 24/7, as our developers are scattered all over the globe. | |||
;Not only the mentors, but also the entire development team, are encouraged to communicate with the students. The students are marked with a special flag on our IRC channel, so everyone knows who they are. And we require the students to write introductory letters to our development list, so everyone will have an impression about them, their skills and their assigned task (of course). | |||
;In order to help the students familiarize themselves with the project, we also have created several pieces of documentation for them. In particular, we have an exhaustive developer central where we describe the all-important internals of ScummVM. This is 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? === | |||
This year | This year we also decided to require the GSoC student code be merged into our Master tree much earlier in the process, if possible. Based on our own experience, on discussion with returning students and on discussions with other projects, 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. We'll obviously have to make an assessment afterwards of the benefits and disadvantages of that new process. | ||
=== 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 a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. === | ||