summerofcode2009template

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
summerofcode2009template [2009/03/09 21:07] – BrooksDavissummerofcode2009template [2009/03/09 21:26] (current) – BrooksDavis
Line 4: Line 4:
 The objective of the proposal is to identify what is to be done, explain why this needs to be done, and convince us that: 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 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 needed to complete the project within the working period of the Summer of Code.+  * You have the resources (especially time!) needed to complete the project within the working period of the Summer of Code.
  
 ===== General Information ===== ===== General Information =====
Line 28: Line 28:
 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.): 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.  For projects where it would be appropriate, this schedule should include multiple committable or releasable points so people can benefit from and/or test your work as soon as possible.):+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):
  
  • summerofcode2009template.1236632877.txt.gz
  • Last modified: 2009/03/09 21:07
  • by BrooksDavis