Summer Coding 2010 timeline

Raw calendars
April 2010            May 2010              June 2010 Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa             1  2  3                     1         1  2  3  4  5 4 5  6  7  8  9 10   2  3  4  5  6  7  8   6  7  8  9 10 11 12 11 12 13 14 15 16 17   9 10 11 12 13 14 15  13 14 15 16 17 18 19 18 19 20 21 22 23 24  16 17 18 19 20 21 22  20 21 22 23 24 25 26 25 26 27 28 29 30     23 24 25 26 27 28 29  27 28 29 30                               30 31

July 2010           August 2010         September 2010 Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa             1  2  3   1  2  3  4  5  6  7            1  2  3  4 4 5  6  7  8  9 10   8  9 10 11 12 13 14   5  6  7  8  9 10 11 11 12 13 14 15 16 17  15 16 17 18 19 20 21  12 13 14 15 16 17 18 18 19 20 21 22 23 24  22 23 24 25 26 27 28  19 20 21 22 23 24 25 25 26 27 28 29 30 31  29 30 31              26 27 28 29 30

by students

 * Application on wiki
 * General app questions
 * Project idea
 * Summer Coding 2010 proposal - Name of idea
 * In some cases, rename the Summer Coding 2010 ideas - Name of idea page
 * Coding test? to a designated mentor
 * Periodic progress reports via blog no fewer than 2x/week
 * Final deliverable is a report to summer-coding-discuss and on the wiki
 * And code, done the open source way - snapshot, not required to function, report should explain status, hosted somewhere

by sub-projects

 * Project application on wiki
 * Ideas list on wiki
 * Mentors list on wiki
 * General app questions on wiki

by mentors

 * "why I would like to work with this student on this project" letter to summer-coding-discuss
 * midterm evaluation to summer-coding-mentors
 * for student to summer-coding-mentors
 * for the program to summer-coding-mentors
 * end of summer evaluation to summer-coding-mentors
 * for student to summer-coding-mentors
 * for the program to summer-coding-mentors

by sponsor

 * How much budget to contribute by email to organizers(?)
 * Other resources to summer-coding-discuss

by upstreams

 * Comment on any proposals relevant to them via summer-coding-discuss
 * Agree, in principle, to work with student and mentor by sending email to summer-coding-discuss

by Campus Ambassadors

 * again, probably no obligatory deliverables, but this list should get pinged when we have dates about stuff

by organizers

 * deadlines published :) on wiki
 * reminders of all deadlines (should set up a script to fire these off automagically)

by communities-at-large

 * spread the word for important dates
 * no actual obligatory deliverables, I should think...
 * but perhaps optional "if you'd like to give feedback on projects, use this template by this date" stuff.