GSOC Questions

Why is your organization applying to participate in Google Summer of Code 2014? What do you hope to gain by participating?

The RIOT community applies to GSOC 2014 in order to get in touch with the best students from different countries, whom might not be reachable otherwise. Our approach is inclusive in the sense that we want such students to become real members of the community, with ongoing contributions on github etc. There are a number of projects for which we need additional help, and we think that some talented students could help us achieve significant goals. Most of the projects we propose are in fact the first phases of longer terms projects that the students may choose to contribute to after GSOC is over.

How many potential mentors do you have for this year's program? What criteria did you use to select them?*

We selected our potential mentors from the core developers and contributors to RIOT. Mentors were selected based on (i) how well they know the code area they're volunteering to mentor, and (ii) how they interact with others in the community, and (iii) how much time available they have to adequately mentor their student(s).

The potential mentors :

• Kaspar Schleiser, who developed the micro-kernel on which is based RIOT.
• Ludwig Ortmann, who developed most of the the virtualization of RIOT on Linux, the native port.
• Hauke Petersen, who developed the driver model for RIOT.
• Martine Lenders, who developed most of the 6LoWPAN network stack and POSIX APIs.
• Emmanuel Baccelli, who is an expert in IPv6 protocols stack, and an author of several RFCs.
• Matthias Wählisch, who is an expert in IPv6 protocols stack, and an author of several RFCs.

All the potential mentors have extensive experience dealing with students as they all mentored (or are still mentoring) a number of students in various software projects in the recent years. All potential mentors listed above have extensive experience in embedded design programming and/or network stack design and programming.

What is your plan for dealing with disappearing students?*

All the potential mentors have extensive experience dealing with students as they all mentored (or are still mentoring) a number of students in various software projects in the recent years. The goal of the project is to be as inclusive as possible from day one: we want our students to become real members of the community, with ongoing contributions on github etc. In our experience, such an inclusive approach encourages students to hang on. In order to further decrease the risk of student drop out, we will put in place a rhythm where bi-weekly update/meetings are expected between mentors and students to continuously discuss progress and next steps. We'll also ask our students to provide means for us to get in touch beyond email, where possible - Skype, IM, phone, etc - in case we need to get in touch urgently.

What is your plan for dealing with disappearing mentors?*`

We provide a "backup mentor" for each project that briefly monitors the mentoring process and can jump in quickly if needed. The admin (Oliver Hahm) will also ensure that the mentors are indeed keeping track of what their students are up to.

What steps will you take to encourage students to interact with your project's community before and during the program?*

We use Github, and one advantage of this platform is that the current activity of the RIOT community (a relatively 'young' community) on this platform is very visible and may thus attractive for students. This attraction should lead students to start interacting with the community even before the GSOC program, and certainly during the program. We also use IRC, which should also help the inclusive process and the sense of real-time interaction that can be quite motivating. We hope we can make students feel that they're an important part of our community; be open for creative contributions and make them realize that their contributions are really making a difference towards the goals of RIOT. We will make sure they understand how important community building is for the ongoing health of this type of open source project, and they are welcome to continue to contribute to the RIOT community even after the GSOC 2014 is over.

What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes?*

Many of the projects we propose are explicitly the first phases of longer terms projects that the students may choose to contribute to after GSOC is over. This in itself should be a motivation for students to continue to contribute outside of the context of GSOC 2014. We will encourage them to consider this not just as a mere "summer job", but as first steps in an actual developer community that is ready to welcome them. We will highlight that doing something that is not only interesting for them personally but also useful for others.

Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.

The veteran organization ns3 (nsnam) vouches for RIOT.