gsoc:planning_2009

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
Next revision Both sides next revision
gsoc:planning_2009 [2008/08/29 15:29]
johannes add weekly reports to the ideas...
gsoc:planning_2009 [2009/05/10 17:05]
zoe
Line 1: Line 1:
-This year, 2008, showed we need at least the following for [[.|GSoC]]:+This year, 2009, showed we need at least the following for [[.|GSoC]]:
  
   - Let all together define the goals, verify the goals, in a group and revise them where needed   - Let all together define the goals, verify the goals, in a group and revise them where needed
-  - A GSoC list where students can interact with the community as not all projects fit to internals and other existing lists+  - Idea proposals should be filled out in full so that goals can be concrete before we let students pick them up. 
 +  - <del>A GSoC list where students can interact with the community as not all projects fit to internals and other existing lists</del> done. gsoc@lists.php.net && http://news.php.net/php.gsoc
   - A mentors list so mentors can exchange information without having to send mails with a longish CC line   - A mentors list so mentors can exchange information without having to send mails with a longish CC line
   - Motivate more discussion between the different projects   - Motivate more discussion between the different projects
-  - Maybe it would be a good idea to request students to fill out a questionnaire during the application time like other projects do +  - Questionnaire during the application time for anything PHP specific, not everything can be handled by the generic GSoC form. 
-  - Weekly Reports to the GSoC lsit so all know what'going on+  - Weekly Reports to the GSoC list so all know what'going on 
 +    - One org (don't remember which) has a nice approach sending weekly reports to the mentor only till midterm, project-wide after midterms
  
-----+====== Links to other orgs =====
  
-====== Weekly report template ======+  - Python has a nice page explaining "What we expect", a good read, http://wiki.python.org/moin/SummerOfCode/Expectations 
 +  - Tor has a template for applications https://www.torproject.org/gsoc#Template 
 +  - Etherboot has an overview page on the wiki and individual project pages where the student lists useful things like timezone, weekly journal entries and any project notes. http://etherboot.org/wiki/soc/2008/start 
 +  - Advice for mentors, interesting info and links http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors
  
-MySQL uses a template ismilar to the one below for the regular developers, might be a good start for us:+====== Two Weekly report template ======
  
  
-Subject: XXX'Weekly Report Starting 2008-..-..+Subject: XXX's Report for the two weeks starting: 2009-MM-DD
  
 < introduction > < introduction >
  
-LOGGED TIME: 40 hours (See breakdown below)+TIME SPENTXX hours 
  
  
 KEY GOOD VIBRATIONS KEY GOOD VIBRATIONS
-  < 2-3 good vibrations >+  < Things that you were really pleased with >
  
 KEY CONCERNS KEY CONCERNS
Line 41: Line 46:
   < list as many things as you wish, but prioritize   < list as many things as you wish, but prioritize
     by putting the most important items first >     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 
  
  
gsoc/planning_2009.txt · Last modified: 2017/09/22 13:28 (external edit)