|
Size: 2641
Comment:
|
Size: 6354
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Outreach Program for Women (OPW) Intro = | = FOSS Outreach Program for Women (OPW) and Project Ascend Alumni = Please see the [https://wiki.gnome.org/OutreachProgramForWomen FOSS Outreach Program for Women homepage] for an introduction to the program. |
| Line 3: | Line 4: |
| The Linux Foundation is sponsoring internships for women to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. The kernel encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more. | We are looking for round 9 [:OPWSponsor:funding sponsors] and Linux kernel [:OPWMentor:mentors]. Please see the linked FAQ pages if you want to help out. |
| Line 5: | Line 6: |
| == Participating kernel projects == | Welcome OPW applicants! Our [:OPWSponsor:round 9 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and alumni from the Ascend Project to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more. |
| Line 7: | Line 8: |
| Currently, we have two participating projects. | = How to apply = The application period for OPW Round 8 is September 8 to October 31. Most OPW organizations have an application deadline of October 22, however, the Linux kernel application period will be put on temporary hold from October 10 to October 20. Most kernel mentors will be attending conferences (LinuxCon Europe, Linux Plumbers Conf, and Embedded Linux Conference Europe) during that time. During the hold period, no new kernel application patches will be accepted or reviewed, and mentors may not be available on the IRC channel. Therefore, it is important to start sending patches early in the application period. We suggest that you tackle a medium-sized advanced project during that week, rather than preparing to send many small clean up patches after the hold period is finished. |
| Line 9: | Line 11: |
| === USB === | Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application] by October 22nd, and complete your initial kernel patch by October 31. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OPWApply:application FAQ] for more info on how to fill our your initial application. Applicants will be notified on November 12 if they have been accepted. |
| Line 11: | Line 13: |
| The Linux kernel includes a USB stack that communicates with the hardware behind your USB ports (USB host controller drivers), and includes USB device drivers that talk to your USB devices (USB device drivers). Working on USB is fun because you get to make all sorts of interesting USB devices work. | If you are interested in being a Linux kernel intern, please: |
| Line 13: | Line 15: |
| Sarah Sharp is sponsoring an intern to work on the USB 3.0 host controller driver. The Linux kernel USB 3.0 driver was introduced in 2009, and works 10 times faster than USB 2.0 devices. The USB 3.0 driver still needs a lot of work, so there are plenty of small bug fixes that interns can tackle. If time permits, interns could also work on small to medium features. | * Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by October 31. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31. |
| Line 15: | Line 21: |
| FIXME: add links to kernel.bugzilla.org entries for these tasks. | = Participating Linux kernel projects = Applicants for all projects should have basic experience with C or C++ and boolean algebra. Optionally, we would love it if you have basic operating system knowledge, know your way around a Linux/UNIX command line, and/or know the revision system called git. ''Please note that these three skills can be learned during the internship.'' |
| Line 17: | Line 24: |
| Necessary skills: Experience in C or C++ Optional but learnable skills: Knowledge of operating systems, USB |
Round 9 projects: |
| Line 20: | Line 26: |
| Suggested reading for accepted interns: * [http://lwn.net/Kernel/LDD3/ Linux Device Drivers] * [http://www.beyondlogic.org/usbnutshell/usb1.shtml USB in a Nutshell] |
== Kernel tinification == |
| Line 24: | Line 28: |
| == Ethernet == | ''Mentor:'': Josh Triplett |
| Line 26: | Line 30: |
| Carolyn Wyborny and Anjali Jain are sponsoring a project to work on 1 gig ethernet. (More info coming soon.) | Over time, the Linux kernel has grown far more featureful, but it has also grown significantly larger, even with all the optional features turned off. I'd like to reverse that trend, making the kernel much smaller, to enable ridiculously small embedded applications and other fun uses. In this project, you'll start from "make allnoconfig", and then try to shrink the kernel even further. You'll learn how to work with the kernel configuration system, Kconfig, and use scripts/bloat-o-meter to measure the size impact of a change. This is a highly incremental project: each feature you make optional or kernel component you shrink will mostly stand alone, and you can develop and submit each change independently. Some of these tinification goals will work well during the application period; others will require a substantial time investment, and will primarily make sense during the full internship. Before working on any of these, especially during the application period, you should send a quick note to the OPW kernel mailing list to coordinate, and avoid duplicated effort. Please see https://tiny.wiki.kernel.org/ for more details on this effort. See https://tiny.wiki.kernel.org/projects for a list of possible projects. The projects listed as "small" can potentially be done during the application period, or by an intern accepted to work on this project. The projects listed as "large" should wait until the internship. (Note to mentors and prospective applicants: Josh plans to present the tinification effort and list of projects at Linux Kernel Summit, and may add, remove, or edit items on this list based on feedback obtained there.) == Coccinelle == [http://coccinelle.lip6.fr Coccinelle] is a program matching and transformation tool for C code that has been used extensively in contributing to the Linux kernel, for both code evolutions and bug fixes. Coccinelle is driven by specifications, known as semantic patches, that use a notation based on C code, and are this fairly easy to develop. Around 40 semantic patches are included with the Linux kernel source code, in scripts/coccinelle, and are used in the continuous testing service provided by Intel. Recently, we have used Coccinelle in an extensive study of [http://hal.archives-ouvertes.fr/docs/01/02/27/04/PDF/faults-in-linux-2.6-tocs.pdf faults in Linux 2.6]. The goal of this project is to extend the results to more recent versions of Linux, and to facilitate the extension of the work to subsequent versions. This will entail: 1. Running the Coccinelle scripts that have been developed to collect data. 1. Evaluating the resulting reports to identify real bugs and false positives. 1. Submitting patches to the Linux kernel to fix the identified real bugs that are still present in the kernel. 1. Updating a database with the results. 1. Creating graphs to summarize the results. ''Mentor:'' [http://kernelnewbies.org/JuliaLawall Julia Lawall] |
| Line 29: | Line 59: |
| = Getting Started = | = Yeah, that sounds cool! = If you are interested in being a Linux kernel intern, please: |
| Line 31: | Line 62: |
| TODO: * Intro, what the goals are, why they should be excited about developing for the kernel. :) * What skills are good to have (e.g. having taken an OS class is good), or how they can get those skills later on, like by reading Linux Device Drivers * Outline of what this tutorial covers * If you run into any issues, ask on the opw irc channel, or email sarah.a.sharp at linux.intel.com * Step 0: install Linux on a home computer (alternative instructions for installing in a VM would be good, but I have no background in that). * Build a custom kernel * Find out which drivers you have installed (maybe plug in any USB devices on hand) * Make small change in one of the drivers (e.g. run checkpatch over them, or fix some grammer in the printks) * Or maybe pick a driver in staging and run checkpatch on it * Test your patch (may need to enable debugging) * Make a patch (link to art of patch description creation) * Send patch to kernel newbies mailing list as RFC (perhaps we need a separate mailing list?) |
* Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by October 22. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31. |
FOSS Outreach Program for Women (OPW) and Project Ascend Alumni
Please see the [https://wiki.gnome.org/OutreachProgramForWomen FOSS Outreach Program for Women homepage] for an introduction to the program.
We are looking for round 9 [:OPWSponsor:funding sponsors] and Linux kernel [:OPWMentor:mentors]. Please see the linked FAQ pages if you want to help out.
Welcome OPW applicants! Our [:OPWSponsor:round 9 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and alumni from the Ascend Project to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more.
How to apply
The application period for OPW Round 8 is September 8 to October 31. Most OPW organizations have an application deadline of October 22, however, the Linux kernel application period will be put on temporary hold from October 10 to October 20. Most kernel mentors will be attending conferences (LinuxCon Europe, Linux Plumbers Conf, and Embedded Linux Conference Europe) during that time. During the hold period, no new kernel application patches will be accepted or reviewed, and mentors may not be available on the IRC channel. Therefore, it is important to start sending patches early in the application period. We suggest that you tackle a medium-sized advanced project during that week, rather than preparing to send many small clean up patches after the hold period is finished.
Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application] by October 22nd, and complete your initial kernel patch by October 31. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OPWApply:application FAQ] for more info on how to fill our your initial application. Applicants will be notified on November 12 if they have been accepted.
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list]
- Join the #opw IRC channel on irc.gnome.org
- Join the #kernel-opw IRC channel on irc.oftc.net
Read our [:OPWApply:instructions for applying], and apply by October 31.
Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31.
Participating Linux kernel projects
Applicants for all projects should have basic experience with C or C++ and boolean algebra. Optionally, we would love it if you have basic operating system knowledge, know your way around a Linux/UNIX command line, and/or know the revision system called git. Please note that these three skills can be learned during the internship.
Round 9 projects:
Kernel tinification
Mentor:: Josh Triplett
Over time, the Linux kernel has grown far more featureful, but it has also grown significantly larger, even with all the optional features turned off. I'd like to reverse that trend, making the kernel much smaller, to enable ridiculously small embedded applications and other fun uses.
In this project, you'll start from "make allnoconfig", and then try to shrink the kernel even further. You'll learn how to work with the kernel configuration system, Kconfig, and use scripts/bloat-o-meter to measure the size impact of a change.
This is a highly incremental project: each feature you make optional or kernel component you shrink will mostly stand alone, and you can develop and submit each change independently.
Some of these tinification goals will work well during the application period; others will require a substantial time investment, and will primarily make sense during the full internship.
Before working on any of these, especially during the application period, you should send a quick note to the OPW kernel mailing list to coordinate, and avoid duplicated effort.
Please see https://tiny.wiki.kernel.org/ for more details on this effort. See https://tiny.wiki.kernel.org/projects for a list of possible projects. The projects listed as "small" can potentially be done during the application period, or by an intern accepted to work on this project. The projects listed as "large" should wait until the internship.
(Note to mentors and prospective applicants: Josh plans to present the tinification effort and list of projects at Linux Kernel Summit, and may add, remove, or edit items on this list based on feedback obtained there.)
Coccinelle
[http://coccinelle.lip6.fr Coccinelle] is a program matching and transformation tool for C code that has been used extensively in contributing to the Linux kernel, for both code evolutions and bug fixes. Coccinelle is driven by specifications, known as semantic patches, that use a notation based on C code, and are this fairly easy to develop. Around 40 semantic patches are included with the Linux kernel source code, in scripts/coccinelle, and are used in the continuous testing service provided by Intel.
Recently, we have used Coccinelle in an extensive study of [http://hal.archives-ouvertes.fr/docs/01/02/27/04/PDF/faults-in-linux-2.6-tocs.pdf faults in Linux 2.6]. The goal of this project is to extend the results to more recent versions of Linux, and to facilitate the extension of the work to subsequent versions. This will entail:
1. Running the Coccinelle scripts that have been developed to collect data. 1. Evaluating the resulting reports to identify real bugs and false positives. 1. Submitting patches to the Linux kernel to fix the identified real bugs that are still present in the kernel. 1. Updating a database with the results. 1. Creating graphs to summarize the results.
Mentor: [http://kernelnewbies.org/JuliaLawall Julia Lawall]
Yeah, that sounds cool!
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list]
- Join the #opw IRC channel on irc.gnome.org
- Join the #kernel-opw IRC channel on irc.oftc.net
Read our [:OPWApply:instructions for applying], and apply by October 22.
Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31.