|
Size: 3339
Comment:
|
Size: 8915
Comment: converted to 1.6 markup
|
| 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: |
| 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. | The application period for '''Round 15''' will start on September 7, 2017. 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: |
| 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. | We are looking for round 15 [[OutreachySponsor|funding sponsors]] and Linux kernel [[OutreachyMentor|mentors]]. Please see the linked FAQ pages if you want to help out. |
| Line 7: | Line 9: |
| 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.'' | Welcome Outreachy applicants! Our [[OutreachySponsor|round 15 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 15 is September 7 to October 23. Please fill your [[https://live.gnome.org/OutreachProgramForWomen#Application_Process|application]] by '''October 23''', and complete your kernel patch by '''October 23''' 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 October 23. * Use our [[Outreachyfirstpatch|tutorial]] to send in your first kernel patch by October 23. |
| Line 10: | 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 11: | Line 27: |
| === USB === | 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 13: | Line 29: |
| 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). | = Round 15 projects = Previous projects, from round 14 projects are available [[OutreachyRound14|here]]. For each project, if you click on the proposer's name, you may find more information. |
| Line 15: | Line 32: |
| 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. | == dri-devel aka kernel GPU subsystem == |
| Line 17: | Line 34: |
| USB 3.0 hardware will be provided to accepted interns if you don't have access to it. | In laptops, tablets, phones and lots of other places GPU/display uses more silicon die space than everything else combined (humans are mostly visual people after all), dri-devel (and the wider set of projects under the X.org Foundation's umbrella) is the community that makes this all work and shine. |
| Line 19: | Line 36: |
| ''Optional but learnable skills'': Knowledge of USB or other low-level busses | We have a bunch of janitorial-type projects collected in [[https://dri.freedesktop.org/docs/drm/gpu/todo.html]], varying from fairly mechanical to really challenging. We're also taking the usual array of checkpatch and coccinelle driven cleanup patches (they're great newbie starter patches). For an internship this means there's a lot of "build your own internship program", and we're definitely open to other projects. Just chat with mentors to start scoping a good project and what might be interesting for you. |
| Line 21: | Line 38: |
| ''Mentor'': Sarah Sharp. Email: sarah.a.sharp at intel.com. My #opw IRC handle is sarahsharp. [https://www.twitter.com/sarahsharp twitter] and [https://plus.google.com/116960357493251979546/posts google plus] | Bit more PR for dri-devel: We're the subsystem that implemented the new shiny kernel-doc tooling and pushed for the conversion [[https://dri.freedesktop.org/docs/drm/gpu/index.html]]. We're the first ever kernel subsystem with a real CoC (and yes it's enforced)[[https://dri.freedesktop.org/docs/drm/gpu/introduction.html#code-of-conduct]]. We're running our main trees with a much more participative model where all regular contributors have direct commit rights to relevant repos (instead of having to always jump through maintainers to get anything landed)[[http://blog.ffwll.ch/2016/09/commit-rights-in-the-linux-kernel.html]]. In short, we take newbie's and our contributor's needs in general very serious and try to care for them. |
| Line 23: | Line 40: |
| ''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] | Best place to say hi to the community is by joining #dri-devel on freenode. You need a registered nick: https://freenode.net/kb/answer/registration |
| Line 25: | Line 42: |
| == Ethernet == | ''Mentors:'': [[Daniel_Vetter|Daniel Vetter]], [[SeanPaul|Sean Paul]] |
| Line 27: | Line 44: |
| [http://lh6.ggpht.com/_KnE2M8e3X8Q/S6z4IPztwSI/AAAAAAAAE_Y/7O7nJuT8deQ/s200/130659908_922e26a071_b.jpg] | == attribute documentation == ''Mentor:'': [[JuliaLawall|Julia Lawall]] |
| Line 29: | Line 47: |
| 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. | The Linux kernel has many configurable parameters, declared as eg DEVICE_ATTR_RO. These should be represented in the kernel documentation, but many are not. The goal of this project will be to develop tools, likely using [[http://coccinelle.lip6.fr/:Coccinelle]], to help collect information relevant to such documentation and to create an appropriate documentation skeleton, and then to work on filling in some such documentation, based on study of the code, comments, etc. Relevant tasks will appear on the page of the mentor. |
| Line 31: | Line 49: |
| 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. | == nftables == ''Mentor:'': [[pablo|Pablo Neira Ayuso]] |
| Line 33: | Line 52: |
| ''Optional but learnable skills:'' Knowledge of network protocols | 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 35: | Line 54: |
| ''Mentors:'' Carolyn Wyborny and Anjali Jain | If you are interested in this project then: |
| Line 37: | Line 56: |
| == x86 core == | * Install a fresh Linux kernel, from git sources, and latest git snapshots for libmnl, libnftnl and nftables. You can find more information on how to set up your enviroment at wiki.nftables.org. * Make sure you understand basic operational of nftables, read existing documentation. * Once you're fully set up, you got basic understanding of the tooling and everything is working on your side, then contact the mentor to request for an initial task. |
| Line 39: | Line 60: |
| In the heart of the Linux kernel is code that runs directly on x86 processors. This includes early boot code, etc. | For more information on nftables, please check: http://wiki.nftables.org |
| Line 41: | Line 62: |
| ''Optional but learnable skills:'' Knowledge of computer architecture | == IIO driver == ''Mentors:'': [[DanielBaluta|Daniel Baluta]] & [[AlisonSchofield|Alison Schofield]] |
| Line 43: | Line 65: |
| ''Mentors:'' Peter Waskiewicz Jr (PJ) | 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 45: | Line 67: |
| 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''' == Project == ''Mentor:'': [[WikiName|Mentor names]] Brief project description. |
|
| Line 47: | Line 79: |
| If you are interested in being a Linux kernel intern, please: | |
| Line 48: | Line 81: |
| If you're interested in our Linux kernel projects, please read the guide to [:OPWfirstpatch:sending your first patch]. == Creative Commons Photo Credits == [http://www.flickr.com/photos/pfly/130659908/ Ethernet] |
* 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 Outreachy homepage for an introduction to the program.
The application period for Round 15 will start on September 7, 2017. 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 15 funding sponsors and Linux kernel mentors. Please see the linked FAQ pages if you want to help out.
Welcome Outreachy applicants! Our round 15 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 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 15 is September 7 to October 23. Please fill your application by October 23, and complete your kernel patch by October 23 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:
Join the 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 instructions for applying, and apply by October 23.
Use our tutorial to send in your first kernel patch by October 23.
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 15 projects
Previous projects, from round 14 projects are available here. For each project, if you click on the proposer's name, you may find more information.
dri-devel aka kernel GPU subsystem
In laptops, tablets, phones and lots of other places GPU/display uses more silicon die space than everything else combined (humans are mostly visual people after all), dri-devel (and the wider set of projects under the X.org Foundation's umbrella) is the community that makes this all work and shine.
We have a bunch of janitorial-type projects collected in https://dri.freedesktop.org/docs/drm/gpu/todo.html, varying from fairly mechanical to really challenging. We're also taking the usual array of checkpatch and coccinelle driven cleanup patches (they're great newbie starter patches). For an internship this means there's a lot of "build your own internship program", and we're definitely open to other projects. Just chat with mentors to start scoping a good project and what might be interesting for you.
Bit more PR for dri-devel: We're the subsystem that implemented the new shiny kernel-doc tooling and pushed for the conversion https://dri.freedesktop.org/docs/drm/gpu/index.html. We're the first ever kernel subsystem with a real CoC (and yes it's enforced)https://dri.freedesktop.org/docs/drm/gpu/introduction.html#code-of-conduct. We're running our main trees with a much more participative model where all regular contributors have direct commit rights to relevant repos (instead of having to always jump through maintainers to get anything landed)http://blog.ffwll.ch/2016/09/commit-rights-in-the-linux-kernel.html. In short, we take newbie's and our contributor's needs in general very serious and try to care for them.
Best place to say hi to the community is by joining #dri-devel on freenode. You need a registered nick: https://freenode.net/kb/answer/registration
Mentors:: Daniel Vetter, Sean Paul
attribute documentation
Mentor:: Julia Lawall
The Linux kernel has many configurable parameters, declared as eg DEVICE_ATTR_RO. These should be represented in the kernel documentation, but many are not. The goal of this project will be to develop tools, likely using http://coccinelle.lip6.fr/:Coccinelle, to help collect information relevant to such documentation and to create an appropriate documentation skeleton, and then to work on filling in some such documentation, based on study of the code, comments, etc. Relevant tasks will appear on the page of the mentor.
nftables
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.
If you are interested in this project then:
- Install a fresh Linux kernel, from git sources, and latest git snapshots for libmnl, libnftnl and nftables. You can find more information on how to set up your enviroment at wiki.nftables.org.
- Make sure you understand basic operational of nftables, read existing documentation.
- Once you're fully set up, you got basic understanding of the tooling and everything is working on your side, then contact the mentor to request for an initial task.
For more information on nftables, please check: http://wiki.nftables.org
IIO driver
Mentors:: Daniel Baluta & 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
Project
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 #outreachy IRC channel on irc.gnome.org
- Join the #kernel-outreachy IRC channel on irc.oftc.net
Read our instructions for applying, and apply by March 30.
Use our tutorial to send in your first kernel patch by March 30.
After you have 10 cleanup patches and at least two patchsets, choose some small tasks to complete.