Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni)
Please see the Outreachy homepage for an introduction to the program.
Welcome Outreachy applicants! Our round 10 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 Outreachy Round 10 is February 17 to March 24. Please fill our your application by March 24, and complete your kernel patch by March 24. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our application FAQ for more info on how to fill our your application.
Join the outreachy-kernel mailing list
Read our instructions for applying, and apply by March 24.
Use our tutorial to send in your first kernel patch by March 24.
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.
Some projects may have small tasks you can complete as part of the application process. Do not start on these tasks until after you complete the first patch tutorial and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets. In order to ensure applicants aren't working on the same task, we need your help in coordinating who is working on what task. Please see the Outreachy tasks page for details before starting on a task!
Round 10 projects
More coming soon. Round 9 projects are available here. For each project, if you click on the proposer's name, you may find more information.
Mentor:: Julia Lawall
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.
The use of out of date APIs is confusing for people who need to understand the code, and requires the maintenance of excess code. The goal of this project is to use Coccinelle to replace out of date API uses in the Linux kernel with more modern equivalents.
Media Controller Virtual Driver
Mentor:: Laurent Pinchart
The media subsystem has a kernel driver that emulates a V4L device in order to allow testing userspace applications without requiring hardware. We are, however, missing a driver that would emulate a Media Controller device. Such a driver would be very useful to test handling of complex media pipelines in userspace applications.
The goal of this project is to create a virtual Media Controller driver. No access to hardware is needed to perform this task, although a USB camera compatible with the USB Video Class could be useful to first experiment with the Media Controller API.
Modernize Linux Wireless drivers
Mentor: Jes Sorensen
The Linux wireless (WiFi) stack has migrated from the old obsolete WEXT API to the modern cfg80211/nl80211 API. The old WEXT API has been marked deprecated for years, but unfortunately a couple of drivers are still using it, making it impossible to remove the old code.
Full Dynamic Ticks
CPUs have to be interrupted through periodic timers to initiate tasks such as update of CPUs'load and runtime of tasks, perform preemption of running tasks if necessary and load balancing to even out system wide load. But when CPUs are idle, none of these tasks is required to be performed as there is no load on them. So periodic timer interrupts can be stopped on idle CPUs. This improves power efficiency of the kernel to a good extent. Thus an infrastructure called "Tickless Idle" which disables periodic timer interrupts when CPUs are idle, was added to the 2.6.21 release of the Linux kernel.
However some users required that periodic timer interrupts be disabled even on CPUs running single tasks. Typically high performance workloads (HPC) and real time tasks are performance critical and require to be run undisturbed as far as possible. For the benefit of such tasks, the Full Dynamic Ticks infrastructure was added to the 3.10 release of the Linux kernel. The goal of Full Dynamic Ticks is to enable CPUs to run in tickless mode as long as they are running single tasks. As a consequence it manages to isolate such CPUs to run performance critical user tasks without interruptions from the kernel. Over the months much effort has gone into making this stable. However there is more work to be done.
IIO dummy driver
The Industrial I/O subsystem is intended to provide support for devices that in some sense are analog to digital or digital to analog converters. Some devices that fall in this category are: accelerometers, gyroscopes, light sensors, etc.
Linux staging already holds a dummy IIO driver which is very useful as documentation on how to write a driver. Also it is very useful for testing user space code and rapidly prototyping new interfaces.
The goal of this project is to move IIO dummy driver out of staging. The major challenge in order to make this ready is interrupt emulation. The way evgen module generates interrupts greatly restricts their use and is far from clean. There is also work on the device creation part. Current approach where we use a module parameter controlling how many instances are created it's pretty ugly. Last thing we need to add support for more devices, allowing userspace applications to do smoke testing without have the actual hardware.
Yeah, that sounds cool!
Join the outreachy-kernel mailing list
Read our instructions for applying, and apply by October 31.
Use our tutorial to send in your first kernel patch by October 31.
After you have sent several cleanup patches and at least one patchset, choose a small task to complete.