|
Size: 7971
Comment:
|
Size: 8023
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| We are looking for round 11 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out. | The application period for '''Round 14''' will start on February 16, 2016. 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 interested in applying. |
| Line 7: | Line 7: |
| Welcome Outreachy applicants! Our [:OutreachySponsor: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. | We are looking for round 14 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out. Welcome Outreachy applicants! Our [:OutreachySponsor:round 14 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. '''News''' This year, we ask that you send all patches to the appropriate staging driver maintainers, as well as to the outreachy mailing list. See [:FirstKernelPatch#submit+a+patch:Submit a patch] for more information. '''For IIO patches, be sure to send them to linux-iio@vger.kernel.org''' |
| Line 10: | Line 14: |
| The application period for Outreachy Round 11 is September 29 to November 2. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process 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 [:OutreachyApply:application FAQ] for more info on how to fill out your application. | The application period for Outreachy Round 14 is February 16 to March 30. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by '''March 30''', and complete your kernel patch by '''March 30''' 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 [:OutreachyApply:application FAQ] for more info on how to fill out your application. |
| Line 15: | Line 19: |
| * Join the #opw IRC channel on irc.gnome.org | * Join the #outreachy IRC channel on irc.gnome.org |
| Line 17: | Line 21: |
| * Read our [:OutreachyApply:instructions for applying], and apply by November 2. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by November 2. |
* Read our [:OutreachyApply:instructions for applying], and apply by March 30. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30. |
| Line 25: | Line 29: |
| = Round 11 projects = Round 10 projects are available [:OutreachyRound10:here]. For each project, if you click on the proposer's name, you may find more information. |
= Round 14 projects = Previous projects, from round 13 projects are available [:OutreachyRound13:here]. For each project, if you click on the proposer's name, you may find more information. |
| Line 28: | Line 32: |
| == ADXL377 Triple Axis Accelerometer IIO driver == ''Mentor:'': [:OctavianPurdila:Octavian Purdila], [:DanielBaluta:Daniel Baluta] |
== Finding and fixing resource release bugs == ''Mentor:'': [:JuliaLawall:Julia Lawall] |
| Line 31: | Line 35: |
| 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. | Hector is a tool for finding missing resource release operations (kfree, etc). This project will involve analyzing the reports produced by Hector on Linux kernel code and submitting patches to fix those that are found to be true bugs. |
| Line 33: | Line 37: |
| 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. | == Using an IDR to replace the process ID allocator == ''Mentor:'': [:MatthewWilcox:Matthew Wilcox] |
| Line 35: | Line 40: |
| We will provide you the hardware setup necessary to test the driver. == Staging driver cleanup == ''Mentor:'': [:GregKH: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. |
Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR. |
| Line 47: | Line 47: |
| If you are interested in this project please consider solving any of the following tasks: * Request an account for the wiki.nftables.org page and help us improve the content. * Provide an iptables to nft translation via the iptables-translate utility. You can give a try to the following extensions: icmp, icmp6, rt. * Try to fix any of the existing nft bugs in bugzilla.netfilter.org. |
|
| Line 49: | Line 55: |
| == Ceph-related kernel code cleanup == | == IIO driver == ''Mentors:'': [:DanielBaluta:Daniel Baluta] & [:AlisonSchofield:Alison Schofield] |
| Line 51: | Line 58: |
| ''Mentor:'': [:AlexElder:Alex Elder] | 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. |
| Line 53: | Line 60: |
| 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. | 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 you will enhance the driver with advanced features such as support for buffered readings, power management and interrupts. The exact device will be decided when the internship starts. |
| Line 55: | Line 62: |
| 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). | We will provide you the hardware setup necessary to test the driver. If you are interested in this project please solve ["IIO tasks"]. |
| Line 57: | Line 64: |
| == y2038 cleanup in drivers == | '''For IIO patches, be sure to send them to linux-iio@vger.kernel.org''' |
| Line 59: | Line 66: |
| ''Mentor:'' [:ArndBergmann:Arnd Bergmann] | == Documentation == ''Mentor:'': [:JonathanCorbet:Jonathan Corbet] |
| Line 61: | Line 69: |
| 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 http://en.wikipedia.org/wiki/Year_2038_problem. | After many years of relative neglect, we are working to improve the kernel's documentation; this includes [https://lwn.net/Articles/692704/ a transition to the Sphinx formatting system.] There are a number of potential projects associated with this transition, ranging from the conversion of existing documents into the ReStructured Text format and integrating them into the manual through to improving the Python/Perl-based document build system, adding kerneldoc comments to the source, and writing entirely new documents. |
| Line 63: | Line 71: |
| 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. |
If you want to work in this area, there are a number of things that can be done for the application process, starting with simple typo fixes in the documentation tree. Converting simple text documents to RST is a relatively straightforward task, but contacting the mentor first is recommended, since some parts of the documentation tree are more amenable to this work in the short term than others. We would also love to see fixes for the large number of warnings that are currently emitted as part of the build process. |
| Line 80: | Line 82: |
| * Join the #opw IRC channel on irc.gnome.org | * Join the #outreachy IRC channel on irc.gnome.org |
| Line 82: | Line 84: |
| * Read our [:OutreachyApply:instructions for applying], and apply by November 2. * Use our [:Outreachyfirstpatch: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 [:OutreachyTasks:small task] to complete. |
* Read our [:OutreachyApply:instructions for applying], and apply by March 30. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30. * After you have 10 cleanup patches and at least two patchsets, choose some [:OutreachyTasks:small tasks] to complete. |
Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni)
Please see the [https://www.gnome.org/outreachy/ Outreachy homepage] for an introduction to the program.
The application period for Round 14 will start on February 16, 2016. 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 interested in applying.
We are looking for round 14 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out.
Welcome Outreachy applicants! Our [:OutreachySponsor:round 14 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.
News This year, we ask that you send all patches to the appropriate staging driver maintainers, as well as to the outreachy mailing list. See [:FirstKernelPatch#submit+a+patch:Submit a patch] for more information. For IIO patches, be sure to send them to linux-iio@vger.kernel.org
How to apply
The application period for Outreachy Round 14 is February 16 to March 30. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by March 30, and complete your kernel patch by March 30 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 [:OutreachyApply:application FAQ] for more info on how to fill out your application.
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list]
- Join the #outreachy IRC channel on irc.gnome.org
- Join the #kernel-outreachy IRC channel on irc.oftc.net
Read our [:OutreachyApply:instructions for applying], and apply by March 30.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30.
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 [:Outreachyfirstpatch: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 [:OutreachyTasks:Outreachy tasks page] for details before starting on a task!
Round 14 projects
Previous projects, from round 13 projects are available [:OutreachyRound13:here]. For each project, if you click on the proposer's name, you may find more information.
Finding and fixing resource release bugs
Mentor:: [:JuliaLawall:Julia Lawall]
Hector is a tool for finding missing resource release operations (kfree, etc). This project will involve analyzing the reports produced by Hector on Linux kernel code and submitting patches to fix those that are found to be true bugs.
Using an IDR to replace the process ID allocator
Mentor:: [:MatthewWilcox:Matthew Wilcox]
Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR.
nftables
Mentor:: [:pablo: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.
If you are interested in this project please consider solving any of the following tasks:
- Request an account for the wiki.nftables.org page and help us improve the content.
- Provide an iptables to nft translation via the iptables-translate utility. You can give a try to the following extensions: icmp, icmp6, rt.
- Try to fix any of the existing nft bugs in bugzilla.netfilter.org.
For more information on nftables, please check: http://wiki.nftables.org
IIO driver
Mentors:: [:DanielBaluta:Daniel Baluta] & [:AlisonSchofield:Alison Schofield]
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 you will enhance the driver with advanced features such as 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. If you are interested in this project please solve ["IIO tasks"].
For IIO patches, be sure to send them to linux-iio@vger.kernel.org
Documentation
Mentor:: [:JonathanCorbet:Jonathan Corbet]
After many years of relative neglect, we are working to improve the kernel's documentation; this includes [https://lwn.net/Articles/692704/ a transition to the Sphinx formatting system.] There are a number of potential projects associated with this transition, ranging from the conversion of existing documents into the ReStructured Text format and integrating them into the manual through to improving the Python/Perl-based document build system, adding kerneldoc comments to the source, and writing entirely new documents.
If you want to work in this area, there are a number of things that can be done for the application process, starting with simple typo fixes in the documentation tree. Converting simple text documents to RST is a relatively straightforward task, but contacting the mentor first is recommended, since some parts of the documentation tree are more amenable to this work in the short term than others. We would also love to see fixes for the large number of warnings that are currently emitted as part of the build process.
Project
Mentor:: [:WikiName:Mentor names]
Brief project description.
Yeah, that sounds cool!
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list]
- Join the #outreachy IRC channel on irc.gnome.org
- Join the #kernel-outreachy IRC channel on irc.oftc.net
Read our [:OutreachyApply:instructions for applying], and apply by March 30.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30.
After you have 10 cleanup patches and at least two patchsets, choose some [:OutreachyTasks:small tasks] to complete.