|
Size: 3551
Comment:
|
Size: 6872
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Please see the [https://www.gnome.org/outreachy/ Outreachy homepage] for an introduction to the program. | Please see the [[https://www.gnome.org/outreachy/|Outreachy homepage]] for an introduction to the program. |
| 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 16''' will start in mid February, 2018. 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 16 [[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 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 10: | Line 14: |
| The application period for Outreachy Round 10 is February 17 to March 24. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by '''March 24''', and complete your kernel patch by '''April 1''' (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 our your application. | The application period for Outreachy Round 16 is February 12 to March 22. Please fill your [[https://outreachy.gnome.org/|application]] by '''March 22''', and complete your kernel patch by '''March 22''' 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 14: | Line 18: |
| * Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org |
* Join the [[https://groups.google.com/forum/#!forum/outreachy-kernel|outreachy-kernel mailing list]] * 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 22. * Use our [[Outreachyfirstpatch|tutorial]] to send in your first kernel patch by March 22. |
| Line 23: | Line 27: |
| 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! | 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 25: | Line 29: |
| = Round 11 projects = | = Round 16 projects = Previous projects, from round 15 projects are available [[OutreachyRound15|here]]. For each project, if you click on the proposer's name, you may find more information. |
| Line 27: | Line 32: |
| Round 10 projects are available [:OPWRound10: here]. For each project, if you click on the proposer's name, you may find more information. | == Migrate NAND driver to new exec_op framework == |
| Line 29: | Line 34: |
| == Project == | ''Mentor:'': [[ Eze Garcia|]] |
| Line 31: | Line 36: |
| ''Mentor:'': [:WikiName:Mentor names] | === Major task === |
| Line 33: | Line 38: |
| Brief project description. | Recently, a new NAND framework called "exec_op" was introduced, which sends specific NAND operations to a device, via a single ->exec_o() callback. |
| Line 35: | Line 40: |
| Its goal is to ease the support of complex NAND controllers, while also supporting legacy devices. In other words, it's meant to eventually replace ->cmd_ctrl(), ->cmdfunc() and ->read/write_byte/word/buf() hooks. Currently, a few drivers have been already converted, and others are in the process of being converted. However, many drivers will remain to be converted, some conversions being more complex than others. The goal of this project is to convert one or more NAND device drivers, removing the ->cmd_ctrl() uses and use ->exec_op() instead. |
|
| Line 36: | Line 44: |
| The selected intern will learn generic skills on Linux device drivers development. Also, they will learn specific skills about NAND technology, general MTD support in Linux and the new NAND framework. | |
| Line 37: | Line 46: |
| === Small tasks === Do not start on these tasks until after you complete the Linux kernel first patch tutorial (https://kernelnewbies.org/Outreachyfirstpatch) and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets. The NAND subsystem does not seem to have many small tasks that applicants can engage. We propose to work generic cleanups (i.e. printk to pr_{} conversion), focused in the MTD and NAND subsystems. == 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 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 |
|
| Line 41: | Line 68: |
| * Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org |
* Join the [[https://groups.google.com/forum/#!forum/outreachy-kernel|outreachy-kernel mailing list]] * Join the #outreachy IRC channel on irc.gnome.org |
| Line 44: | Line 71: |
| * Read our [:OutreachyApply:instructions for applying], and apply by March 24. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by 1st April. * 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 Outreachy homepage for an introduction to the program.
The application period for Round 16 will start in mid February, 2018. 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 16 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 16 is February 12 to March 22. Please fill your application by March 22, and complete your kernel patch by March 22 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 March 22.
Use our tutorial to send in your first kernel patch by March 22.
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 16 projects
Previous projects, from round 15 projects are available here. For each project, if you click on the proposer's name, you may find more information.
Migrate NAND driver to new exec_op framework
Mentor:: Eze Garcia
Major task
Recently, a new NAND framework called "exec_op" was introduced, which sends specific NAND operations to a device, via a single ->exec_o() callback.
Its goal is to ease the support of complex NAND controllers, while also supporting legacy devices. In other words, it's meant to eventually replace ->cmd_ctrl(), ->cmdfunc() and ->read/write_byte/word/buf() hooks. Currently, a few drivers have been already converted, and others are in the process of being converted. However, many drivers will remain to be converted, some conversions being more complex than others. The goal of this project is to convert one or more NAND device drivers, removing the ->cmd_ctrl() uses and use ->exec_op() instead.
The selected intern will learn generic skills on Linux device drivers development. Also, they will learn specific skills about NAND technology, general MTD support in Linux and the new NAND framework.
Small tasks
Do not start on these tasks until after you complete the Linux kernel first patch tutorial (https://kernelnewbies.org/Outreachyfirstpatch) and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets.
The NAND subsystem does not seem to have many small tasks that applicants can engage. We propose to work generic cleanups (i.e. printk to pr_{} conversion), focused in the MTD and NAND subsystems.
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
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.