GSoC/2009/StudentApplicationTemplate

= Google Summer of Code 2009 Student Application Template for autonomo.us = This is in progress and should be done by end of day, Fri Mar 13, 2009.

Guidelines
The objective of the proposal is to identify what is to be done, explain why this needs to be done, and convince us that:


 * You are qualified to do this project. This means both having the necessary background and demonstrating a general understanding of the problem.
 * You have the resources (especially time!) needed to complete the project within the working period of the Summer of Code.

General Information

 * Project Title:


 * Name:


 * Email:


 * Phone:


 * IRC:


 * Jabber:

Availability
(How many hours per week will you spend working on this? How many on other things? What other obligations (work, school, vacation, weddings, etc) do you have this summer? Be as specific as possible.):

Biography
Who are you? What skills do you bring to this project?

Activism
Write a few paragraphs describing your commitment to free software, what user freedom means to you, and why you think they you be a good fit to work with the autonomo.us group.:

History
1. What if any free software projects have you worked on in the past?

2. Do you have any systems administration experience? If so, describe that experience.:

3. Describe your development experiences and what computer languages you are comfortable with.:

Learning
What do you think you will need to learn to complete this project?

Mentorship
Possible Mentor (Optional, but highly recommended. Do not put a name here if you have not contacted them. Please feel free to email our mailing list or ask in our IRC channel; djbclark is the primary coordinator):

Project Description
A few paragraphs describing your project. Direct copies from the ideas page will be rejected. Include both what you will be doing and why it is a good thing for autonomo.us:

Deliverables
A list quantifiable results and related code milestones. We suggest at least two milestones before the mid-term evaluations and two after. Where appropriate, this schedule should include multiple committable or releasable points so people can benefit from and/or test your work as early as possible.:

Test Plan
What parts of your code need testing and how do you plan to test them? This might include both functionality and performance tests.: