|
Size: 3318
Comment:
|
Size: 6847
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Applying for OPW = | ## page was renamed from OPWApply = Applying for Outreachy = |
| Line 3: | Line 4: |
| Thank you for your interest in the Linux kernel internships! Please read the following thoroughly | Thank you for your interest in the Linux kernel internships! Please read the following thoroughly. |
| Line 5: | Line 6: |
| = Do you qualify? = | Also, make sure you: * 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 |
| Line 7: | Line 11: |
| We want interns to make sure they qualify for the OPW internship. Read [https://live.gnome.org/OutreachProgramForWomen this page] for more information. | = Patch submission process = |
| Line 9: | Line 13: |
| The TLDR version of the requirements are that OPW interns: | * Complete the Linux kernel first contribution [[Outreachyfirstpatch|tutorial]] by March 22, 2018, and email your first patch to the [[https://groups.google.com/forum/#!forum/outreachy-kernel|outreachy-kernel mailing list]] and the relevant maintainers. Do not send patches to the main Linux mailing lists! Note that your patch must be '''accepted''' by March 22, and you may have to go through several patch revisions. The more high-quality, complex patches you get accepted, the more likely your chance of getting accepted for an internship. Note that we look at patch quality, communication style, ability to learn, and applicant background as well, so don't get discouraged if you see people sending a lot of patches. Submit early and often! |
| Line 11: | Line 15: |
| * should be over 18, * should be able to work full-time (40 hours per week) from June 17 to Sept 23, * should identify as a woman, or be gender queer or gender fluid, and * should not have participated in OPW or Google Summer of Code before. |
* Complete at least one small task from the projects you are interested in. Completing small tasks for a particular project makes it more likely that you'll be accepted for that project. Make sure to complete tasks for a couple of different projects, because it's often the case that some of the projects will get a lot of applicants. '''Before''' you start on a small task, please claim that task on [[OutreachyTasks|the task list page]], unless the task specifically says that this is not necessary. |
| Line 16: | Line 17: |
| We also want interns to speak at either [https://events.linuxfoundation.org/events/linuxcon LinuxCon North America] (in September) or [https://events.linuxfoundation.org/events/linuxcon-europe LinuxCon Europe] (in October) about your project. | = Application tips = |
| Line 18: | Line 19: |
| You will get a $500 travel stipend to attend. Linux conferences are a lot of fun, because you get to meet professional Linux developers, and there's a lot of opportunity for networking and job hunting. | Here are some tips for how to answer various questions on the Outreachy application. |
| Line 20: | Line 21: |
| = How to apply = | '''''Are you planning to apply for Google Summer of Code?''''' |
| Line 22: | Line 23: |
| Since the kernel project joined OPW late, our application process is a little different than what is outlined in the OPW pages. Here's what we need you to do: | ''(Not applicable for December applicants).'' This question is designed to make sure that participants in Outreachy also apply to GSoC if they meet the summer of code [[http://www.google-melange.com/gsoc/homepage/google/gsoc2013|applicant requirements]]. Basically, the idea was to make sure applicants get the most chances to get an internship. We do encourage all students to also apply to GSoC, especially to the [[https://wiki.linuxfoundation.org/gsoc/2016-gsoc-kernel-work|Linux Foundation]] projects. |
| Line 24: | Line 25: |
| 1. Look over the list of projects at http://kernelnewbies.org/OPWIntro | '''''Please describe your experience with the organization's product as a user and as a contributor (include the information about the contribution you made to the project you are interested in here):''''' |
| Line 26: | Line 27: |
| 2. Find a project there that interests you, and email the mentor. Introduce yourself, let the mentor know why you think that project would be a good fit for you, and ask the mentor any questions about the project. | Please include some information about yourself, such as: * Do you run Linux on your personal computers? * Have you used Linux at university labs or other places? * What Linux distros do you use? * Have you ever compiled a custom kernel? * Have you ever made a change to a kernel driver? * Have you ever contributed a patch to the mainline kernel? If so, please provide links to the patches, and indicate whether they were accepted. * Do you have C or C++ experience? * Have you taken operating systems or computer architecture classes before? * Do you have experience with the command line? * Have you compiled a project before? |
| Line 28: | Line 39: |
| 3. Fill out your [https://live.gnome.org/OutreachProgramForWomen initial application], which is shown under the "Send in an Application" section. Email your application to opw-list@gnome.org | Please provide a link to all patches authored by you, e.g. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=author&q=Sarah+Sharp. If a contribution has been accepted into another mentor's tree but not into Greg or Linus' tree, please ask them to provide a link to that contribution. |
| Line 30: | Line 41: |
| We'll be contacting potential applicants by the end of this week, through this mailing list, to announce how you can make your small contribution to the Linux kernel. You can and should submit your initial application without doing the small contribution. | '''Important Update''' This year, the applicants are required to add their contributions on the Outreachy application form along with a detailed description. Please provide a link to all your patches in the application. |
| Line 32: | Line 43: |
| AGAIN, MAKE SURE YOU SUBMIT YOUR APPLICATION BY MAY 1st. | '''''Who is a possible mentor for the project you are most interested in?''''' |
| Line 34: | Line 45: |
| You will have the opportunity to update your application with your small contribution by May 17th. Accepted interns will be notified on May 27th. | Please review the [[http://kernelnewbies.org/OutreachyIntro|participating Linux kernel projects]]. List the projects that you are interested in participating with, in order from the most interesting project to the least interesting project. For each project, say why you are interested in this particular project (e.g. it fits your background or interests in school, or the mentor has been particularly helpful, etc.). If you have completed any small todo items for that particular project, please link to those accepted contributions. Here is an example list: |
| Line 36: | Line 47: |
| = Further FAQ = | {{{ First choice ------------ Project name: EHCI driver rewrite Mentor: Alan Stern Reason for choice: I'm interested in EHCI because I have been working on code for USB to serial adapters, and I want to learn more about the USB host controller driver. Completed tasks: Greg KH has accepted my patch to remove the FISH/SOUP macros from the PL2303 driver. https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?id=eb44da0b3aa0105cb38d81c5747a8feae64834be |
| Line 38: | Line 57: |
| When you get to the part of the application that asks these two questions: | Second choice ------------- Project name: TTY code cleanups Mentor: Alan Cox Reason for choice: I like the idea of learning more about the TTY layer. Completed tasks: I started on Alan's suggestion to trace the TTY layer by running ftrace on a write call to a USB serial adapter TTY file. The completed graphviz output can be found here. |
| Line 40: | Line 65: |
| "Who is a possible mentor for the project you are most interested in? | Third choice ------------ Project name: Sparse warning cleanups Mentor: Josh Triplett Reason for choice: Josh is very responsive as a patch reviewer, and I have been able to learn a lot about sparse by following his advice. I hope to work more with him on sparse cleanups. Completed tasks: I completed one patch, which is now available here. |
| Line 42: | Line 73: |
| Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):" | Fourth choice ------------ Project name: HPET timer coalescing Mentor: Tony Luck Reason for choice: I don't have any background in servers or embedded Linux systems, but I would like to learn more about them. Diving into the timer subsystem seems to be a good way to start learning about this area. Completed tasks: None. }}} |
| Line 44: | Line 83: |
| Please review the [http://kernelnewbies.org/OPWIntro participating Linux kernel projects]. Pick the project that you're most passionate about (or two projects) and put those mentors names on the first question. | Note that you may not get your first or second choice of projects. Often a particular project is very popular, and we may need to move further down your list of projects. Please make sure to list as many projects you are interested in as possible, even if you haven't completed a task specifically for that project. |
| Line 46: | Line 85: |
| For the second question, you do not need to provide a detailed timeline. Instead, describe why you're passionate about that particular Linux kernel project, and what qualifies you to work on that project. | '''''Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):''''' |
| Line 48: | Line 87: |
| Please note that interns may be switching between Linux kernel projects, as we find more work, so you may work on multiple projects. | = Application Deadlines = MAKE SURE YOU SUBMIT YOUR APPLICATION BY MARCH 22, 2018. |
| Line 52: | Line 93: |
| Contact sarahsharp on #opw (irc.gnome.net) or #kernel-opw (irc.oftc.net), or email the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list]. | Contact jlawall, shraddha or vaishali on #outreachy (irc.gnome.net) or #kernel-outreachy (irc.oftc.net), or email the [[https://groups.google.com/forum/#!forum/outreachy-kernel|outreachy-kernel mailing list]]. Make sure you are subscribed to that mailing list. |
Applying for Outreachy
Thank you for your interest in the Linux kernel internships! Please read the following thoroughly.
Also, make sure you:
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
Patch submission process
Complete the Linux kernel first contribution tutorial by March 22, 2018, and email your first patch to the outreachy-kernel mailing list and the relevant maintainers. Do not send patches to the main Linux mailing lists! Note that your patch must be accepted by March 22, and you may have to go through several patch revisions. The more high-quality, complex patches you get accepted, the more likely your chance of getting accepted for an internship. Note that we look at patch quality, communication style, ability to learn, and applicant background as well, so don't get discouraged if you see people sending a lot of patches. Submit early and often!
Complete at least one small task from the projects you are interested in. Completing small tasks for a particular project makes it more likely that you'll be accepted for that project. Make sure to complete tasks for a couple of different projects, because it's often the case that some of the projects will get a lot of applicants. Before you start on a small task, please claim that task on the task list page, unless the task specifically says that this is not necessary.
Application tips
Here are some tips for how to answer various questions on the Outreachy application.
Are you planning to apply for Google Summer of Code?
(Not applicable for December applicants). This question is designed to make sure that participants in Outreachy also apply to GSoC if they meet the summer of code applicant requirements. Basically, the idea was to make sure applicants get the most chances to get an internship. We do encourage all students to also apply to GSoC, especially to the Linux Foundation projects.
Please describe your experience with the organization's product as a user and as a contributor (include the information about the contribution you made to the project you are interested in here):
Please include some information about yourself, such as:
- Do you run Linux on your personal computers?
- Have you used Linux at university labs or other places?
- What Linux distros do you use?
- Have you ever compiled a custom kernel?
- Have you ever made a change to a kernel driver?
- Have you ever contributed a patch to the mainline kernel? If so, please provide links to the patches, and indicate whether they were accepted.
- Do you have C or C++ experience?
- Have you taken operating systems or computer architecture classes before?
- Do you have experience with the command line?
- Have you compiled a project before?
Please provide a link to all patches authored by you, e.g. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=author&q=Sarah+Sharp. If a contribution has been accepted into another mentor's tree but not into Greg or Linus' tree, please ask them to provide a link to that contribution.
Important Update This year, the applicants are required to add their contributions on the Outreachy application form along with a detailed description. Please provide a link to all your patches in the application.
Who is a possible mentor for the project you are most interested in?
Please review the participating Linux kernel projects. List the projects that you are interested in participating with, in order from the most interesting project to the least interesting project. For each project, say why you are interested in this particular project (e.g. it fits your background or interests in school, or the mentor has been particularly helpful, etc.). If you have completed any small todo items for that particular project, please link to those accepted contributions. Here is an example list:
First choice ------------ Project name: EHCI driver rewrite Mentor: Alan Stern Reason for choice: I'm interested in EHCI because I have been working on code for USB to serial adapters, and I want to learn more about the USB host controller driver. Completed tasks: Greg KH has accepted my patch to remove the FISH/SOUP macros from the PL2303 driver. https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?id=eb44da0b3aa0105cb38d81c5747a8feae64834be Second choice ------------- Project name: TTY code cleanups Mentor: Alan Cox Reason for choice: I like the idea of learning more about the TTY layer. Completed tasks: I started on Alan's suggestion to trace the TTY layer by running ftrace on a write call to a USB serial adapter TTY file. The completed graphviz output can be found here. Third choice ------------ Project name: Sparse warning cleanups Mentor: Josh Triplett Reason for choice: Josh is very responsive as a patch reviewer, and I have been able to learn a lot about sparse by following his advice. I hope to work more with him on sparse cleanups. Completed tasks: I completed one patch, which is now available here. Fourth choice ------------ Project name: HPET timer coalescing Mentor: Tony Luck Reason for choice: I don't have any background in servers or embedded Linux systems, but I would like to learn more about them. Diving into the timer subsystem seems to be a good way to start learning about this area. Completed tasks: None.
Note that you may not get your first or second choice of projects. Often a particular project is very popular, and we may need to move further down your list of projects. Please make sure to list as many projects you are interested in as possible, even if you haven't completed a task specifically for that project.
Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):
Application Deadlines
MAKE SURE YOU SUBMIT YOUR APPLICATION BY MARCH 22, 2018.
Still have questions?
Contact jlawall, shraddha or vaishali on #outreachy (irc.gnome.net) or #kernel-outreachy (irc.oftc.net), or email the outreachy-kernel mailing list. Make sure you are subscribed to that mailing list.