gsoc-student-app-template -Diff-



# 2011 Plan 9 & Google Summer of Code Student Application Template

Please use this template as a guide for information you send in any project application. Unless specifically stated otherwise, all information we request is required. Ensuring that your application is properly and fully filled saves us all time, so please be thorough and accurate!

## Personal Information

### Contact Information

### Educational Information

### Biographical information

### Code Challenge

We want to be sure you understand the basics of Plan 9 concepts and coding. Please take a look at one (or more) of the following options and submit your solution along with your application. If you need any clarification, or have any general questions on any of these topics, please feel free to get in touch either via the #plan9 or #plan9-gsoc channels on Freenode, or via the plan9-gsoc mailing list at http://groups.google.com/group/plan9-gsoc.

## Project Information

### Project Overview

Tell us about the specific project you'd like to work on. If you've picked something from our ideas page, please make the title match what's on that page. Regardless, you should be able to describe the project in your own words (even if it's just to show us you understand what an existing idea is looking for). Especially if your proposal is your own idea, be sure to include enough detail so that we understand your idea.

Do *not* copy / paste an idea from the ideas page verbatim.

### Schedule / Timeline

Part of effective engineering is being able to break a project down into component parts and evaluate those. Do so: tell us what the component parts of your project are and build a schedule for them.

We'd like you to break down your project into weekly milestones. This will allow you to get a great feel for the work required for your project, and will give everyone involved a schedule to help guide project planning along the way. It will also help us evaluate the scope and complexity of your project, as well as how well-formed your idea is.

### Availability

Summer of Code is a significant commitment. If selected, you'll be undertaking a project designed to fill the summer. Please tell us about any other commitments you have during the summer. How many hours per week are you prepared to dedicate to this? Will you be taking courses, as well? Working? Any vacation time planned? This should already be included in your proposed schedule above, but call out any vacation, late start or other such exceptional issues explicitly here.

### Mentor communication

Summer of Code is a mentoring arrangement, and communication with your mentor is key. What frequency of communication would you expect? Are you prepared to provide progress updates at least a few times a week? How are you most comfortable communicating (email, blog, IRC, so on)? While our mentors are making a commitment to give you time and attention over the summer, "stuff happens"; what would you do if your mentor disappeared for a week during the summer?

### Optional: Suggested Mentor

If you've spoken to someone in our community about this project, and they've agreed to mentor you for the summer, list them here. This is optional, but is particularly valuable if you're proposing a project not on our list. If it is on our ideas list, we can mostly figure this out.