SummerOfCode2009Template [FreeBSD WIKI]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Summer of Code 2009 Application Template ======

===== 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:

IM/IRC:

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.  You should be ready to produce a day by day schedule before the program starts.):

Bio. Who are you?  What skills do you bring to this project?  What is your past involvement with The %%FreeBSD%% Project?  (Past involvement is not required, but ideally you will have at least installed %%FreeBSD%% and perhaps fixed a bug or two)  What do you think you will need to learn to complete this project?:

Possible Mentor (Optional, but highly recommended.  Do not put a name here if you have not contacted them.):

===== Project Information =====

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 The %%FreeBSD%% Project.):

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):