Redirected from page "OPWIntro"

Clear message
  • Immutable Page
  • Info
  • Attachments


Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni)

Please see the Outreachy homepage for an introduction to the program.

Round 12 is coming up soon. It's too early to send patches to the outreachy kernel mailing list, but please consider working through the other parts of the tutorial if you are intersted in applying.

We are looking for round 12 funding sponsors and Linux kernel mentors. Please see the linked FAQ pages if you want to help out.

Welcome Outreachy applicants! Our round 11 sponsors have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latino, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander 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 12 is February 9 to March 22. Please fill your application by March 22, and complete your kernel patch by March 22 also (7pm UTC in both cases). 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 out your application.

If you are interested in being a Linux kernel intern, please:

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 12 projects

Round 11 projects are available here. For each project, if you click on the proposer's name, you may find more information. The following is a partial list of projects. More will come soon.

Update legacy workqueue creation interface users

Mentor:: Tejun Heo

Workqueue is an asynchronous execution mechanism which is widely used across the kernel. A work item queued on a workqueue is asynchronously executed by a worker task (kworker/* in ps output). It's used for various purposes from simple context bouncing to hosting a persistent in-kernel service thread.

Due to its development history, there currently are two sets of interfaces to create workqueues.

  • create[_singlethread|_freezable]_workqueue()

  • alloc[_ordered]_workqueue()

The latter is the new interface which is superset of the former. While each create*_workqueue() can be directly mapped to an alloc*_workqueue() invocation, create*_workqueue() encodes much less information than alloc*_workqueue() making determining which exact flavor and attributes to use non-trivial. Each case should be examined to find out why a specific kind is used and then converted to an alloc*_workqueue() invocation which matches the requirements.

There currently are around 280 users of the legacy interface. While the number seems daunting, there are common patterns that many of them follow.

This project would involve understanding workqueue's various users to certain degree in addition to workqueue itself and can be a good opportunity to roam through and learn various parts of the kernel.


Mentor:: Julia Lawall

Coccinelle is a program matching and transformation tool that has been extensively used for finding bugs in the Linux kernel. More details about the project will be available soon. More information about Coccinelle is available here, including a tutorial.

IIO driver

Mentor:: Daniel Baluta

A driver allows applications to communicate and control hardware devices. Each development cycle, driver changes account for more than a half of the total Linux kernel code changes.

The goal of this project is to write a driver for a sensor using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO subsystem then implement raw readings from the device. After upstreaming the code we will enhance the driver with support for buffered readings, power management and interrupts. The exact device will be decided when the internship starts.

We will provide you the hardware setup necessary to test the driver.


Mentor:: Mentor names

Brief project description.

Yeah, that sounds cool!

If you are interested in being a Linux kernel intern, please:

  • Join the outreachy-kernel mailing list

  • Join the #opw IRC channel on

  • Join the #kernel-outreachy IRC channel on

  • Read our instructions for applying, and apply by March 22.

  • Use our tutorial to send in your first kernel patch by March 22.

  • After you have sent several cleanup patches and at least one patchset, choose a small task to complete.

Tell others about this page:

last edited 2016-02-01 09:47:02 by DanielBaluta