Has your group participated previously? If so, please summarize your involvement and any past successes and failures.We took part in the Google Summer of Code program during the 2007 and the 2008 summers. In 2007, we accepted four projects. The code that was generated was extremely useful to our project as well as to others. Our new fixed point WMA decoder has made Rockbox more useful for our users, was incorporated into the Open Neuros project besides Rockbox, and has attracted attention from other groups. We also hope to see it included in ffmpeg once it is mature enough to be merged into their current decoder. Our metadata buffering project led to support for album art in rockbox and paved the way for further improvements in our playback system. Finally, the USB project took some initial steps towards for a flexible software USB stack which has now been enabled in SVN for all builds - finally freeing us of having to use the original firmware's USB facilities in many devices. Unfortunately, one project - a text to speech engine - did not succeed. Over all I think GSoC2007 gave us a real boost as a open source project and we learned a lot about the process and how to act as mentors, etc. to bring with us for future years. In 2008, we were assigned 5 slots, however we accepted 4 projects (giving one back to the pool) after duplicate resolutions. The first project was dealt with localizing plugins to make Rockbox more accessible for blind users and speakers of other languages than English. Even now, there is still ongoing work on this and the student is a committer who has continued to work on this and other projects. The second project was to create an application for a user's computer that would assist theme creators in creating themes instead of simply editing a text file. The work was merged into SVN. The third was a project to create an ARM that we and likely many other projects could use in debugging/reverse engineering hardware. The student essentially disappeared after midterms and came back during final evaluations to tell us that he felt that he should not pass and to apologize for "over committing himself this summer". The last project aimed to make rockbox run as an application on devices like phones, PDAs, etc by providing a frame work for compiling rockbox as an application. The student completed some initial work towards this end, however seemed to grow disinterested in the project and instead devoted his time towards making vast improvements in Rockbox's WMA codec ultimately making it fastest transform codec on ARM. As this work was not towards the actual project, he was not passed, though he continues to be a valuable committer to Rockbox and is still quite involved in development. As a group, we were not quite thrilled with 2008's results, though we have made some adjustments to our plan for 2009 that should help with keeping a constant communication with students and setting firmer deadlines for students to follow.
If your group has not previously participated, have you applied in the past? If so, for what sort of participation?N/A http://www.rockbox.org/twiki/bin/view/Main/SummerOfCode2009 http://cool.haxx.se/mailman/listinfo/rockbox-dev http://www.rockbox.org/twiki/bin/view/Main/GSoCApplicationTemplate2009 will be formatted accordingly.
What steps will you take to encourage contributors to interact with your community before, during, and after the program?We'll inform the possible students that interaction with the Rockbox community will be considered a plus when selecting applications. We already have multiple students that have come forward and asked questions regarding their project application. During the six weeks familiarization period, mentors will suggest and encourage students to engage in further detailed design discussion about their chosen task if they have not already and will be directed to any documents or areas that they may need to read to learn about specific elements of their project, familiarize themselves with specific areas of the code, or any other such purpose. Throughout the coding period, mentors will encourage students to make their in-development code available for comment and review on a regular basis. Everything in the Rockbox project happens online, in public forums, etc so we will of course assume and insist that program participants join in and follow this set tradition in open source development By mentoring the students into this world and style of acting, we hope that they will see and understand the benefits of working this way and that they will then continue doing so even after the project's completion - perhaps even in non-open-source projects.
What will you do to ensure that your accepted contributors stick with the project after the program concludes?The best thing that really can do is to infect the students in some way with our enthusiasm and excitement we have for open source development. We have a set of mentors who act professionally and assist as well as we can to help the students see the fun in our way of open source hacking. We truly believe that once they've got their feet wet and get the hang of some of the internals, they too will see the light and will hang around even after this summer for the same reasons we do it - because it is a great way to learn, expand on one's skills, and because it is fun!
r2 - 12 Mar 2009 - 15:31:51 - AustinAppel
Copyright © by the contributing authors.