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.

We are looking for round 11 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 11 is September 29 to November 2. Please fill your application by November 2, and complete your kernel patch by November 2 also (7pm UTC on both dates). 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 11 projects

Round 10 projects are available here. For each project, if you click on the proposer's name, you may find more information.

ADXL377 Triple Axis Accelerometer IIO driver

Mentor:: Octavian Purdila, 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 Analog Devices ADXL377 triple axis accelerometer using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO 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.

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

Staging driver cleanup

Mentor:: Greg Kroah-Hartman

This project will dive into a few specific drivers in the staging tree, doing more than just basic code formatting cleanup. The goal will be to help change the code to make it acceptable for merging into the "real" portion of the kernel. If possible, hardware will be provided for the code being worked on.


Mentor:: Pablo Neira Ayuso

nftables provides a replacement for the very popular {ip,ip6,arp,eb}tables tools. nftables reuses most of the Netfilter components such as the existing hooks, connection tracking system, NAT, userspace queueing, logging among many other features. So we have only replaced the packet classification framework. nftables comes with a new userspace utility nft and the low-level userspace library libnftnl. The goal will be to help finish the translation layer software that converts from the iptables syntax to nftables, complete some simple missing features and fixing bugs whenever possible.

For more information on nftables, please check:

Ceph-related kernel code cleanup

Mentor:: Alex Elder

The Ceph project implements a scalable and fault-tolerant network based storage system. Portions of Ceph reside in the Linux kernel, presenting either a block device or a file system interface backed by Ceph storage accessed over the network.

This project involves doing cleanup of the Ceph-related kernel code. The work will range from very easy fixes (like typo's and coding style) to more more substantive (refactoring functions and source files). Typically this kind of work identifies bugs as well, and if so those will be fixed (or at least documented).

More information can be found here.

y2038 cleanup in drivers

Mentor: Arnd Bergmann

The concept of 'time' in Linux is encoded in many different ways, but the most common one is based on the 'time_t' type that counts the number of seconds that have passed since Jan 1, 1970. This type is currently defined as 'long', which on 32-bit systems is a signed 32-bit number that will overflow on Jan 19 2038 and likely cause existing systems to stop working, see

On 64-bit systems, the problem is solved for the most part because 'long' is a 64-bit number that will not overflow for billions of years, but there are some important missing pieces such as file systems that store time in 32-bit quantities on disk as well support for 32-bit user space binaries running on 64-bit kernels.

Solving this problem in general is a huge effort involving lots of changes in the kernel as well as in user space. This project focuses on the kernel side, can be nicely split up into many small subtasks and is a prerequisite for doing the user space changes. There are currently 2003 instances of 'time_t', 'struct timespec' and 'struct timeval' in the kernel, and we are going to replace all of them with other types.

Any isolated in-kernel uses of these types can be replaced with 'ktime_t' or 'struct timespec64'. For any interface to user space (typically an ioctl command or a system call) that passes a data structure based on these types, we have to keep the existing interface working and introduce an alternative interface that can be used by newly built user space programs.

y2038 has a deeper introduction to the topic and will be updated with more detailed subtasks over time.


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 November 2.

  • Use our tutorial to send in your first kernel patch by November 2.

  • 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 2015-09-30 22:05:01 by AlexElder