## page was renamed from OPWCoordinators ''This page needs to be cleaned up to mention Outreachy where appropriate instead of OPW'' ---- <> = Timeline = == "Meta" tasks == * Notice any common mistakes that applicants make in their tasks. Check if the tutorial covers those mistakes. If not, update the documentation so applicants won't make those mistakes. * Make sure that someone responds to a first patch posting by an applicant within a day. That first patch is critical for getting them hooked, and having them wait more than a day is disheartening. * Watch applicants, and push them if they've been "coasting" for a while. E.g. if they've gotten 10 single patches accepted, push them to do patchsets. Once a couple patchsets have been accepted, point them to tools to try (sparse or Coccinelle) or small tasks to be tackled. == One Month Before Outreachy Application == 1. Find mentors. Assume more than half of them will flake out. Of the ones that don't flake out, about half the mentors will be really responsive during the application period, and the other half won't review patches or interact with applicants very much. See Round 9 mentor section for where each mentor is in the process of getting involved. 2. Pursue sponsorship. You may have to learn when to hit certain people's budget deadlines. Most people need at least a quarter's worth of notice before they will need to pay out the sponsorship. == First week of application period == September 12th for round 9: * Welcome email to applicants, outlining the application process, and any changes from the last round. This is important to note, since some people may have applied last round. Sample: {{{ From: To: OPW Kernel Applicants List Cc: Bcc: Subject: [ANNOUNCE] OPW internship applications open tomorrow! Reply-To: Greetings potential Linux kernel OPW interns! Please read this *entire* email, even if you have applied in the past, as some things have changed for this OPW application round. What is OPW? ------------ The next application round for the FOSS Outreach Program for Women (OPW) internships starts tomorrow, September 12. OPW interns are paid $5,500 to work on a full-time internship with an open source mentor from December 9, 2014 to March 9, 2014. Interns are also granted a $500 travel stipend to go to any conference approved by their mentor that relates to their project. Who can apply? -------------- To qualify to apply for Outreachy, you must meet the following requirements: * You must be over 18, * You must be able to work full-time (40 hours per week) from December 9, 2014 to March 9, 2015, * You must be a woman (cis or trans), or a gender queer, gender free, or gender fluid individual, or an alumni of the Ascend Project, and * You cannot have participated in OPW or Google Summer of Code before. What Outreachy projects can you apply to? ----------------------------------- There will be several different open source projects participating in this round of Outreachy, and the full list will be officially announced tomorrow. https://wiki.gnome.org/OutreachProgramForWomen/2014/DecemberMarch#Participating_Organizations It's no secret that the Linux kernel project is participating again, since we already have three new mentors listed on our wiki, and more mentors will be announced soon. http://kernelnewbies.org/OutreachyIntro How do I apply to the Linux kernel project? ------------------------------------------- The application process for the Linux kernel project is outlined here: http://kernelnewbies.org/OPWApply Basically, applicants will need to walk through our tutorial for creating their first Linux kernel patch: http://kernelnewbies.org/OPWfirstpatch Applicants should also join the #opw IRC channel on irc.gnome.org, and the #kernel-opw channel on irc.oftc.net. If you're having trouble with IRC, please ask for help on this mailing list. One change from the last OPW round is that we are encouraging applicants (once they have completed a number of Staging driver cleanup patches) to complete some small tasks outlined by the mentors. The task lists for each mentor are linked from the OPWIntro page. *Before* you start on a task, please claim that task through this page: http://kernelnewbies.org/OPWTasks Another change is that we added a tips section at the end of the tutorial to outline what behaviors we look for in potential OPW interns. I hope this will give more insight into our selection process. http://kernelnewbies.org/OPWfirstpatch#tips We've also noticed that applicants (and even accepted interns!) aren't consistently using the email communication style preferred by the Linux kernel community. This style can be as important as coding style to many community members, so please review the email style guidelines and attempt to follow them: http://kernelnewbies.org/OPWfirstpatch#head-9799d3ebaa1221875dfdb0a05c4063dc4eb474a1 When can I apply? ----------------- The application period for the Linux kernel project during OPW Round 9 is September 12 to October 31. Most OPW organizations have an application deadline of October 22, however, the Linux kernel application period will be put on temporary hold from October 10 to October 20. Most kernel mentors will be attending conferences (LinuxCon Europe, Linux Plumbers Conf, and Embedded Linux Conference Europe) during that time. During the hold period, no new kernel application patches will be accepted or reviewed, and mentors may not be available on the IRC channel. Therefore, it is important to start sending patches early in the application period. We suggest that you tackle a medium-sized advanced project during that week, rather than preparing to send many small clean up patches after the hold period is finished. Good luck with your application! If you have any questions, mentors will be available via IRC or this mailing list. Do not hesitate to ask questions if you get stuck in the tutorial. Sarah Sharp Linux Kernel OPW Coordinator }}} == Third week of application period == September 29th for round 9: * All mentors should have their projects on the wiki, and be interacting on the opw-kernel mailing list. Ping them every two days until they do so, or give up on them. == Fourth week of application period == October 6th, for round 9: * Email Marian to get all mentors who have a project up on the wiki to log into the [[https://opw.gnome.org/|OPW application tracking system]] * Create OPW tracking spread sheet, tracking everyone who has gotten a kernel patch accepted into staging tree. * Create a mutt filter to filter out all applicants that already have a patch in, so that you can see newcomers. * Example mutt filter: {{{ ~s PATCH !(~(~f "name")) !(~(~f "email")) }}} * Search for who has patches in staging-next by pulling down the tree, and running {{{ git log --pretty=oneline --abbrev-commit --author="name" staging/staging-next --after="Sept 1 2014" | wc }}} * Encourage those people who have patches accepted to fill out an OPW application, see the form email below. * Encourage those who are doing too many simple cleanups to move onto more complex topics (sparse, coccinelle, or small cleanups) * In the tracking spreadsheet, update the patch count once a week or so. Application submission encouragement email: {{{ To: OPW Kernel Applicants List Cc: [all people who have at least one patch in staging-next] Subject: [ANNOUNCE] Please complete your OPW application Greetings, As of [date], the following people have successfully gotten at least one staging driver cleanup patch into Greg's staging-next tree: [list of names, ideally in alphabetical order, but usually by number of patches submitted, whichever is easier to copy-paste from the tracking spreadsheet] If your name is on that list, *PLEASE* fill out your application form at https://opw.gnome.org/ Follow the instructions at https://wiki.gnome.org/OutreachProgramForWomen/#Submit_an_Application Make sure to include answers to the additional Linux-kernel specific application questions, found in the "Application tips" section at http://kernelnewbies.org/OPWApply You will have until [application period deadline] to complete your application for the Linux kernel OPW internships. The OPW application system has rough draft applications from the following people: [List of people who filled out an application] Thank you for getting an initial application in! I hope to see more applications completed by [application deadline]. Small tasks =========== Additionally, the following people have completed at least ten staging driver patches: [list of names] If your name is on that list, you are *highly encouraged* to start working on more complex kernel patches, such as Sparse cleanups, Coccinelle scripts, or small tasks from mentors. Please remember that we will look at the quality, not quantity of patches, and we value applicants that can move onto more advanced topics. The list of small tasks are listed for individual projects under http://kernelnewbies.org/OPWIntro Please make sure to coordinate which small task you are working on by creating a kernelnewbies.org account and modifying this page: http://kernelnewbies.org/OPWTasks A full description of how we evaluate applicants can be found in the "Tips for Applying to be an OPW Kernel intern" section at the end of http://kernelnewbies.org/OPWfirstpatch Sarah Sharp }}} Email to mentors, reminding them to sign up for the OPW application site, and put their notes into the tracking spreadsheet: {{{ Greetings OPW mentors! Please make sure you apply to be a mentor in the official OPW application website: https://opw.gnome.org/ Once you've been marked as a kernel mentor, you will be able to see draft applications. Additionally, we have an applicant tracking spreadsheet at [URL for tracking spreadsheet] Please add a "notes" column for yourself, and add comments about any applicants that show good potential for your project. If you notice any less-than-clueful or applicants that are really not independent, you can note that as well. Some stats: * [X] applicants have gotten at least one patch accepted into staging-next. * [X] applicants have more than ten patches in the staging-next * [X] applicants have more than thirty patches in the staging-next. Please note that the *quality* of the patches are more important than the *quantity* of patches. A full list of the criteria we use to evaluate applicants can be found in the "Tips for Applying to be an OPW Kernel intern" section at the bottom of http://kernelnewbies.org/OPWfirstpatch We will need to meet between Nov 1 and Nov 7 in order to select interns. What time/dates work for people? Please fill out the doodle survey: [survey link] Please encourage those applicants with a lot of patches to take on more advanced patches. Some of the applicants with over 30 patches are sending in simple one or two line patches, and they should be moving on to more advanced patches (Sparse, Coccinelle, or small tasks). People I would like to see move on to advanced tasks: [list] Let me know what date/times work for the selection meeting! Thanks, Sarah Sharp }}} == One week before round closes == For round 9, this is October 21st, when the application period opens again. * Urge applicants to get their applications in through the opw.gnome.org website. * Hassle mentors to get them to sign up for opw.gnome.org * Last minute pleas to potential mentors who don't have their shit together^W^W project on the website. == Day before application deadline == For round 9, this is October 30th: * Update spreadsheet with who has applications submitted. * If someone has more than five patches accepted, and they have been active in the last week, but they don't have an application in, ping them. * Update spreadsheet with the project preferences for interns. See which projects are the most popular, and which may need more candidates to list it. * Double check each application for: * Did they fill out info from both the GNOME OPW application page, and the Application Tips section questions from OPWApply? * Are they clear about time commitments? If they're taking classes next term, are they explicit about the number of hours of classes? If they are interning or working, how many hours will they work? Can they take a leave of absence? (We can't accept people with full-time jobs, and part-time jobs are very hard to do while doing the internship.) * Do they have enough kernel projects listed? If they are applying to the two most popular projects, email them and ask them to add two more alternatives. == After the application deadline == * Update tracking spreadsheet with final patch stats, a link to their patches, and a link to their application * Send an email outlining the selection process, and that people need to send patches to the staging mailing list now that the application period is closed: {{{ To: OPW Kernel Applicants List Cc: [all people who have at least one patch in staging-next and submitted an application] Subject: [ANNOUNCE] OPW kernel application period is now closed The deadline for applying to the OPW project passed on [APPLICATION DEADLINE DATE AND TIME]. In order to be considered for a kernel internship, you will need to have submitted an application through the opw.gnome.org portal, and have gotten a patch accepted into staging-testing. The list of people who meet those two qualifications are: [LIST OF PEOPLE] If you are not on that list and feel you should be, please contact me privately. You can check to see if your patches have been accepted into staging-next by searching here: https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/log/?h=staging-testing Select "author" from the drop down menu, and type in your name (you may need to not use accent marks if you've been sending patches without them.) We will be having a meeting to select interns on [DAY WE PICK INTERNS]. Please stop editing your application by [DAY BEFORE WE PICK INTERNS] 24:00 UTC, so that I can record your project preferences in our tracking spreadsheet. Please be aware that any edits between now and Friday may be missed by mentors who have already reviewed your application. Major editing is discouraged. Applicants will be considered based on the criteria outlined in the "Tips for Applying to be an OPW Kernel intern" section at the end of http://kernelnewbies.org/OPWfirstpatch Only patches applied before [APPLICATION DEADLINE DATE AND TIME] 24:00 UTC will be evaluated during the selection process. If you have been selected as an intern, you will be notified on [DAY INTERNS ARE NOTIFIED]. If you would like to continue participating in the Linux kernel after the application period is over, we encourage you to send cleanup patches to the staging driver list at devel@driverdev.osuosl.org. Make sure to use scripts/get_maintainers.pl to Cc the right driver maintainers on your patches. Do not send patches to the opw-kernel mailing list until the next round opens in [NEXT APPLICATION ROUND MONTH YEAR]. I hope you've all enjoyed the application process, and learned a lot about contributing to the Linux kernel. It's been great fun to see all of you learn, grow, and discover. :) Feel free to contact me privately with any feedback on how we can improve the application process. Sarah Sharp }}} == OPW Internship Announcement Day == After Marina announces the accepted OPW interns at 24:00 UTC, send out an email to the selected Linux kernel interns: {{{ Subject: You've been accepted as an OPW intern! Congratulations, you've been accepted as an OPW Linux kernel intern! [link to OPW wiki page with list of selected interns.] [description of which intern will work with which mentor on what project.] We're really excited about accepting you all as interns. Please email us back to confirm you accept the internship and project. I will be sending out an email with the next steps for accepted interns shortly. Sarah Sharp }}} Once everyone accepts, send a second email: {{{ Subject: Next steps on OPW internships Greetings OPW interns and mentors! Now that all interns have accepted, we should talk about the next steps for the program. Interns don't officially start until [START DATE], but if they wanted to get an early start, they can work that out with their mentors. Interns and mentors are expected to meet at least once a week, either by phone, video chat, or google hangout. If communication isn't working from either side, please email me privately, and we'll sort it out. The OPW program is also likely to have at least one IRC meeting during the internship, to check in with interns and mentors. I have subscribed all interns and mentors to the opw-kernel-interns mailing list. There are past mentors on that list as well. Feel free ask the list for advice, send RFCs, or just generally chat. :) You are welcome to continue to chat with mentors and other interns through the opw-kernel IRC channel. If your mentor and you want patches to be reviewed by a wider audience, you are also welcome to Cc the opw-kernel mailing list (not this private list). Payment details will be sent out by Marina or Karen in the upcoming week, but are also summarized here: [OPW wiki payment schedule link] Mentors will be asked to sign a mentoring agreement shortly. Mentors will be doing a mid-term and final review for their interns, in order make sure they're making good progress before they get their payment. Whew! That's all the bureaucratic stuff for now. Have fun and happy hacking! Sarah Sharp }}} After all the interns have accepted, send individual emails to the candidates that didn't get accepted. Prioritize the really good candidates that didn't get accepted first, and encourage them to apply next round. Some mentors may offer to write them a letter of recommendation, so mention that during the intern selection meeting. Sample rejection email: {{{ Subject: Thank you for your OPW kernel application You may have noticed that the GNOME foundation has announced the accepted OPW interns: [OPW wiki link for accepted interns] [personalized message to the applicant.] [IF THEY SUBMITTED MANY PATCHES:] [NAME], I'm sad to report that you weren't selected this round for a Linux kernel internship. The number of patches you got accepted into the kernel this round was awesome! Unfortunately, the selection process was very difficult due to the popularity of some of your top project choices ([TOP PROJECT CHOICES] in particular). [IF THEY SUBMITTED LESS THAN TEN PATCHES:] [NAME], I'm sad to report that you weren't selected this round for a Linux kernel internship. We really appreciated your patch contributions during the application process, and you should be proud that you now have [NUMBER OF PATCHES] patches accepted into the Linux kernel. [IF WE WANT THEM TO APPLY NEXT ROUND: I really encourage you to apply for the next round, and [TIP FOR NEXT ROUND]. The next round of OPW internship will run from [START DATE TO END DATE], with an application deadline in [APPLICATION DEADLINE MONTH]. There will also be another round in a year.] We hope you enjoyed working with Linux kernel mentors, and that you continue to work with the open source community. Any kernel patches you get accepted in between now and the next round will count in your future OPW application. However, we ask that you not send patches to the opw-kernel mailing list, but instead use the standard Linux kernel mailing lists. The staging mailing list is a good place for people who are new to kernel development, so I encourage you to try sending patches there. If you want to continue to send staging driver cleanup patches, please send them directly to Greg Kroah-Hartman, and Cc the staging drivers mailing list at devel@driverdev.osuosl.org. Also, please Cc any of the driver maintainers that the scripts/get_maintainer.pl tool lists. Although that tool lists the linux-kernel mailing list (LKML), I would not recommend Ccing that list, as it's too high-traffic and you're unlikely to get a response on that list. Another way you can keep up with Linux kernel development is to read the Linux Weekly News (LWN) website: http://lwn.net/ There are also a lot of kernel developers on Google+, feel free to follow some of them from my own circles: https://plus.google.com/stream/circles/paeff3338b3c6977 [IF I PERSONALLY LIKED OR WAS IMPRESSED BY THE APPLICANT, I ADD:] Good luck with your future endeavors in the Linux kernel! I hope to meet you at a Linux conference some day. :) Sarah Sharp Linux Kernel OPW coordinator }}} == Start of internships == Make sure all interns are subscribed to opw-kernel-interns list. Send them the following email explaining how the internship works: {{{ Now that all interns have accepted, we should talk about the next steps for the program. Interns don't officially start until [START DATE], but if they wanted to get an early start, they can work that out with their mentors. Interns and mentors are expected to meet at least once a week, either by phone, video chat, or google hangout. If communication isn't working from either side, please email me privately, and we'll sort it out. I'll be sending out private email once a month to kernel interns and mentors, to check in and make sure everything is running smoothly. The OPW program is also likely to have at least one IRC meeting during the internship, to check in with interns and mentors. I have subscribed all interns and mentors to the opw-kernel-interns mailing list. There are past mentors on that list as well. Feel free ask the list for advice, send RFCs, or just generally chat. :) You are welcome to continue to chat with mentors and other interns through the opw-kernel IRC channel. If your mentor and you want patches to be reviewed by a wider audience, you are also welcome to Cc the opw-kernel mailing list (not this private list). Payment details will be sent out by Marina or Karen in the upcoming week, but are also summarized here: https://wiki.gnome.org/OutreachProgramForWomen/2014/DecemberMarch#Payments_Schedule Your OPW internship includes a $500 travel stipend for you to go to an open source conference related to your internship. Ideally you would present at that conference. In order to use your travel stipend, your mentor will have to approve the conference, and you will need to contact opw-admins at gnome dot org in order to get approval to attend. Please note that OPW cannot provide more travel funding over the $500, so if you need additional funding, you will need to contact the conference organizers. We highly encourage OPW interns to present at either LinuxCon North America (August 17-19 in Seattle, Washington, USA) http://events.linuxfoundation.org/events/linuxcon-north-america or at LinuxCon Europe (Oct 5-7 in Dublin, Ireland) http://events.linuxfoundation.org/events/linuxcon-europe We typically have an OPW panel, where interns present lightning talks that are around 5 minutes each. It's a short, easy way to get recognition for your project, meet Linux kernel developers, network with other open source developers, and even look for a job. As a speaker at LinuxCon, your conference registration fee is waived, and you will only have to pay for airfare (or train fare), hotel, and food. }}} == 3 months before LinuxCon == Poll interns to see which interns or alumni want to go to LinuxCon. Ask who needs additional funding to go, ask them to prepare a cost estimate for going, and tell them to submit that through the [[https://www.linuxfoundation.org/programs/developer/travel/request|LF travel fund request]]. Once all funding requests are in, ping Amanda with a summary of all interns' expenses, see if she can fund them. Sample email: {{{ Would interns from the last Dec-March round and the current May-Aug round like to present at this year's LinuxCon? Linux conferences are a great way to network with the Linux kernel community, and to promote your work and find jobs if you're looking. Conferences are also a great way to learn about the current issues that people are working on, and learn about new tools. If you choose to speak at LinuxCon, your conference fee is waived, but you will have to pay the fee for any co-located events. Anything over your $500 travel stipend will have to be paid out-of-pocket. Of course, you can use that stipend for a different conference if you find a more useful conference, or one that's closer to you or fits your school schedule better. If you're nervous about presenting, don't be worried. :) I'm happy to review slides, coach you through practice talks, and help out any way I can. In the past, we've also had an OPW dinner so that interns can meet their mentors. You might want to talk with your mentor to see if they're planning on attending either LinuxCon. Linux Con North America ----------------------- LinuxCon North America will take place on August 20th to 22nd in Chicago, Illinois, U.S.A. It will be co-located with Cloud Open and the invite-only Linux Kernel Summit. http://events.linuxfoundation.org/events/linuxcon-north-america [TALK ABOUT PLUMBERS CONF, BUT REMIND THEM THAT REGISTRATION IS SEPARATE] LinuxCon is more lecture-style presentations on what people did. Plumbers Conf is focused on highly collaborative sessions where developers get together and solve current issues. Plumbers Conf has several "microconferences" that are focused on a particular subsystem (e.g. real-time, Wayland graphics, etc.). People submit talks to the microconf organizers, but often the discussions free-flow into whatever urgent issue is currently pressing. I find the Plumbers Conf style sessions to be more interesting, because you see what problems developers are actually tackling right now. But LinuxCon is also good for getting more introductory-level talks, or going very deep on a particular subject. There's some good tutorials as well. LinuxCon and Plumbers Conf have a "shared track day" on Wednesday [DATE], and I will push to get the talk scheduled for that day. I highly recommend attending both LinuxCon and Plumbers Conf. http://www.linuxplumbersconf.org/2015/ [TALK ABOUT WHICH INTERNS OR ALUMNI ARE IN NORTH AMERICA, ASK IF THEY WANT TO ATTEND.] Linux Con Europe ---------------- LinuxCon Europe will take place on October 13th to 15th in Düsseldorf, Germany. It will be co-located with CloudOpen, Linux Plumbers Conf (Oct 15 - 17), and Embedded Linux Conference Europe (Oct 13 - 15). http://events.linuxfoundation.org/events/linuxcon-europe [TALK ABOUT WHICH INTERNS OR ALUMNI ARE IN EUROPE, ASK IF THEY WANT TO ATTEND.] If you are interested in presenting, please let me know. Once I have responses back from interns, I will submit one presentation proposal for the OPW panel. Once that is accepted, I will email interns with the speaker registration code, and they will be able to register for free. }}} == 2 months before LinuxCon == Make sure all Indian interns have applied for a visa to LinuxCon Europe. It's easier for them if they have a LF visa request letter (which can be obtained by a link in each conference website). If the LF has said they can pay for the intern, that makes the visa process go faster. However, if it gets too close to the conference date, just go for the unpaid visa process. == 1 month before LinuxCon == Give interns three weeks to work on their presentations. Set a deadline 1 week before you leave for LinuxCon, so that you can review and tweak any presentations. Email to send to interns about what they should present on: {{{ LinuxCon Europe is less than two weeks away, and I'm looking forward to seeing you all there! Our presentation slot is Monday, October, 13 at 4:30pm - 5:20pm. http://lccoelce14.sched.org/event/dfe22cb5dc6d9301add1ceb9c6cbac0e I will need a draft of your presentation slides by end of day, Tuesday, October 7th. Just send me what you have, and I expect there will be some editing involved. I need to have your final slides by Saturday, October 11, so I can compile them into one presentation. Please send slides in both libreoffice presentation and PDF format. Since there's only 50 minutes to present in, and we have seven presenters (eight if you include my introduction), I would like to do lightning-style talks. Please limit your presentations to approximately 5 minutes, and remember that you're likely to talk slower when you're presenting at the conference than when you're practicing. Suggested topics in your talk include: - An overview and technical details of the project you worked on. Assume that the audience knows what the Linux kernel is, has configured and compiled their own kernel, and knows a little bit about kernel development and kernel drivers. However, assume they know nothing (or maybe they have only seen a high-level overview) of the particular subsystem or problem you worked on. Tell them a story about your project, and why it's interesting or will matter to them. - Specific examples of what you worked on, or are still working on. It's perfectly fine to have uncompleted work; you can talk about your goals for finishing your project, or even talk about why it turned out the project wasn't a good idea to complete. - Your experiences within the OPW project. This includes the application period, the internship itself, getting used to kernel development, and so on. Help people see what it's like getting into the kernel for the first time; most kernel developers only see that experience once (for themselves), and other developers don't see it at all. - Your current plans. Where are you going from here? What are you working on right now? Are you pursuing your education? Starting your own business? Taking time off to travel the globe? Are you looking for a job or internship right now? (It's *completely* accepted to include that last point as part of a presentation; don't hesitate to say "please hire me" if you want to.) If you're looking for inspiration, the slides from the first round of OPW interns are here: http://kernelnewbies.org/OPWRound6 If you have any questions, let me know! Sarah Sharp }}} == Internship wrap-up tasks == Mailing list tasks * Move all interns from opw-kernel-interns to opw-kernel-alumni. Send this email notifying them of the change, and make sure to thank the individual interns, so that the current subscribers to the list can welcome the new alumni. {{{ Greetings OPW interns! The [TIME PERIOD] OPW internship period has ended, and we now have [NUMBER OF PAST INTERNS] new OPW kernel alumni: - [INTERN] worked on [PROJECT] with her mentor, [MENTOR] Thank you to all the OPW mentors who helped out in this last round! The OPW kernel internships would not be possible without your guidance and mentoring. As this internship period ends, I'm moving all past interns and mentors from the opw-kernel-interns mailing list to the opw-kernel-alumni mailing list. opw-kernel-alumni is a low-traffic mailing list for past OPW interns to ask for advice, post their successes, or look for jobs. All past OPW mentors are subscribed to this list, so you are welcome to use us as a sounding board. OPW alumni and mentors are encouraged to post internship or job opportunities, conference CFPs, speaking opportunities to this list, or diversity outreach efforts, as long as they are related to Linux or open source. You will also be subscribed by Marina to a general OPW alumni list, opw-alumni@gnome.org. }}} * Move all past mentors from opw-kernel-interns to opw-kernel-alumni. Leave them on opw-kernel-mentors. * Ask past mentors if they want to remain on opw-kernel, to review the next round of patches. Ask if they want to participate as a mentor again. * Send out exit surveys to both interns and mentors [TODO, Sarah to create this] * Reach out to any interns that struggled * Wrap-up blog post explaining successes of last round == On-going tasks == Mailing list tasks * Approve people who apply to the opw-kernel google groups. Approve anyone. * ''Julia and Josh?'' Mentoring * Keeping your eyes open for Linux kernel job opportunities * Passing on CFPs for conferences * Scholarship or grant opportunities * Career coaching (setting up mock interviews, reviewing resumes, etc.) * ''maybe explicitly ask other mentors to do this? Paul might want to help with CFPs? Tie in @CallbackWomen to list somehow?'' Promoting OPW * Blog posts on successes * Longitudinal survey results - once a year, three months after Winter OPW interns have finished their internship * Twitter and Google+ posts * ''Sarah Sharp'' Sponsorship Management * Asking companies in Q1 and Q3 if they will donate in Q2 and Q4 to OPW. * Connecting sponsors to OPW interns who need jobs. * ''Sarah Sharp'' = Wrangling mentors = == Form emails for initial contact with potential mentors == Cold call-email: {{{ Hi , Someone suggested you might enjoy being a mentor for the FOSS Outreach Program for Women (OPW). Maybe you have some [PROJECT] tasks that would be a good three month internship project? The OPW program is open to women (cis and trans), and genderqueer, genderfluid or genderfree individuals. The program runs twice yearly, with a one-month long application period, followed by a three month long internship. http://gnome.org/opw/ For this round, OPW is running a pilot program to expand OPW to support other non-traditional applicants (people of color, people from low income backgrounds, and people who identify as LBGTQ). For this pilot, alumni from the Ascend Project can apply to OPW. http://ascendproject.org/ The next application period starts [DATE] and runs through [DATE]. The internships will run from [DATE] to [DATE]. If you're interested in mentoring, you will need to come up with a project for your intern to work on for three months. Please read the following pages for more information about OPW and mentorship duties: http://kernelnewbies.org/OPWMentor https://wiki.gnome.org/OutreachProgramForWomen/Admin/InternshipTime If you're interested in being an OPW mentor or have any questions about the program, please let me know! Sarah Sharp }}} Indicated they would like to be a mentor at a conference: {{{ Hi , At [CONFERENCE], you said you would be interested in volunteering to be a mentor for the FOSS Outreach Program for Women (OPW). The OPW program is open to women (cis and trans), and genderqueer, genderfluid or genderfree individuals. The program runs twice yearly, with a one-month long application period, followed by a three month long internship. http://gnome.org/opw/ For this round, OPW is running a pilot program to expand OPW to support other non-traditional applicants (people of color, people from low income backgrounds, and people who identify as LBGTQ). For this pilot, alumni from the Ascend Project can apply to OPW. http://ascendproject.org/ The next application period starts September 12 and runs through October 31. The application period will be put on hold from October 10 to 20 for ELCE and Plumbers. The internships will run from December 9, 2014 to March 9, 2015. If you're interested in mentoring, you will need to come up with a project for your intern to work on for three months. Please read the following pages for more information about OPW and mentorship duties: http://kernelnewbies.org/OPWMentor https://wiki.gnome.org/OutreachProgramForWomen/Admin/InternshipTime If you're interested in being an OPW mentor or have any questions about the program, please let me know! Sarah Sharp }}} Past OPW mentor: {{{ Hi , I just wanted to follow up with our conversation at [CONFERENCE]. Have you thought of a good OPW project? The next application period starts [DATE] and runs through [DATE]. The internships will run from [DATE] to [DATE]. I know I sent you the links before, but here's the mentorship time commitment and duties list again: http://gnome.org/opw/ http://kernelnewbies.org/OPWMentor https://wiki.gnome.org/OutreachProgramForWomen/Admin/InternshipTime There are a few changes to the OPW kernel process this time around. For this round, OPW is running a pilot program to expand OPW to support other non-traditional applicants (people of color, people from low income backgrounds, and people who identify as LBGTQ). For this pilot, alumni from the Ascend Project can apply to OPW. http://ascendproject.org/ We're also encouraging people to put up small tasks for their project for people to complete during the application process. I hope that will cause applicants to interact more with mentors, and mentors can get a better sense of whether applicants are suited to their project. If you're interested and come up with a project, please put it up on http://kernelnewbies.org/OPWIntro Sarah Sharp }}} == Round 9 Mentor Wrangling == Contacted with initial email: * Andrew Morton * Matthew Wilcox - NVMe? * Kyle McMartin - talked to Marina at Libre planet in April * Jan Kara - talked to me at kernel summit 2013 In process: * Extended attributes initramfs * ''status: waiting to see if Mimi produces technical docs by Sept 26th'' * Mimi Zohar * will write technical specs, doesn't want to be main mentor * Shuah Khan * Mimi asked at LinuxCon NA to be co-mentor * Said no because three is too many co-mentors and she just took maintainership of kernel testing infrastructure * Kees Cook * interested in being mentor, but scared of time committment * Rik Van Riel - has a two ideas for a MM project, needs to put it up on the wiki - needs to ping Mel Gorman for small tasks Ping next round: * Rusty Russell - will be on vacation Sept 18 to Oct 12, which doesn't align well with OPW application period * Laurent Pinchart - talked to Sarah at LinuxCon NA 2014 - in the middle of moving to Finland, ping for next round * Tejun Heo - cgroups - Sarah cold-emailed to see if he wants to be a mentor - ping next round for project on converting create[_singlethread]_workqueue() to appropriate alloc[_ordered]_workqueue() * Dan Williams (Intel) - Raid acceleration cleanup or storage-related project. * Shuah Khan - kernel testing infrastructure || Mentor || Project || Kernelnewbies account? || Subscribed to google groups || Project on wiki? || Contact info linked? || Interacting with applicants? || subscribed to opw gnome list? || || Josh Tripplet || tinification || Y || Y || Y || Y || || || || Julia Lawall || coccinelle fault finding || Y || Y || Y || Y || Y || || || Nicolas Palix || coccinelle fault finding || Y || Y || Y || Y || || || || Arnd Bergman || 2038 time_t cleanup || Y || Y || Y || || Y || || || Octavian Purdila || IIO cleanup || Y || Y || Y || Y || || || || Daniel Baluta || IIO cleanup || Y || Y || Y || Y || || || || Rik van Riel || Khugepaged swap readahead || Y || Y || Y || Y || || || == During Application Period == * Once a bunch of mentors are confirmed and have their projects up on the wiki, send their emails to be subscribed to opw-list at gnome.org. This mailing list is for potential applicants to ask questions, and for coordinator and mentor announcements. * Direct add any mentors to opw-kernel, opw-kernel-interns, and opw-kernel-alumni. Send these three welcome messages as you subscribe them: {{{ Hi , I'm going to subscribe you to three lists: opw-kernel is for applicants to send patches during the application period, and ask questions. opw-kernel-interns is for accepted interns and mentors only, and will be used once interns are chosen. opw-kernel-mentors is a private list for mentors only. It's used during the intern selection process and in case we need to communicate with all mentors privately. Sarah Sharp }}}