|
Size: 7082
Comment:
|
Size: 4720
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from OPWIntro | |
| Line 2: | 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 4: | Line 5: |
| We are looking for round 10 [: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 17''' is '''now open'''! Please follow the [[https://kernelnewbies.org/OutreachyfirstpatchSetup| setup directions]] and complete the [[Outreachyfirstpatch|first patch tutorial]] before submitting patches to the mailing list. |
| Line 6: | Line 7: |
| Welcome OPW applicants! Our [:OPWSponsor: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. | '''Important Update''' This year, applicants are expected to check their [[https://www.outreachy.org/apply/eligibility/|eligibility]] before getting started with patch submissions. Welcome Outreachy applicants! Our [[OutreachySponsor|round 17 sponsors]] have generously 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 9: | Line 14: |
| The application period for OPW Round 10 is February 17 to March 24. Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application] by March 24, and complete your initial 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 [:OPWApply:application FAQ] for more info on how to fill our your initial application. | The application period for Outreachy Round 17 is September 19 to October 30. Please fill your [[https://outreachy.gnome.org/|application]] by '''October 30''', and complete your kernel patch by '''October 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 the [[https://www.outreachy.org/apply/|application FAQ]] for more info on how to fill out your application. |
| Line 13: | 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 #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by March 24. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by March 24. |
* 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 [[https://www.outreachy.org/apply/|instructions for applying]], and apply by October 30. * Use our [[Outreachyfirstpatch|tutorial]] to send in your first kernel patch by October 30. |
| Line 22: | 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 [:OPWfirstpatch: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 [:OPWTasks:OPW 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 24: | Line 29: |
| = Round 10 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 26: | Line 32: |
| 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. | == Migrate NAND driver to new exec_op framework == ''Mentor:'': [[ Eze Garcia|]] == Netfilter/Nftables == ''Mentor:'': [[pablo|Pablo Neira Ayuso]] == Non-cooperative userfaultfd stress test == ''Mentor:'': [[ Mike Rapoport |]] == Dri-devel aka kernel GPU subsystem == ''Mentor:'': [[Daniel_Vetter|Daniel Vetter]] |
| Line 28: | Line 41: |
| == Coccinelle == ''Mentor:'': [:JuliaLawall:Julia Lawall] [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. 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. == Media Controller Virtual Driver == ''Mentor:'': [:LaurentPinchart:Laurent Pinchart] 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. 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. == Modernize Linux Wireless drivers == ''Mentor'': [:JesSorensen: Jes Sorensen] 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. 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. == Full Dynamic Ticks == ''Mentors'': [:Frederic Weisbecker: Frederic Weisbecker], [:Preeti U Murthy: Preeti U Murthy] 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. 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. The goal of this project is to tackle specific issues that are currently in way of running CPUs in Full Dynamic Tick mode effectively. |
Please check the [[https://www.outreachy.org/communities/cfp/linux-kernel/| Linux kernel page]] on the Outreachy website for detailed project descriptions. |
| Line 69: | Line 46: |
| * 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 October 31. * Use our [:OPWfirstpatch: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 [:OPWTasks:small task] to complete. |
* 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 [[https://www.outreachy.org/apply/|instructions for applying]], and apply by October 30. * Use our [[Outreachyfirstpatch|tutorial]] to send in your first kernel patch by October 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 17 is now open! Please follow the setup directions and complete the first patch tutorial before submitting patches to the mailing list.
Important Update This year, applicants are expected to check their eligibility before getting started with patch submissions.
Welcome Outreachy applicants! Our round 17 sponsors have generously 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 17 is September 19 to October 30. Please fill your application by October 30, and complete your kernel patch by October 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 the 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 30.
Use our tutorial to send in your first kernel patch by October 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 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
Netfilter/Nftables
Mentor:: Pablo Neira Ayuso
Non-cooperative userfaultfd stress test
Mentor:: Mike Rapoport
Dri-devel aka kernel GPU subsystem
Mentor:: Daniel Vetter
Please check the Linux kernel page on the Outreachy website for detailed project descriptions.
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 October 30.
Use our tutorial to send in your first kernel patch by October 30.
After you have 10 cleanup patches and at least two patchsets, choose some small tasks to complete.