|
Size: 4316
Comment:
|
Size: 7835
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = FOSS Outreach Program for Women (OPW) = | ## page was renamed from OPWIntro = 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. |
| Line 3: | Line 5: |
| attachment:pinktux.png | 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 5: | Line 7: |
| Welcome OPW applicants! The Linux Foundation is sponsoring internships for women 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. |
| Line 7: | Line 9: |
| The official deadline for applying to OPW is May 1st. However, the kernel project joined late, so that deadline is flexible. Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application], and then update by May 17th with your initial patch. Applicants will be notified by May 27th if they have been accepted. | 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. |
| Line 9: | Line 11: |
| Applicants for all projects should have basic experience with C or C++. 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.'' | '''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. = 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. |
| Line 12: | Line 25: |
| 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.'' | |
| Line 13: | Line 27: |
| == Ethernet == | 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! |
| Line 15: | Line 29: |
| [http://lh6.ggpht.com/_KnE2M8e3X8Q/S6z4IPztwSI/AAAAAAAAE_Y/7O7nJuT8deQ/s200/130659908_922e26a071_b.jpg] | = 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 17: | Line 32: |
| The Linux kernel ethernet drivers communicate with network hardware, to give you access to the Internet. Ethernet devices can be as simple as the 1 gigabit ethernet controllers in your laptop, to much faster ethernet controllers in servers. | == Finding and fixing resource release bugs == ''Mentor:'': [:JuliaLawall:Julia Lawall] |
| Line 19: | Line 35: |
| Interns would work on the Intel 1 gigabit ethernet driver, igb. These devices are found in most Intel laptops, but hardware will be provided if you don't have access to it. | 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 21: | Line 37: |
| ''Optional but learnable skills:'' Knowledge of network protocols | == Using an IDR to replace the process ID allocator == ''Mentor:'': [:MatthewWilcox:Matthew Wilcox] |
| Line 23: | Line 40: |
| ''Mentors:'' Carolyn Wyborny and Anjali Jain [:AnjaliJain:(contact info)] | Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR. |
| Line 25: | Line 42: |
| === USB === | == nftables == ''Mentor:'': [:pablo:Pablo Neira Ayuso] |
| Line 27: | Line 45: |
| attachment:usb-sushi.jpg | 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 29: | Line 47: |
| The Linux kernel includes a USB stack that communicates with the hardware behind your USB ports (USB host controller drivers), and includes USB device drivers that talk to your USB devices (USB device drivers). | If you are interested in this project please consider solving any of the following tasks: |
| Line 31: | Line 49: |
| Interns would work on the USB 3.0 host controller driver. The Linux kernel USB 3.0 host driver works 10 times faster than USB 2.0 host driver. The USB 3.0 driver still needs a lot of work, so there are plenty of small bug fixes that interns can tackle. If time permits, interns could also work on small to medium features. | * 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 33: | Line 53: |
| USB 3.0 hardware will be provided to accepted interns if you don't have access to it. | For more information on nftables, please check: http://wiki.nftables.org |
| Line 35: | Line 55: |
| ''Required skills'': Experience with manipulating linked lists in C, knowledge of basic boolean algrebra (bit masks and manipulating bits) | == IIO driver == ''Mentor:'': [:DanielBaluta:Daniel Baluta] |
| Line 37: | Line 58: |
| ''Optional but learnable skills'': Knowledge of USB or other low-level busses | 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 39: | Line 60: |
| ''Mentor'': Sarah Sharp [:SarahSharp:(contact info)] | 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 41: | Line 62: |
| ''Suggested reading for accepted interns'': [http://lwn.net/Kernel/LDD3/ Linux Device Drivers] and [http://www.beyondlogic.org/usbnutshell/usb1.shtml USB in a Nutshell] | We will provide you the hardware setup necessary to test the driver. If you are interested in this project please solve ["IIO tasks"]. |
| Line 43: | Line 64: |
| == Documentation == ''Mentor:'': [:JonathanCorbet:Jonathan Corbet] |
|
| Line 44: | Line 67: |
| == x86 core == | 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 46: | Line 69: |
| attachment:tux-hardware.jpg | 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 48: | Line 71: |
| In the heart of the Linux kernel is code that runs directly on x86 processors. This includes early boot code, etc. | == Project == ''Mentor:'': [:WikiName:Mentor names] |
| Line 50: | Line 74: |
| This part of the kernel is usually considered one of the more complex areas of the operating system. However, with a bit of guidance, it's really fascinating to see how a computer begins the journey from powered off to a blinking cursor at your login prompt. Interns would work alongside PJ on central boot code in the Linux kernel. Today, the kernel brings CPU's online one by one in a serial fashion. We can do better. Several stages of changes are planned to go from a completely serial approach to a fully parallel approach to bringing CPU's up. Interns would work on some of these planned changes. ''Required skills:'' Knowledge of how to use and manipulate pointers and function pointers in C is a must. ''Optional but learnable skills:'' Knowledge of computer architecture, x86 assembly ''Mentors:'' Peter Waskiewicz Jr (PJ) [:PeterWaskiewicz:(contact info)] |
Brief project description. |
| Line 62: | Line 77: |
| If you are interested in being a Linux kernel intern, please: | |
| Line 63: | Line 79: |
| If you're interested in our Linux kernel projects, please read the guide to [:OPWfirstpatch:sending your first patch]. == Creative Commons Photo Credits == [http://tux.crystalxp.net/ Pink Tux], [http://www.flickr.com/photos/pfly/130659908/ Ethernet], [http://www.flickr.com/photos/zopeuse/56910709/ Tux on Hardware] |
* 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. |
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.
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
Mentor:: [:DanielBaluta: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 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"].
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.