gsoc:planning_2009

This is an old revision of the document!


This year, 2008, showed we need at least the following for GSoC:

  1. Let all together define the goals, verify the goals, in a group and revise them where needed
  2. A GSoC list where students can interact with the community as not all projects fit to internals and other existing lists
  3. A mentors list so mentors can exchange information without having to send mails with a longish CC line
  4. Motivate more discussion between the different projects
  5. Maybe it would be a good idea to request students to fill out a questionnaire during the application time like other projects do
  6. Weekly Reports to the GSoC lsit so all know what'S going on

Weekly report template

MySQL uses a template ismilar to the one below for the regular developers, might be a good start for us:

Subject: XXX's Weekly Report Starting 2008-..-..

< introduction >

LOGGED TIME: 40 hours (See breakdown below)

KEY GOOD VIBRATIONS

< 2-3 good vibrations >

KEY CONCERNS

< anything that is outside of your control and which 
  concern you >

WAITING FOR...

< if you are waiting for someone else in order to complete
  one or more tasks >

KEY TASKS THAT STALLED

< if something stalled that is not outside your control
  in and by itself, even if it was outside factors that 
  delayed it >

KEY ACCOMPLISHMENTS

< list as many things as you wish, but prioritize
  by putting the most important items first >
(Sprint tasks, Bug items, ...)

LOGGED TIME

Day         Hours
----------  -----
Monday         8
Tuesday        8
Wednesday      8
Thursday       8
Friday         8
Saturday       0
Sunday         0

DETAILED ACTIVITIES

< This section is optional -- list here all minor tasks that
  did not fit into any of the categories above. >

MY TODO

< The major tasks you will be doing in the next couple 
  of weeks >
gsoc/planning_2009.1220023746.txt.gz · Last modified: 2017/09/22 13:28 (external edit)