Summer Coding 2010 timeline

From FedoraProject

Jump to: navigation, search

Contents

Schedule

This schedule is ready for Summer Coding 2010. Join the discussion mailing list and/or watch this page to be updated about schedule changes.

Start dates are emphasized and deadlines are in bold emphasis for student items.

Idea.png
Deadlines are 23:59 UTC on the specified date
For example, if the deadline is 09 August, all work must be in for mentor review by 23:59 UTC on 09 August. You must adjust for your own timezone, meaning the deadline may be at a different time of the day for you locally.
  • April
    7 April - Students can begin submitting applications
  • May
    Whole month - students, mentors, and sub-projects get to know each other
    13 May - Mentors need to finish idea pages
    20 May - Students applications + proposals need to be in
    21 May - Sponsors must pledge funding by this point
    24 May - Organizers finalize how many applications will be accepted
    27 May - Mentors + admins finalize rank-ordered list
    28 May - Students informed yes/no about application
  • June
    Whole month - code, interact
    01 June - Project begins (depending on proposal)
Note.png
Proposals may have a modified schedule included.
  • July
    05 July - Midterm evaluations period begins
    05 July - Student midterm deadline for evaluation (first, soft deadline)
    08 July - Student midterm deadline for evaluation (final deadline)
    12 July - Midterm evaluations due from mentors
  • August
    09 August - Project coding completes
    16 August - Students final report, code snapshot, and evaluations due
    20 August - Mentor evaluations due for students
    23 August - Final evaluations due back to students
    25 August - Mentor, sub-project evaluations of the Summer Coding program requested
  • September
    01 September - Sponsors receive report from organizers
    06 September - Sponsors release and deliver funds (proposed date)

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      


Deliverables

by students

  • Application on wiki
  • 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.