This is an old revision of the document!
====== Google Summer of Code 2008 ====== **The Etherboot Project is applying to participate in Google's 2008 [[http://code.google.com/soc/|Summer of Code]] project!** {{ :bootroms.jpeg?350×190|Some boot ROMs}} We, the [[http://etherboot.org/|Etherboot Project]], create network booting code (gPXE) that allows computers to load their operating system from a network. gPXE can be stored in a number of places, including BIOS Flash, EPROMs, floppy, CD, HD, or other bootable media. The project has been around since about 1993. We have a number of areas we can use help with. Since our focus is on creating network boot code, it is important that you be comfortable with low-level programming -- that is, C and possibly some x86 assembler (though this is not essential for many projects, and you can pick it up as you go along). You should also understand that efficiencies of code size, runtime size, and execution speed are important to us. Low-level, or "bare-metal" programming requires patience and focus, but the sense of control and deep understanding of what is happening, and why, can be very exhilarating. ===== Where to find us ===== We generally hang out in the ''#etherboot'' channel on the FreeNode IRC network (irc.freenode.net). Please feel free to drop in and ask questions, discuss ideas, etc. We talk to all applicants individually as part of the selection process and, if we accept you as a Summer of Code student, we'll expect to talk to you in the IRC channel at least every couple of days. Our mentors for Summer of Code are: * Marty Connor [''mdc''] (Project Leader, Developer, Etherboot Project) * Michael Brown [''mcb30''] (Lead Developer, Etherboot Project) * H. Peter Anvin [''hpa''] (Project Leader, Lead Developer, Syslinux Project) You can reach the mentors directly via e-mail using <soc-mentors@etherboot.org>. There is also an Etherboot project mailing list ([[https://lists.sourceforge.net/lists/listinfo/etherboot-discuss]]; you must subscribe before posting). ===== Project ideas ===== This list is not exhaustive, and we welcome new suggestions. Some of these ideas are not in themselves complete projects; feel free to ask us how much work is likely to be involved, and how many ideas you might sensibly attempt as a Summer of Code project. {{ :nic.jpeg?237×222|A network card}} ==== Device drivers ==== gPXE is always in need of more device drivers. In the case of network card drivers, existing drivers and Linux kernel drivers are available as starting points. Data sheets are also generally available for most NIC variations, though such documentation is sometimes unreliable. You could: * Update some of the old Etherboot drivers to work with the new gPXE driver API. All drivers are written in C, and you will need to have hardware (network cards, server and client computers) to test driver changes. (We may be able to provide some of the required cards for development and testing.) * Add support for newer network card variants to an existing gPXE driver. * Add a device driver for a new, currently-unsupported network card to gPXE. If you are feeling more adventurous, and have access to appropriate hardware, you could: * Add a driver for a wireless network card. There is some out-of-date support for one type of 802.11b wireless card; you could expand this into a general framework for wireless networking, and add drivers for one or more modern wireless NICs. * Add a non-Ethernet driver, e.g. a driver for an Infiniband card. (gPXE does have a working Infiniband subsystem.) * Fix up the support for legacy bus types such as ISAPnP. These devices are allegedly supported, though most have not been tested for many years, and it is unlikely that the current code is in a working state. * Add support for a new bus type, e.g. PCMCIA or USB. {{:nullmodem.jpeg?200×200 |A null-modem cable}} ==== Protocols ==== gPXE already supports several common (and less common) protocols, including TFTP, FTP, HTTP, HTTPS, DNS, iSCSI and AoE. There are several more (mostly fairly esoteric) protocols that people may find useful. You could add support for: * Fibre Channel over Ethernet (FCoE) * Novell's Remote Program Load (RPL) * iSCSI extensions for RDMA (iSER) ==== Automated regression testing ==== gPXE has a relatively large feature set given the code size. Many features are rarely used, and there has been a tendency for parts of the code to suffer from bit-rot. The measures we have taken so far will ensure that we never end up with unbuildable code; we now avoid the use of #ifdef wherever possible, and have automated tests in place to identify missing or redundant symbols. However, we do not have any systematic method for functional testing. We would ideally like to be able to run a series of tests to verify different functional units (e.g. http download, Linux kernel booting, PXE booting, serial console support, etc.). Most of these tests can be carried out inside a virtual machine such as bochs or qemu. Some tests (e.g. specific device driver tests) will need to be carried out on real hardware. The tests should be fully automated, and should produce a clear pass/fail status indicator. It should be possible for a developer to simply run “make test” and, some time later, receive an overall pass/fail status, together with a list of any failed tests. Having such an automated test suite would enable us to offer quality control guarantees; we could then be confident that upgrades would not break existing functionality. ===== How to apply ===== First, take a look at the above list of project ideas and see if anything takes your fancy. If you have an idea of your own that isn't listed above, that's great. Take some time to think about your idea; how might you approach the problem, how long do you think it would take, how interesting do you find it, how useful will it be to other people, etc.? Second, introduce yourselves to us. Preferably via the IRC channel, though e-mail is perfectly acceptable. We will want to spend some time talking to you about your proposal. We will base our decision mostly on the interactions we have with you, rather than on the project proposal you submit via the GSoC web interface. Thirdly, once you've talked to us on IRC or via e-mail, submit a project proposal via the official Summer of Code web interface. ===== Hints and tips ===== * Do get in touch with us. Unlike the larger projects, we **will** take the time to talk to you personally. If we haven't spoken to you, we're very unlikely to accept you as a student. * Do ask for help when you need it. You're not in class, and you won't be penalised for not knowing the answer immediately. ===== Potentially useful links ===== ==== Google Summer of Code ==== * Main page: [[http://code.google.com/soc/]] * Student FAQ: [[http://code.google.com/soc/studentfaq.html]] * Student Application: [[http://code.google.com/soc/student_step1.html]] ==== Etherboot Project Links ==== * Project Home Page: [[http://www.etherboot.org/]] * Source Code: [[http://www.etherboot.org/wiki/download]] ==== Etherboot Mailing List Links ==== * Etherboot-Discuss Mailing List Archives: [[http://sourceforge.net/mailarchive/forum.php?forum=etherboot-discuss]] * Etherboot-Discuss Mailing List Subscription Page: [[https://lists.sourceforge.net/lists/listinfo/etherboot-discuss]] ==== Etherboot IRC Channel ==== * ''#etherboot'' on the FreeNode network (irc.freenode.net) We hope you have enjoyed reading about the [[http://www.etherboot.org/|Etherboot Project]], and we look forward to meeting you and discussing your project ideas.
