6279
Comment:
|
8915
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) = Please see the [https://wiki.gnome.org/OutreachProgramForWomen FOSS Outreach Program for Women homepage] for an introduction to the program. |
## 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 4: | Line 5: |
We are looking for round 8 [:OPWSponsor:funding sponsors] and Linux kernel [:OPWMentor:mentors]. Please see the linked FAQ pages if you want to help out. | 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 6: | Line 7: |
attachment:pinktux.png | 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 8: | Line 9: |
Welcome OPW applicants! Our [:OPWSponsor:round 8 sponsors] have generiously donated funds for internships for women and genderqueer/genderfluid people 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. | 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''' |
Line 11: | Line 14: |
The application period for OPW Round 8 is Feb 25th to March 19th. Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application] and complete your initial kernel patch by March 19th. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OPWApply:application FAQ] for more info on how to fill our your initial application. Applicants will be notified in late March if they have been accepted. | 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. |
Line 15: | Line 18: |
* Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by March 19th. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by March 19th. We also encourage all OPW applicants that are students to also apply to [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code], and in particular the [http://www.google-melange.com/gsoc/org2/google/gsoc2014/lf Linux Foundation projects]. The Google Summer of Code projects are separate from the projects listed below, so you will need to work on applications for both programs. |
* 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 26: | Line 27: |
Round 8 (May to August 2014) projects: | 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 28: | Line 29: |
== Coccinelle == | = 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 30: | Line 32: |
[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 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. |
== dri-devel aka kernel GPU subsystem == |
Line 33: | Line 34: |
The goal of this internship is to help build up the set of semantic patches that are included in the Linux kernel. This will involve primarily hardening semantic patches that have been developed previously, and putting them in the form used in the semantic patches Linux kernel. There is ample opportunity to contribute patches to Linux source code as part of the semantic patch hardening process. | 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 35: | Line 36: |
''Mentor:'' [http://kernelnewbies.org/JuliaLawall Julia Lawall] | 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 37: | Line 38: |
== Linux-Kernel RCU == | 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 39: | Line 40: |
Potential projects include: | 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 41: | Line 42: |
1. Automatically Locate RCU Abuses 1. Inline __rcu_read_lock() __ 1. Add kmem_cache_free_rcu() 1. Validate RCU Algorithms 1. Automate Testing of RCU CPU Stall Warnings 1. Port RCU's KVM Scripts 1. Miscellaneous Fixes to RCU |
''Mentors:'': [[Daniel_Vetter|Daniel Vetter]], [[SeanPaul|Sean Paul]] |
Line 49: | Line 44: |
For more details on each project, please see [http://kernelnewbies.org/OPWIntro-RCU this page]. | == attribute documentation == ''Mentor:'': [[JuliaLawall|Julia Lawall]] |
Line 51: | Line 47: |
''Mentor:'' Paul E. McKenney < paulmck@linux.vnet.ibm.com > == ath5k == [http://wireless.kernel.org/en/users/Drivers/ath5k Ath5k] is a completely FOSS wireless driver for Atheros based wireless chipset versions AR5xxx in the Linux Kernel. The hardware is old but the driver is still heavily used on academia/research and on various modern applications (e.g. 802.11p). Some time ago Adrian Chadd released code on AR5513 (the Atheros HAL -Hardware Access Layer- for that chipset), it's a chipset able to do 802.11a/b/g with a smart antenna/dual PHY design. The goal of this project is to port this code on ath5k and add support for AR5513. In the process you'll get familiar with the low level parts of wireless cards, the inner workings of a device driver, the related subsystems and the challenges we face when playing with hardware. ''Mentors:'' [http://kernelnewbies.org/NickKossifidis Nick Kossifidis], Adrian Chadd |
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 62: | Line 50: |
''Mentor:'': [[pablo|Pablo Neira Ayuso]] | |
Line 63: | Line 52: |
[http://www.netfilter.org/projects/nftables/ nftables] is a new firewalling framework available since the Linux kernel 3.13. It includes new userspace libraries and utilities that aim to replace the popular [http://www.netfilter.org/projects/iptables/ {ip,ip6,arp,eb}tables] utilities. | 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 65: | Line 54: |
The goal of this internship is to help to improve nftables, this includes: | If you are interested in this project then: |
Line 67: | Line 56: |
1. chase bugs and fix them. We already have a good bunch in the [http://bugzilla.netfilter.org Netfilter's bugzilla website]. 1. implement an automated testing infrastructure for nftables that would help to catch regressions. 1. help us implement some of the missing [http://people.netfilter.org/pablo/map-pending-work.txt features]. |
* 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 71: | Line 60: |
Please, read the [http://wiki.nftables.org nftables HOWTO] to get familiarized with the new software. | For more information on nftables, please check: http://wiki.nftables.org |
Line 73: | Line 62: |
''Mentor:'' [http://kernelnewbies.org/Pablo Pablo Neira Ayuso] | == IIO driver == ''Mentors:'': [[DanielBaluta|Daniel Baluta]] & [[AlisonSchofield|Alison Schofield]] |
Line 75: | Line 65: |
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:'': [[WikiName|Mentor names]] Brief project description. |
|
Line 79: | Line 81: |
* Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by March 19th. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by March 19th. == Creative Commons Photo Credits == [http://tux.crystalxp.net/ Pink Tux] |
* 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.