Outreachy: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(158 intermediate revisions by 33 users not shown)
Line 1: Line 1:
Mozilla has participated in the Outreachy program for several years.  The goals of the program are to increase participation from under-represented groups in free and open source software. Participation is open:
<div style="float: right">__TOC__</div>
* internationally to all women (cis and trans), trans men, and genderqueer people
Mozilla has participated in [https://outreachy.org the Outreachy program] since January 2013.  The goal of the program is to increase participation from under-represented groups in free and open source software. It is a project of the Software Freedom Conservancy.
* also open in the U.S. to all Black/African American, Hispanic/Latin@, American Indian, Alaska Native, Native Hawaiian, and Pacific Islander people


We provide a supportive community for beginning to contribute any time throughout the year and offer three month paid contribution opportunities twice a year.
Mozilla hosts approximately 20 participants across two cohorts (summer and winter) each year.  Mozilla employees work 1:1 with participants for three months.  The program expressly invites women (both cis and trans), trans men, and genderqueer people to apply. It also expressly invites applications from residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. Anyone who faces under-representation, systemic bias, or discrimination in the technology industry of their country is invited to apply.                                                                                                                                                                                                                                                                                                          


==Useful links for More Information==
== Current Round ==
* https://wiki.gnome.org/OutreachProgramForWomen
* https://gnome.org/opw/
* [[GNOME OPW Handbook]]
* [http://kernelnewbies.org/OPWMentor Information for mentors, from Linux Kernel project]


==Current Outreachy Program Cohort: Round 12 (May-August 2016)==
[[Outreachy/Round/22|Round 22]] (May-August 2021) is the current round.
===Enhancements to Python testing tool plugin for generation of HTML reports===
* Mentor: [https://mozillians.org/en-US/u/davehunt/ Dave Hunt]
* Participant: [https://mozillians.org/en-US/u/anaribeiro/ Ana Ribero]
* [http://outreachy.anaplusplus.com/ Participant Blog]


The participant will be responsible for developing enhancements to pytest-html - a plugin based on the popular Python testing tool pytest, which generates a HTML report based on test results.
== Participant Application Process ==
First, please review the [https://wiki.gnome.org/Outreachy#Program_Details Outreachy Eligibility and Application Information page] to learn more about eligibility for Outreachy.


The desired enhancements include: gracefully degrading when JavaScript is not available; saving CSS, images, and other resources as additional files rather than embedding in a single file; grouping results by package/module/class; and including test docstrings in the report.
Steps for applicants to Mozilla:
# Confirm your eligibility on the [https://www.outreachy.org/apply/ outreachy site]
# Look at the Mozilla projects available on the Outreachy site, consider your options, and if you have questions communicate with the project mentors. Of course, you are welcome to apply for non-Mozilla projects you find on the site as well!  You can communicate with other applicants, mentors, and coordinators in [https://chat.mozilla.org/#/room/#outreachy:mozilla.org #outreachy on chat.mozilla.org].
# Begin by contributing to the project. Most projects will describe how to make your first contribution.  As you make contributions, record them in the Outreachy site.  [https://codetribute.mozilla.org/ Codetribute] may help you find good tasks to work on.  ''For many applicants, this is the most valuable part of the experience!''
# Once you have made a few contributions, begin to write your application.  Ask the mentors to review the application before you submit it.


Any new enhancements to the plugin must also be accompanied with tests, which will ensure that these new features work in all expected environments, and reduce the chances of regression.
== Participant Expectations ==


===Make Firefox look great on desktop!===
You will be working full-time on your project for three months. You will meet with your mentor(s) frequently and participate in the open-source development process -- writing code, reviewing code, testing, and so on. You will be expected to write a blog entry each week.
*Mentor: [https://mozillians.org/en-US/u/Gijs/ Gijs Kruitbosch]
*Participant: [https://mozillians.org/en-US/u/Rakhi/ Rakhi Sharma]
* [http://rakhisharma.github.io/Verbose-Journal/ Participant Blog]


Firefox for desktop is used by hundreds of millions of people every day. We control what it looks like using CSS, XUL (a markup language that's a bit like HTML), and JavaScript. There's also a small amount of C++ here and there.
== Mentor / Project Applications ==


For this project, the participant will help to address a number of styling problems where Firefox does not currently look its best.
Mentors submit projects that they are willing to mentor. Here's what you need to know:


===Project SmartHome prototyping===
* The participant will be working full-time, spending 40 hours a week on their project for three months.  Participants will work remotely from home. Your project must be something the participant can do remotely and complete within those months.  You will need to meet at least weekly with your participant, and be available for questions, code review, and so on throughout the internship.
* Mentors: [https://mozillians.org/en-US/u/kglazko/ Kate Glazko] and [https://mozillians.org/en-US/u/marcia/ Marcia Knous]
* You will be heavily involved in the selection process for your mentee which will involve interviewing, reviewing code check-ins / bug reports / trial work.
* Participant: [https://mozillians.org/en-US/u/Mermi/ Manel Rahem]
* During the application process, applicants will be expected to make contributions, so make sure you have established a system for new contributors to get involved and have enough good starter tasks for them.
* Participant Blog: https://mermi.github.io
* Speak with your manager to check it’s OK for you to submit a project proposal.  Each participating organization will need to provide budget for the participant costs of $6500.  The Mozilla coordinators can help connect you with that budget.
* To maximize the number of applicants to your project, submit it as early in the process as possible.
* [https://www.outreachy.org/mentor/mentor-faq/ More FAQ's on the Outreachy Site]


The participant will be involved with Project SmartHome, working on assisting active and ongoing prototyping, integrating logging and metrics into SmartHome work with the collaboration of the metrics team, and helping with user research testing analysis and results.
== Help! ==


===Webcompat.com Web Application Engineer===
Questions? Ask:
*Mentor: [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor]
* Mozilla Outreachy Coordinators: [mailto:outreachy-coordinators@mozilla.com outreachy-coordinators@mozilla.com]
*Participant: [https://mozillians.org/en-US/u/venkid/ Deepthi Venkitaramanan]
* Mozilla Slack: #outreachy (staff only)
*[http://venkid.com/portfolio.html#Outreachy Participant Blog]
* [https://chat.mozilla.org/#/room/#outreachy:mozilla.org #outreachy on chat.mozilla.org]


Mozilla's Web Compatibility team builds and maintains a web application called webcompat.com that allows individuals to easily report site compatibility issues - and to allow us to better understand the larger picture of compatibility issues affecting Firefox users on the web.
== Links ==
 
* [https://chat.mozilla.org/#/room/#outreachy:mozilla.org Outreachy on chat.mozilla.org]
In this Outreachy project, the participant will contribute to one or more of the following projects to help us succeed from a few different angles.
* [https://docs.google.com/document/d/1hR_JDDTihKXGK46NnueNpbpfat4PAZ7wiIvgYX47ZpY/edit# Project Proposal Guide] (staff only)
* Design and implement a system that allows site owners and developers to register for notifications (i.e., RSS, E-mail) for issues related to a given domain
* https://www.outreachy.org/ -- main Outreachy site
* Design and build a user interface that allows bug reporters to identify possible duplicate problems
* [http://kernelnewbies.org/OPWMentor Information for mentors, from Linux Kernel project]
* Use cutting edge features like Service Workers to enable offline and sync capabilities between the client and server
* [https://lists.outreachy.org/cgi-bin/mailman/listinfo/announce Outreachy announcement mailing list] (find out about upcoming rounds)
* Migrate webcompat.com front-end to use ES6 modules (likely powered by something like Babel)
 
===Convert Mozmill tests to Marionette===
*Mentor: John Dorlus <jdorlus@mozilla.com>, Silne30 on IRC
*Participant: [https://mozillians.org/en-US/u/bennyjr35/ Benjamin "Benny" Forehand, Jr.]
*Participant Blog: https://www.bennyjr.xyz/blog and https://benjaminfjr.blogspot.com/
 
This project involves reading and writing code in both Python and Javascript.  Mozmill is one of Mozilla’s older automated testing frameworks; tests written in Mozmill are being ported to Marionette, which is an implementation of the Webdriver standard, capable of interacting with both web content and browser UI. 
Applicants should have a strong knowledge of Python and at least some exposure to Javascript.  The starting point (and main focus) for this project will be the work outlined in Bug 1132680; there is other work in the same area that can be done if that bug gets finished early.
 
 
===Realtime Push Notifications for Kinto===
*Mentor: [https://mozillians.org/en-US/u/natim/ Remy Hubscher]
*Participant: [https://mozillians.org/en-US/u/ipsha21/ Ipsha Bhidonia]
*[https://ipsha218.wordpress.com/feed/ Participant Blog]
Kinto is the Mozilla storage solution to backup and sync Firefox Account Users data. It is currently used as a backend for Firefox OS applications and for Firefox and Fennec updates in the Go Faster projects.
https://kinto.readthedocs.org
 
Today a notification system allow us to notify Firefox and Fennec users for them to come and get updates.
 
The participant would extend the notification system to implement realtime updates between devices.
 
* On the server side we are using Pyramid and Python with a bit of AsyncIO
* On the client side this will involve JavaScript and Websocket management.
 
===Test-driven Refactoring of Marionette's Python Test Runner===
* Mentor: [https://mozillians.org/en-US/u/maja_zf/ Maja Frydrychowicz]
* Participant:
[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette Marionette's] Python Test Runner is slated to become the canonical harness for running most new automated tests for Firefox, but it needs to be lovingly cleaned up and stabilized first. We've already started this work and we're excited to have you help us continue. 
 
We want it to be easy and safe for teams around Mozilla to customize the Test Runner for their needs, so we're writing a suite of tests for the Test Runner itself to prevent breaking any existing automation infrastructure -- i.e. we're testing the thing that runs Firefox tests. Part of your role will be to write more of these tests. While writing tests, you will naturally find areas in the Test Runner code that need to be improved or reorganized in order to be testable in the first place. This is what we mean by "test-driven refactoring". Other tasks might include:
* Making the test results more informative and easy to read on [https://treeherder.mozilla.org Treeherder's] log viewer.
* Making the tests more convenient to run locally with mach.
 
 
===Add robust AMI management to the TaskCluster AWS Provisioner===
* Mentor: [https://mozillians.org/en-US/u/dustin/ Dustin J. Mitchell]
TaskCluster (https://tools.taskcluster.net) is a distributed task execution system Mozilla uses to build, test, and release Firefox.  The AWS provisioner is the component responsible for managing the AWS EC2 instances that execute tasks.  The project is to improve its management of AMIs, making them easier to create, deploy, and clean up.
 
===Improving user experience of Firefox Accounts===
* Mentor: [https://mozillians.org/en-US/u/vladikoff/ Vlad Filippov] (vladikoff on IRC)
 
There are several pending initiatives that are focused on improving the user experience of Firefox Sync and [https://accounts.firefox.com Firefox Accounts]. As part of this Outreachy internship project you will be involved in improving user interaction, running experiments, and measuring success of certain features. Your engineering skills will assist in the following:
 
* Developing new application improvements to reduce the number of user errors on password reset, [https://github.com/mozilla/fxa/blob/rfeeley/eye-password-experiment/features/FxA-80-eye-password-experiment/README.md password change], and [https://github.com/mozilla/fxa/blob/feature-mailcheck-part-two/features/proposed/FxA-79-mailcheck-part-2/README.md sign up flows]. This will give you developer experience working with the Firefox Accounts UX team.
* Experimenting with [https://github.com/mozilla/fxa/blob/rfeeley/eye-password-experiment/features/FxA-80-eye-password-experiment/README.md “Show Password” UX]. Determining which design is more effective in terms of speed and popularity.
*Improving the verification rate and speed of new users signing up for Firefox Accounts.
 
===Content Process Management Tool===
* Mentor: [https://mozillians.org/en-US/u/mconley/ Mike Conley]
* Participant:  https://mozillians.org/en-US/u/Rutuja/ Rutuja Surve]
* [ https://rutujasurveblog.wordpress.com/2016/05/17/outreachy-2016-my-first-post/ Participant Blog]
"With multi-process Firefox going out the door in the very near future, we're looking at scaling up and tuning the number of content processes that Firefox starts and uses.
 
Memory usage is something we want to keep an eye on while we do this, so this project is about building a Content Process Management tool that can track real-time memory usage across each process. We might increase the number of uses of the management tool over time, but we'll start with memory management.
 
===Taskcluster tools UI/UX improvements===
 
* Mentor: [https://mozillians.org/en-US/u/wcosta/ Wander Lairson Costa]
* Co-Mentor: [https://mozillians.org/en-US/u/dustin/ Dustin J. Mitchell]
 
[https://docs.taskcluster.net Taskcluster] is the new Mozilla CI that will in future be responsible to run every build and test for Firefox, Firefox TV, rust and other Mozilla projects. We are a small and passionate team engaged to make Taskcluster the best CI ever.
 
===Automation of Taskcluster Documentation===
* Mentor: [https://mozillians.org/en-US/u/jonasfj/ Jonas Finnemann Jensen] and [mailto:bstack@mozilla.com Brian Stack]
Our task execution platform TaskCluster consists of many small services.
We would like a system to which each component can upload its documentation in a reference format markdown for text, JSON for API references, etc. From the uploaded references we would then generate the entire documentation site.
 
By uploading documentation and reference files from the services, we can have it automatically update when we deploy new features.
Services already uploads some formal JSON references, but this needs more structure.
 
Technically speaking:
- A node.js module for uploading a directory of JSON files + a manifest
- A service generating a static documentation site from uploaded documentation.
Useful skills:
- node.js
- HTML/CSS/JS (react.js would be nice to have)
- Some graphical design skills
 
This is not a project about writing documentation, most of it already exists. It needs automatic deployment and structure.
 
===Fixing some papercuts in the Firefox desktop user interface [No longer taking applicants]===
* Mentor: [https://mozillians.org/en-US/u/jaws/ Jared Wein]
Firefox for desktop is used by hundreds of millions of people every day. We control how it works and what it looks like using CSS, XUL (a markup language that's a bit like HTML), and JavaScript. There's also a small amount of C++ here and there.
 
Some of the work will cover:
* Improving entering and exiting of Reader Mode
* Cleaning up the styling of our getting-started tour
* Improving shadows of the dropdowns for the URL and search box
* Increasing legibility of the menubar on Windows 8
* Researching and improving the Windows 10 Start Menu tile for Firefox
* Showing the Windows 10 accent color in the Firefox title bar
 
===Web Platform Test Crime Scene Investigation===
*Mentor: [https://mozillians.org/en-US/u/ehsan/ Ehsan Akhgari]
"We run a lot of automated tests against each revision to Firefox’s code,  and we verify that code changes do not cause tests  to stop passing. One group of tests, called Web Platform Tests, is  shared among all major web browsers, and we have only begun running them  recently. As a result, we imported thousands of tests and marked  some of them as currently failing, and they have languished in that  state. Some of these failures are caused by Firefox not correctly  implementing an edge case, while others may be very important problems  -  as things stand, it's hard to figure out which ones are which. We  need your help cleaning up this mess!
 
 
===Prototype new Firefox features with the Test Pilot team===
* Mentors: [https://mozillians.org/en-US/u/6a68/ Jared Hirsch] (_6a68 on IRC) and [https://mozillians.org/en-US/u/djustice/ Dave Justice] (JSON_voorhees on IRC)
 
The Mozilla Test Pilot team is seeking someone to join a small, enthusiastic team focused around rapidly testing new features in Firefox.  The team's process is built around getting feedback frequently and directly from an active user base which allows rapid iteration of the feature design.
 
In this program, you will participate in a well-documented four step process:
* Lo-Fi Validation: Sketches, ideation, paper prototypes, and user research.
* Prelaunch: Define and build a minimum viable product, establish your testing protocols, and validate the research.
* Active Testing: Launch and test your prototype, collect metrics and feedback, evolve and re-test.
* Sunsetting: Analyze the tests and determine release platforms.
 
As this program is about rapidly evaluating potential new features, the specifics of what the participant will be developing this summer haven't been settled yet--but ideas are floating around security, privacy, tracking protection, and file transfer. Below are some examples of what the team is currently prototyping as of February 2016:
 
* Universal Search: adding recommendations from sources around the internet directly into the Awesome Bar.
* Tab Center: rethinking tab management by moving tabs to the side of the browser and making them easier to search.
* Better 404s: Using the Internet Archive's Wayback Machine to replace 404 pages with an older version of the page.
* Page Shot: Enabling smarter sharing of screenshots by copying DOM content as well.
 
= For Future Applicants =
* Next Outreachy round is Winter 2016-17. Keep in touch by reading here or on gnome.org/outreachy to learn application deadlines.
 
== Application Process ==
Applicants and mentors, please review the [https://wiki.gnome.org/Outreachy#Program_Details Outreachy Eligibility and Application Information page] to learn more about applying for Outreachy.
 
First steps for applicants to Mozilla:
# Set up [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Getting_Started_with_IRC IRC].
# Set up a [https://bugzilla.mozilla.org Bugzilla] account and a [https://mozillians.org Mozillians] profile. Please include your IRC nickname in both of these accounts so mentors can work with you more easily. For example, Eve Smith would set their Bugzilla name to "Eve Smith (:esmith)", where esmith is their IRC nick.
# Please look at the projects below, consider your options, and chat with Mozilla mentors on IRC. You need to make a small contribution to the area you wish to apply for.
#* To chat with Mozilla mentors, join the #outreachy channel on '''irc.mozilla.org'''.
#* To ask general questions about Outreachy or the application process, you can also try #outreachy IRC channel on irc.gnome.org.
 
==Projects to Apply for==
There will be several Mozilla Outreachy projects for Round 13.
Got Questions? Ask:
 
Outreachy Coordinator:
* [https://mozillians.org/en-US/u/lshapiro/ Larissa Shapiro], Sr Program Manager, Diversity and Inclusion
IRC: #outreachy
 
 
=Past Outreachy/OPW internships=
 
{{#subpages:}}
 
== Complete List of Participants ==
 
=== ROUND 11===
 
==== Lauren Conrad ====
 
Participant: [https://mozillians.org/en-US/u/laurenconrad1993/ Lauren Conrad]
 
Based in: Rye Brook, New York USA. (For anyone who doesn't know, that's a suburb right outside New York City!)
 
Mentor: Joni Savage
 
"I am thrilled to be working for such a well known company and to be translating my writing skills into the tech world."
 
Project:  [https://wiki.mozilla.org/Outreachy/2016/December_to_March#SUMO_-_Build_a_tutorial_or_training_tool_for_new_technical_writers SUMO - Build a tutorial or training tool for new technical writers]
 
Project blog: [http://www.laureneconrad.com www.laureneconrad.com]
 
==== Roxana Ilie ====
Participant: [https://mozillians.org/en-US/u/roxana.ilie23/ Roxana Ilie]
 
Based in: Bucharest, Romania
 
Mentor: [https://mozillians.org/en-US/u/pmcmanus/ Patrick McManus]
 
"I am very excited to be joining the Mozilla Outreach Program because after enjoying so much using the browser, I will have the opportunity to give something back and use my knowledge in order to help the community to improve Mozilla Firefox."
 
Project: [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Battery_Friendly_Platform_Networking_Deadline_Scheduler Battery Friendly Platform Networking Deadline Scheduler]
 
==== Richa Rupela ====
 
Participant: Richa Rupela
 
Based in: Bikaner, Rajasthan, India
 
Mentor: [https://mozillians.org/en-US/u/annevk/ Anne van Kesteren]
 
"Super excited to work on Whatwg project, mentored by Anne van Kesteren. Mozilla Outreach program has given me a great opportunity of working with a such a elite community. Looking forward to an awesome winter where I will work on the HTML standards!"
 
Richa's project blog: https://richarupela.wordpress.com/
 
Project: [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Contribute_to_the_HTML_Standard.21 Contribute to the HTML Standard!]
 
==== Shweta Oak ====
Based in: Mumbai, India
 
Mentor: [https://mozillians.org/en-US/u/alexis/ Alexis Metaireau]
 
"I am extremely excited to be a part of an organization that is so instrumental in the development of the open web and get a chance to make contributions that enrich the lives of people."
 
[https://wiki.mozilla.org/Outreachy/2016/December_to_March#Kinto_.E2.80.94_Make_instances_discoverable Project: Kinto — Make instances discoverable]
 
==== Jullie Utsch ====
Participant: [https://mozillians.org/en-US/u/jullieutsch/ Jullie Utsch]
 
Based in: Belo Horizonte - MG Brazil
 
Mentor: [https://mozillians.org/en-US/u/ilana/ Ilana Segall]
 
“What makes me excited about Outreachy: Being part of a great community, sharing with incredible people and taking part in making the tech industry a little more diverse. :)”
 
Project: [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Visual_Design_with_Research_Data_.5Bno_longer_taking_applications.5D Visual Design with Research Data]
 
==== Cynthia Anyango ====
Participant: [https://mozillians.org/en-US/u/acynthiaanyango/ Cynthia Anyango]
Based in: Nairobi , Kenya
 
Mentor: [https://mozillians.org/en-US/u/kthiessen/ Karl Thiessen]
"I am excited to join Mozilla for the outreach program especially the project I am attached to because I get to contribute to open source Mozilla services that make lives better"
 
Project: [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Enumerate_.28and_Dockerize.29_the_tests.21_.28Quality_Assurance Enumerate (and Dockerize) the tests! (Quality Assurance)]
 
==== Nikki Bee ====
Participant: [https://mozillians.org/en-US/u/nikkicubed/ Nikki Bee]
 
Based in: Alberta, Canada
 
Mentor: [https://mozillians.org/en-US/u/jdm/ Josh Matthews]
 
"I'm excited at the chance to learn Rust and contribute to a major FOSS project, especially for an organization that has been as welcoming as Mozilla."
 
Project:  [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Servo:_Complete_implementation_of_Fetch_standard Servo: Complete implementation of Fetch standard]
 
==== My Lê ====
Based in: Paris - France
 
Mentor: [https://mozillians.org/en-US/u/ricardo/ Ricardo Vazquez]
 
"Proud to be part of Mozilla Outreachy Program, sharing knowledge and contributing to the Open Web."
 
Project: [https://wiki.mozilla.org/Outreachy/2016/December_to_March#Open_Source_Designer.2C_Mozilla_Foundation Open Source Designer, Mozilla Foundation]
 
===ROUND 10===
 
https://wiki.gnome.org/Outreachy/2015/MayAugust#Participating_Organizations
 
Thalia Chan (Tchanders), London, UK - Socorro crash statistics front-end development - Adrian Gaudebert
 
Alice Duarte Scarpa (adusca), Rio de Janeiro, Brazil - Integrate the ability to arbitrarily retrigger jobs into functional tools & production quality code - Armen Zambrano Gasparnian
 
Gloria Dwomoh (blossomica), Piraeus, Greece - Air Mozilla web design and development - Peter Bengtsson
 
===ROUND 9===
 
https://wiki.gnome.org/OutreachProgramForWomen/2014/DecemberMarch#Participating_Organizations
 
Lisa Hewus Fresh Portland, OR, USA - Air Mozilla Web Design and Development - Peter Bengtsson
 
Tessy Joseph (tessy), Kerala, India - One and Done - Rebecca Billings
 
Barbara Miller (galgeek), Portland, OR, USA - QA/Automation - Henrik Skupin
 
Adam Okoye (aokoye), Portland, OR, USA - SUMO/Input Web Design and Development - Will Kahn-Greene
 
===ROUND 8===
 
https://wiki.gnome.org/OutreachProgramForWomen/2014/MayAugust#Participating_Organizations
 
Francesca Ciceri (MadameZou), Massa, Italy - Bug wrangling - Liz Henry
 
Joelle Fleurantin (Queeniebee), New York, NY, USA - Maintaining the Gateway: Improving Mozilla Wiki through updating Information Architecture and Theme - Christie Koehler
 
Maja Frydrychowicz (maja_zf), Montreal, Quebec, Canada - Django development for One and Done - Liz Henry
 
Sara Mansouri (sara_mansouri), Saskatoon, Saskatchewan, Canada - Redevelopment of badges.mozilla.org and other contributor gamification infrastructure - Larissa Shapiro
 
===ROUND 7===
 
https://wiki.gnome.org/OutreachProgramForWomen/2013/DecemberMarch#Participating_Organizations
 
Isabelle Carter (ibnc), Springfield, MO, USA - Servo - Lars Bergstrom
 
Jennie Rose Halperin (jennierose), Carrboro, NC, USA - Community building - Larissa Shapiro
 
Jennifer "Nif" Ward (nif), Oberlin, OH, USA - Rust - Tim Chevalier
 
Sabina Brown (binab), Santa Cruz, CA, USA - SUMO (Support.Mozilla.org) community building - Ibai Garcia
 
===ROUND 6===
 
https://wiki.gnome.org/OutreachProgramForWomen/2013/JuneSeptember#Participating_Organizations
 
coordinators: Selena Deckelmann and Liz Henry
 
Gabriela Salvador Thumé (gabithume), São Carlos, São Paulo, Brazil - Socorro - Selena Deckelmann
 
Tiziana Sellitto (tiziana), Salerno, Italy - Bug wrangling - Liz Henry


===ROUND 5===
== Past Outreachy/OPW Rounds ==


https://wiki.gnome.org/OutreachProgramForWomen/2013/JanuaryApril#Participating_Organizations


Lianne Lee (llmelon), Sydney, Australia - Release metrics dashboard - Lukas Blakk
{{#subpages:Outreachy/Round}}

Latest revision as of 20:22, 27 May 2021

Mozilla has participated in the Outreachy program since January 2013. The goal of the program is to increase participation from under-represented groups in free and open source software. It is a project of the Software Freedom Conservancy.

Mozilla hosts approximately 20 participants across two cohorts (summer and winter) each year. Mozilla employees work 1:1 with participants for three months. The program expressly invites women (both cis and trans), trans men, and genderqueer people to apply. It also expressly invites applications from residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. Anyone who faces under-representation, systemic bias, or discrimination in the technology industry of their country is invited to apply.

Current Round

Round 22 (May-August 2021) is the current round.

Participant Application Process

First, please review the Outreachy Eligibility and Application Information page to learn more about eligibility for Outreachy.

Steps for applicants to Mozilla:

  1. Confirm your eligibility on the outreachy site
  2. Look at the Mozilla projects available on the Outreachy site, consider your options, and if you have questions communicate with the project mentors. Of course, you are welcome to apply for non-Mozilla projects you find on the site as well! You can communicate with other applicants, mentors, and coordinators in #outreachy on chat.mozilla.org.
  3. Begin by contributing to the project. Most projects will describe how to make your first contribution. As you make contributions, record them in the Outreachy site. Codetribute may help you find good tasks to work on. For many applicants, this is the most valuable part of the experience!
  4. Once you have made a few contributions, begin to write your application. Ask the mentors to review the application before you submit it.

Participant Expectations

You will be working full-time on your project for three months. You will meet with your mentor(s) frequently and participate in the open-source development process -- writing code, reviewing code, testing, and so on. You will be expected to write a blog entry each week.

Mentor / Project Applications

Mentors submit projects that they are willing to mentor. Here's what you need to know:

  • The participant will be working full-time, spending 40 hours a week on their project for three months. Participants will work remotely from home. Your project must be something the participant can do remotely and complete within those months. You will need to meet at least weekly with your participant, and be available for questions, code review, and so on throughout the internship.
  • You will be heavily involved in the selection process for your mentee which will involve interviewing, reviewing code check-ins / bug reports / trial work.
  • During the application process, applicants will be expected to make contributions, so make sure you have established a system for new contributors to get involved and have enough good starter tasks for them.
  • Speak with your manager to check it’s OK for you to submit a project proposal. Each participating organization will need to provide budget for the participant costs of $6500. The Mozilla coordinators can help connect you with that budget.
  • To maximize the number of applicants to your project, submit it as early in the process as possible.
  • More FAQ's on the Outreachy Site

Help!

Questions? Ask:

Links

Past Outreachy/OPW Rounds

Retrieved from "https://wiki.mozilla.org/index.php?title=Outreachy&oldid=1235831"