If you are reading this, you are probably in the same place I was a few weeks ago, staring at the Outreachy website and trying to figure out where to actually start. The program page is helpful, but there is a gap between reading the docs and knowing what to do on a Tuesday afternoon when you are trying to get a contribution in.
This guide covers what I wish I had known earlier.
Before the Application Phase Opens
Most people start thinking about Outreachy only after the application window opens. That is a mistake. By the time the portal is live, applicants who did their homework earlier are already moving faster.
Here is what you should do in the weeks before:
Read the eligibility rules carefully. The Outreachy eligibility requirements are specific about work hours, student status, and residency. Do not assume you qualify. Check the eligibility page before anything else.
Browse the previous round's projects. Outreachy publishes the list of past participating organizations. Go through them. This gives you a realistic picture of what projects show up, what skills are needed, and which communities you could actually contribute to. You will also start recognizing org names when the new round opens.
Set up accounts early. Several contributing communities require accounts that take time to activate. Fedora, for example, uses FAS (Fedora Accounts System). Create it before you need it. Same applies to Matrix, IRC, mailing lists, or anything else a community uses for communication. These are not the kinds of things you want to be troubleshooting the same day you are trying to submit a contribution.
When the Application Phase Opens
The initial application has two parts: the eligibility check and the essay questions. Get the eligibility check done first. If something disqualifies you, you want to know before you spend time on essays.
For the essays, answer honestly. Outreachy mentors read a lot of these. Generic answers about passion for open source are not memorable. Write about what you actually did, what you actually struggled with, and what you actually want to work on.
Once your initial application is approved, you move into the contribution phase. This is where most of the real work happens.
How to Pick a Project
You are allowed to contribute to more than one project. Do not try to contribute to five. Pick one or two that are a realistic fit for your current skills and available time.
When evaluating a project, look at:
- The contribution requirements. Some projects list specific tasks applicants must complete. Others are more open. Know which type you are dealing with before you start.
- Mentor responsiveness. Before committing time to a project, send one message to the mentor or drop a line in the community chat. See how long it takes to get a reply. A mentor who is unresponsive during the application phase will likely be unresponsive during the internship.
- The codebase or documentation state. Clone the repo. Read the README. If you cannot get a development environment running after a reasonable effort and there is no help available, that is a signal worth paying attention to.
Making Your First Contribution
This is where people get stuck. The task feels either too small or too large.
A few things that help:
Read the contribution guide if one exists. Many projects have a CONTRIBUTING.md or equivalent. Read it fully before touching anything. It will tell you how to format commits, whether there is a PR template, and what review turnaround looks like.
Start with what is explicitly listed. If the project has a list of applicant tasks or labeled issues like good-first-issue, start there. This shows the mentor that you can follow instructions, which is a real and valued skill.
Ask before you guess. If you are not sure whether an approach is correct, ask in the community channel before you build it. A short question saves you from spending three hours on something the mentor will ask you to redo.
Record your contribution. In Outreachy, you must log contributions in the application portal. Do this as you go. Do not wait until the last day of the contribution phase and try to reconstruct everything from memory.
Communication Habits That Actually Matter
Open source communities operate mostly in public, async channels. How you communicate there is part of your contribution record, even without a code commit attached to it.
- Ask questions in public channels when possible. If you message a mentor privately with a question that other applicants might have, you are creating a private silo of information. Asking in the public channel also shows engagement.
- Be specific when you ask for help. "It doesn't work" is not a useful bug report. Say what you tried, what you expected, and what actually happened.
- Acknowledge responses. If a mentor reviews your work and leaves feedback, respond, even if just to confirm you saw it and are working on the changes.
The Final Application
The final application is submitted before the contribution phase ends. Do not leave this until the last few hours.
The most important section is the timeline. You will be asked to break down the internship project into weekly tasks. This shows that you understand the scope of the work. If the project proposal describes a vague outcome, ask your mentor to help you make it concrete before you write your timeline.
Write your timeline in enough detail that someone who does not know the project could understand what you plan to do each week. Mentors use this to evaluate whether you have thought seriously about the work.
One Thing That Is Easy to Overlook
Keep a short running log of what you do each day during the contribution phase. It does not need to be formal. Even a few bullet points in a text file is fine. When it comes time to fill out the contribution log in the portal, or write about your experience, this log is invaluable. Memory is not reliable after three weeks of parallel tasks.
That is the guide. If you are currently in the contribution phase and something here contradicts what your specific project requires, go with what your project documentation and mentor say. Every community has its own quirks. But the fundamentals above apply broadly.
Good luck.
Top comments (0)