7164
Comment: March 19th is the deadline
|
← Revision 58 as of 2018-02-14 14:53:20 ⇥
6863
|
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 6: | Line 7: |
* 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 |
* 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 10: | Line 11: |
= Do you qualify? = | = Patch submission process = |
Line 12: | Line 13: |
We want interns to make sure they qualify for the OPW internship. Read [https://live.gnome.org/OutreachProgramForWomen this page] for more information. | * 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 14: | Line 15: |
The TLDR version of the requirements are that OPW interns: * should be over 18, * should be able to work full-time (40 hours per week) from May 19, 2014 to August 18, 2014, * should be a woman, gender queer or gender fluid individual, and * should not have participated in OPW or Google Summer of Code before. Additionally, we highly recommend that applicants have a stable internet connection, with no download caps. Communication over IRC can be difficult if your internet connection keeps dropping or has a big lag time, so you need a stable internet connection. Downloading the initial kernel will use over 5 GB of data, which will easily blow through a standard 3G capped plan. We recommend making sure you have cable internet, or an unlimited 3G plan. You will get a $500 travel stipend to attend a conference. 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. = How to apply = The OPW kernel project's application process is a little different than what is outlined in the OPW pages. Here's what we need you to do: 1. Look over the list of projects at http://kernelnewbies.org/OPWIntro 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. 3. Fill out your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application], which is shown under the "Send in an Application" section. Email your application to opw-list@gnome.org, in PDF or libreoffice format. If you send it as a Google doc link, you may update your application until March 19th, 2014. At that point, a read-only copy of your application will be saved. 4. Complete the Linux kernel first contribution [:OPWfirstpatch:tutorial] by March 19, 2014, and email your first patch to the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list]. Do not send patches to the main Linux mailing lists! Note that your patch must be '''accepted''' by March 19th, and you may have to go through several patch revisions. The more high-quality 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 [[OutreachyTasks|the task list page]], unless the task specifically says that this is not necessary. |
Line 39: | Line 19: |
Here's some tips for how to answer various questions on the OPW application. | Here are some tips for how to answer various questions on the Outreachy application. |
Line 43: | Line 23: |
''(Not applicable for March applicants).'' This question is designed to make sure that participants in OPW 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. However, the Linux kernel isn't participating in GSoC, so this question does not matter to our organization. We do encourage all students to also apply to GSoC, especially to the [http://www.google-melange.com/gsoc/org2/google/gsoc2014/lf Linux Foundation] projects. | ''(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 49: | Line 29: |
* Have you played with Linux at university labs or other places? | * Have you used Linux at university labs or other places? |
Line 59: | Line 39: |
If you are applying as an OPW kernel intern for the first time, do not worry about providing links to your first kernel patch. Your patches will be tracked by looking at your accepted patches in Greg KH's [https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/ staging driver tree]. If you applied in a previous OPW round and got patches accepted, please note that. | 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 61: | Line 41: |
If you have ever gotten Linux kernel patches accepted outside of the OPW application process, please provide a link to the commits through [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git Linus' git tree]. You can search the log for your patch subject, find the full commit ID, and use it in the URL by placing the commit ID after the "id" part of the URL. E.g. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e9bdc3d6143d1c4b8d8ce5231fc958268331f983 would point to commit ID e9bdc3d6143d1c4b8d8ce5231fc958268331f983. | '''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 65: | Line 45: |
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. Please note the other projects that you are interested in, in order of most interesting to least interesting. Note that you may not get your first or second choice of projects, although we do try. | Please review the [[https://www.outreachy.org/communities/cfp/linux-kernel/|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. |
Line 69: | Line 87: |
You do not need to provide a detailed timeline. Instead, describe why you're passionate about that particular Linux kernel project, and what you hope to learn from that project. Including this optional information will strengthen your application, and increase the chances of getting accepted. |
|
Line 75: | Line 89: |
MAKE SURE YOU SUBMIT YOUR APPLICATION BY MARCH 19th, 2014. You will have the opportunity to update your application with your small contribution until March 19th, 2014. Accepted interns will be notified on April 21st, 2013. |
MAKE SURE YOU SUBMIT YOUR APPLICATION BY MARCH 22, 2018. |
Line 81: | 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]. Make sure you are subscribed to that 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.