|
Size: 8296
Comment:
|
Size: 7884
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| We are looking for round 10 [: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 10 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and alumni from the [http://ascendproject.org/ 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. | 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 10 is February 17 to March 24. Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process 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 [:OutreachyApply:application FAQ] for more info on how to fill our 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 March 24. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 24. |
* 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 10 projects = More coming soon. Round 9 projects are available [:OPWRound9: 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 30: | Line 33: |
| Line 33: | Line 35: |
| [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. | There will be no Coccinelle project in this round. Please feel free nevertheless to use Coccinelle in making cleanup patches. |
| Line 35: | Line 37: |
| 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. | == Using an IDR to replace the process ID allocator == ''Mentor:'': [:MatthewWilcox:Matthew Wilcox] |
| Line 37: | Line 40: |
| == Media Controller Virtual Driver == | Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR. |
| Line 39: | Line 42: |
| ''Mentor:'': [:LaurentPinchart:Laurent Pinchart] | == nftables == ''Mentor:'': [:pablo:Pablo Neira Ayuso] |
| Line 41: | Line 45: |
| The media subsystem has a kernel [http://lwn.net/Articles/607160/ 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 [http://linuxtv.org/downloads/v4l-dvb-apis/media_controller.html Media Controller] device. Such a driver would be very useful to test handling of complex media pipelines in userspace applications. | 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. |
| Line 43: | Line 47: |
| 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 [http://ideasonboard.org/uvc/faq/#faq1 compatible with the USB Video Class] could be useful to first experiment with the Media Controller API. | If you are interested in this project please consider solving any of the following tasks: |
| Line 45: | Line 49: |
| == Modernize Linux Wireless drivers == | * 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 47: | Line 53: |
| ''Mentor'': [:JesSorensen: Jes Sorensen] | For more information on nftables, please check: http://wiki.nftables.org |
| Line 49: | Line 55: |
| 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. | == IIO driver == ''Mentors:'': [:DanielBaluta:Daniel Baluta] & [:AlisonSchofield:Alison Schofield] |
| Line 51: | Line 58: |
| The goal of this project is to complete the conversion of the Orinoco wireless driver from using the WEXT API and make it a good cfg80211 citizen. | 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: |
| == Full Dynamic Ticks == | 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: |
| ''Mentors'': [:Frederic Weisbecker: Frederic Weisbecker], [:Preeti U Murthy: Preeti U Murthy] | 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: |
| 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. |
'''For IIO patches, be sure to send them to linux-iio@vger.kernel.org''' |
| Line 60: | Line 66: |
| 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. |
== Documentation == ''Mentor:'': [:JonathanCorbet:Jonathan Corbet] |
| Line 65: | Line 69: |
| The goal of this project is to tackle specific issues that are currently in way of running CPUs in Full Dynamic Tick mode effectively. | 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 67: | Line 71: |
| == IIO dummy driver == | 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 69: | Line 73: |
| ''Mentors'': [:DanielBaluta: Daniel Baluta], [:OctavianPurdila: Octavian Purdila] | == Project == ''Mentor:'': [:WikiName:Mentor names] |
| Line 71: | Line 76: |
| 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. |
Brief project description. |
| Line 83: | Line 82: |
| * Join the #opw IRC channel on irc.gnome.org | * Join the #outreachy IRC channel on irc.gnome.org |
| Line 85: | Line 84: |
| * Read our [:OutreachyApply:instructions for applying], and apply by October 31. * Use our [:Outreachyfirstpatch: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 [: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.
Coccinelle
Mentor:: [:JuliaLawall:Julia Lawall]
There will be no Coccinelle project in this round. Please feel free nevertheless to use Coccinelle in making cleanup patches.
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.