gsoc:planning_2009
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
gsoc:planning_2009 [2008/09/04 22:51] – Some links and minor other stuff to others johannes | gsoc:planning_2009 [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
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</ | ||
- 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 | + | - Questionnaire |
- 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", | - Python has a nice page explaining "What we expect", | ||
- Tor has a template for applications https:// | - Tor has a template for applications https:// | ||
+ | - 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:// | ||
+ | - Advice for mentors, interesting info and links http:// | ||
- | ====== Weekly report template ====== | + | ====== |
- | MySQL uses a template similar to the one below for the regular developers, might be a good start for us: | ||
+ | Subject: XXX's Report for the two weeks starting: 2009-MM-DD | ||
- | Subject: XXX's Weekly Report Starting 2008-..-.. | ||
- | < introduction > | + | TIME SPENT: XX hours (approx) |
- | + | ||
- | LOGGED | + | |
KEY GOOD VIBRATIONS | KEY GOOD VIBRATIONS | ||
- | < 2-3 good vibrations | + | < things that you were really pleased with > |
KEY CONCERNS | KEY CONCERNS | ||
Line 45: | Line 45: | ||
< 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 | ||
- | Tuesday | ||
- | Wednesday | ||
- | Thursday | ||
- | Friday | ||
- | Saturday | ||
- | Sunday | ||
gsoc/planning_2009.1220568702.txt.gz · Last modified: 2017/09/22 13:28 (external edit)