First decide whether this round is still actionable for you.
An application calendar that displays only Outreachy’s final deadline can waste weeks of a student’s time. For December 2026, you must distinguish the initial eligibility application, the contribution period and the project-specific final application. As of this guide’s September 16 review, a new applicant cannot skip directly to November.
| Stage | Date | Who should act |
|---|---|---|
| Initial application | Closed August 31, 2026 | New applicants missed this round’s entry stage. |
| Initial decisions / contributions start | October 5, 2026 | Applicants whose initial application is approved. |
| Contribution and final application deadline | November 2, 2026 | Approved applicants who record a contribution and apply to a project. |
| Intern announcement | November 30, 2026 | Applicants awaiting selection. |
| Internship | December 7, 2026–March 8, 2027 | Selected interns; approximately 30 hours weekly. |
| Stipend | US$7,000 total | An internship award, not guaranteed income for making application contributions. |
Outreachy supports people who face underrepresentation, systemic bias or discrimination in their country’s technology industry. Read its eligibility guidance in full rather than treating a short identity list elsewhere as the complete rule.
Sources[1]
Do the school-calendar check before choosing a project.
The rules require students to have 42 consecutive days free of school and exams during the internship. Northern-hemisphere students are directed to May–August, southern-hemisphere students to December–March; near-equator cases need closer review. Taking fewer classes or a personal term off does not automatically change the program’s school-calendar assessment.
Other restrictions include prior Outreachy or GSoC participation and conflicting work or internships. A birthday, graduation date or part-time job can matter, so check your exact circumstances with the organizer instead of reverse-engineering a favorable interpretation from a blog.
Your first private worksheet should therefore contain the institution’s official calendar, exam dates, graduation date and all work commitments. Label documents by the period they cover. A calendar screenshot with no institution or year can make an otherwise straightforward eligibility question hard to resolve. If you missed initial applications, use your time for suitable independent learning or another opportunity; do not submit work under an imagined exception.
Sources[1]
Make a small useful contribution, not a large amount of noise.
For approved applicants, Outreachy’s application instructions recommend choosing one or two projects and contributing consistently. At least one contribution must be recorded on the Outreachy website before submitting a final application for that project. A contribution can be recorded before it is merged; posting a pull request elsewhere is not the same administrative step.
Contribution log fields
Choose a task you can understand and complete carefully. For documentation, follow an installation guide in a clean environment and identify the first missing instruction. For design, clarify the problem and acceptance criteria before producing screens. For code, reproduce the behavior and add a focused test. Ask through the project’s stated channel, and check whether someone already owns the task.
Keep a contribution log with the issue, your action, feedback, next step and public link. The purpose is to avoid losing context or making the mentor reconstruct your history. It is not a scoring system in which twenty cosmetic changes necessarily outweigh one useful fix. Discuss what the project needs and stop work that the maintainer has said is out of scope.
Sources[2]
Let a reviewer see both the change and the reasoning.
Here is an original example of a useful documentation contribution. You follow a setup guide and discover that it assumes a configuration file already exists. Instead of rewriting the entire guide, report the exact command, error and environment, then propose the missing step. Test the revised instructions from a clean start. Include what you tested and what you could not test.
A reviewer may ask you to put the instruction somewhere else or explain why the file should not be copied automatically. Treat that as information about the project, not a verdict on your ability. Respond to each material point, make a narrow revision and say when you are blocked. Do not mark a request resolved merely because you have replied.
Outreachy discourages AI-generated contributions and requires attention to mentor and project rules. Discuss any permitted use, disclose it and understand the result. Do not flood maintainers with generated issues or code you cannot evaluate. A trustworthy small contribution is a better basis for learning than an impressive-looking patch that transfers all verification work to someone else.
Sources[1]
A contribution, a final application and an award are three different things.
Before the project’s final cutoff, check that the contribution record and final application are both complete. Keep your proposed timeline consistent with the required availability. Describe the work you actually attempted and the feedback you received. Do not state that a proposed change shipped if it is still under review.
Contribution time should be something you can afford without assuming selection. A recorded contribution is not an offer and its value should not depend entirely on winning an internship. Choose work that develops a relevant skill and leaves the project better off, while keeping your other practical needs visible.
If you are selected, confirm the internship agreement, payment schedule and communication expectations through the program. If you are not selected, retain a truthful record of accepted contributions and skills learned without calling the application period an Outreachy internship. The distinction is simple and useful: public work can be real evidence even when it does not produce the outcome you hoped for.
Data and worked inputs
Sources[2]