gsoc:planning_2009

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
gsoc:planning_2009 [2008/09/04 22:51] – Some links and minor other stuff to others johannesgsoc:planning_2009 [2009/03/23 16:18] – added "advice for mentors" document link. gloob
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 list so all know what's going on   - Weekly Reports to the GSoC list so all know what's 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     - One org (don't remember which) has a nice approach sending weekly reports to the mentor only till midterm, project-wide after midterms
Line 13: Line 14:
   - Python has a nice page explaining "What we expect", a good read, http://wiki.python.org/moin/SummerOfCode/Expectations   - 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   - 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
  
 ====== Weekly report template ====== ====== Weekly report template ======
gsoc/planning_2009.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1