Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2009:wrapup [2009/09/08 11:00] mdc |
soc:2009:wrapup [2010/03/23 15:50] (current) sha0 Typo correction |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | + | ====== Google Summer of Code 2009 Wrapup Report ====== | |
| - | ====== Google Summer of Code 2009 Wrapup Reort ====== | + | |
| ===== Overview ===== | ===== Overview ===== | ||
| - | In 2009 the [[http://etherboot.org/|Etherboot Project]] was privileged to participate in [[http://socghop.appspot.com/|Google Summer of Code 2009]]. | + | In 2009 the [[http://etherboot.org/|Etherboot Project]] was pleased to participate in [[http://socghop.appspot.com/|Google Summer of Code 2009]]. |
| Our main project page for Google Summer of Code 2009 is [[http://etherboot.org/wiki/soc/2009/|here]]. | Our main project page for Google Summer of Code 2009 is [[http://etherboot.org/wiki/soc/2009/|here]]. | ||
| Line 33: | Line 32: | ||
| ==== Daniel Verkamp ===== | ==== Daniel Verkamp ===== | ||
| - | Daniel sucessfully implemented an automated regression testing framework to help the project consistently deliver high-quality releases. | + | Daniel implemented an automated regression testing framework to help the project consistently deliver high-quality releases. |
| Daniel's project pages are [[.:dverkamp:|here]]. | Daniel's project pages are [[.:dverkamp:|here]]. | ||
| Line 39: | Line 38: | ||
| ==== Joshua Oreman ===== | ==== Joshua Oreman ===== | ||
| - | Joshua successfully extended gPXE, our network bootloader, with and 802.11 wireless stack, and added drivers for two wireless cards. | + | Joshua extended gPXE, our network bootloader, with and 802.11 wireless stack, and added drivers for two wireless cards. |
| Joshua's project pages are [[.:oremanj:|here]]. | Joshua's project pages are [[.:oremanj:|here]]. | ||
| - | |||
| - | ==== Chris Kluka ===== | ||
| - | |||
| - | Chris worked on adding a network driver DLink DGE-530T ethernet cards. He was unable to complete his project, but compiled and created useful information which will facilitate future work on this driver. | ||
| - | |||
| - | Chris' project pages are [[.:asdlkf:|here]]. | ||
| ==== Lynus Vaz ===== | ==== Lynus Vaz ===== | ||
| - | Lynus Vaz is extended gPXE scripting with a more powerful language that is capable of expressing advanced boot policies. | + | Lynus Vaz extended gPXE scripting with a more powerful language that is capable of expressing advanced boot policies. |
| Lynus' project pages are [[.:lynusvaz:|here]]. | Lynus' project pages are [[.:lynusvaz:|here]]. | ||
| Line 57: | Line 50: | ||
| ==== Pravin Shinde ===== | ==== Pravin Shinde ===== | ||
| - | Pravin Shinde is created a central resource to network boot operating systems, diagnostic tools, and utilities at http://boot.kernel.org/ . | + | Pravin Shinde created a central resource to network boot operating systems, diagnostic tools, and utilities at http://boot.kernel.org/ . |
| Pravin's project pages are [[.:pravin:|here]]. | Pravin's project pages are [[.:pravin:|here]]. | ||
| + | |||
| + | ==== Chris Kluka ===== | ||
| + | |||
| + | Chris worked on adding a network driver DLink DGE-530T ethernet cards. He was unable to complete his project, but compiled and created useful information which will facilitate future work on this driver. | ||
| + | |||
| + | Chris' project pages are [[.:asdlkf:|here]]. | ||
| ===== Our Mentoring System ===== | ===== Our Mentoring System ===== | ||
| Line 65: | Line 64: | ||
| As this is our fourth year of participation in GSoC, and we have developed and refined a system for mentoring that works quite well for us. | As this is our fourth year of participation in GSoC, and we have developed and refined a system for mentoring that works quite well for us. | ||
| - | One of the important attributes of our system is that if breaks the 12 week coding period into twelve one week periods. By doing this, we ensure that we always have recent information on how are students are doing, which allows us to intervene in a timely fashion should we detect problems. | + | One of the most important attributes of our GSoC system is that if breaks the 12 week coding period into twelve one week evaluation periods. By doing this, we ensure that we always have recent information on how are students are doing, which allows us to intervene in a timely fashion should we detect problems. |
| ==== How we structure our GSoC engagements ==== | ==== How we structure our GSoC engagements ==== | ||
| Line 80: | Line 78: | ||
| * We require our students to maintain a set of project pages, which in include their: | * We require our students to maintain a set of project pages, which in include their: | ||
| - | |||
| * Project Plan | * Project Plan | ||
| * Journal (broken into twelve weeks) | * Journal (broken into twelve weeks) | ||
| Line 88: | Line 85: | ||
| * Our mentors meet weekly with each student in a private IRC channel to review their project pages and generally discuss progress so far. We have found these meetings to be very beneficial to both students and mentors. | * Our mentors meet weekly with each student in a private IRC channel to review their project pages and generally discuss progress so far. We have found these meetings to be very beneficial to both students and mentors. | ||
| - | * We require out students to have IRC access and to define "work hours" where they will be online and available on our main project IRC channel (#etherboot). We have found that this encourages them to interact with our project community as well as their primary mentor. | + | * We require our students to have IRC access and to define "work hours" where they will be online and available on our main project IRC channel (#etherboot). We have found that this encourages them to interact with our project community as well as their primary mentor. |
| | | ||
| * We use all available means to communicate with our students, including IRC, Email, Phone, VOIP, and IM. Students prefer various methods of communication, and finding what works is important. | * We use all available means to communicate with our students, including IRC, Email, Phone, VOIP, and IM. Students prefer various methods of communication, and finding what works is important. | ||
| Line 95: | Line 92: | ||
| * We judge our project's progress and success on both the quality of the code and quality of the community that we create. They are both important to us, and important to the health of our project. | * We judge our project's progress and success on both the quality of the code and quality of the community that we create. They are both important to us, and important to the health of our project. | ||
| - | |||
| - | |||
| - | |||
