Differences

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

--- gsoc [2013/03/24 17:17]
mcb30
+++ gsoc [2013/03/27 21:37]
mcb30
@@ Line 104: / Line 104: @@
 {{ :clipart:books.png?160x160|Study time}}
+You will submit an application via the [[http://www.google-melange.com/gsoc/org/google/gsoc2013/ipxe|GSoC web application]].  Your application should include, at a minimum:
+  * Your name and as many contact routes as possible (e-mail address, phone number, IRC nickname, etc.)
+  * A brief outline of what you would like to implement, including some realistic goals for each week of the project.  Try to think in terms of measurable milestones.  For example, if you are implementing a new network driver, then some sensible milestones might be:
+    * Week 1: ability to read MAC address from the NIC, verified by displaying the MAC address using the ''[[:cmd:ifstat]]'' command
+    * Week 2: ability to transmit a packet, verified by using the ''[[:cmd:dhcp]]'' command, [[:howto:pcap|capturing]] the transmitted packet, and using [[http://www.wireshark.org/|Wireshark]] to observe the transmitted DHCP packet
+    * ...
+    * Week 4: ability to correctly download a 512MB test file containing pseudo-random data in 4.6s (i.e. 1Gbps line rate), verified using the ''[[:cmd:md5sum]]'' and ''[[:cmd:time]]'' commands
+    * ...
+  * Some indication that you are familiar with the iPXE codebase.  If you have already contributed code to the project, then please list some of your previous commits.
 The application process will involve an interview in which you will be asked to solve some short programming exercises in C.  These exercises have been used in previous years:
@@ Line 157: / Line 168: @@
     }
-You will have to submit an application via the [[http://www.google-melange.com/gsoc/org/google/gsoc2013/ipxe|GSoC web application]].  Your application should include, at a minimum:
+===== Commitment =====
-  * Your name and as many contact routes as possible (e-mail address, phone number, IRC nickname, etc.)
+You should expect to work full-time on your GSoC project during the summer.  There's no need to work fixed hours each day, but you should allow around 40 hours per week in order to do justice to the project.
-  * A brief outline of what you would like to implement, including some realistic goals for each week of the project.  Try to think in terms of measurable milestones.  For example, if you are implementing a new network driver, then some sensible milestones might be:
-    * Week 1: ability to read MAC address from the NIC, verified by displaying the MAC address using the ''[[:cmd:ifstat]]'' command"
+We like to maintain constant communication with our students.  You should expect to hang out in the [[http://webchat.freenode.net/?channels=#ipxe|#ipxe]] IRC channel pretty much all the time, and communicate at least once each working day.
-    * Week 2: ability to transmit a packet, verified by using the ''[[:cmd:dhcp]]'' command, [[:howto:pcap|capturing]] the transmitted packet, and using [[http://www.wireshark.org/|Wireshark]] to observe the transmitted DHCP packet
-    * ...
+From past experience, we often find that students try to complete work without asking for help.  From the background of academia, this is understandable; in your degree course it's important to be able to show that you can work unaided.  However, GSoC is not academic in nature.  We **want** you to ask for help.  If you don't need to ask questions, then it probably means that your project isn't sufficiently challenging.
-    * Week 4: ability to correctly download a 512MB test file containing pseudo-random data in 4.6s (i.e. 1Gbps line rate), verified using the ''[[:cmd:md5sum]]'' and ''[[:cmd:time]]'' commands
-    * ...
-  * Some indication that you are familiar with the iPXE codebase.  If you have already contributed code to the project, then please list some of your previous commits.
 ===== Useful links =====