Open Source After Hacktoberfest: How to Keep Contributing from Mexico
October is over and open source goes on. A practical route to pick a project, make your first contribution well and keep the pace from Mexico.

To keep contributing to open source after Hacktoberfest, pick a project you already use, look for an issue labeled "good first issue", read its contribution guide and send a small, well-explained change. Then do it again in the same project, week after week.
October is the month when the most people try open source. The challenge is November. This guide is for anyone who built something at a Fest, opened their first pull request or just got curious, and wants to keep going from Mexico.
Key takeaways
- You do not need to contribute code: documentation, translation, design and triaging issues count too.
- Before contributing, check three things: license, CONTRIBUTING file and recent activity.
- For a big change, open an issue first and ask.
- Your own hackathon project can be open source too: publish it with a license and a clear README.
What changed in Hacktoberfest 2026?
Hacktoberfest 2026 stopped being a four-pull-request challenge and became an event you take part in by building, focused on open models, open source agents and open tooling. It was stewarded by Major League Hacking and DEV, with DigitalOcean as presenting partner, and according to the organizers there were more than 500 in-person Fests in more than 70 countries and territories (hacktoberfest.com, read 17 Nov 2026).
In Mexico City, 16 teams built with open source AI in two days. What teams built at Hacktoberfest México 2026 lists the projects and their repos. The change matters for November: if you built something in October instead of opening pull requests, you already have something you can publish and maintain.
Do you need to code to contribute?
No. The open source guide GitHub publishes says it directly: "A common misconception about contributing to open source is that you need to contribute code", and adds that the non-code parts of a project are often the most neglected (Open Source Guides).
Contributions that count just as much:
- Documentation: fix steps that no longer work, add an example, clarify a README.
- Translation: many projects have no Spanish documentation. It is a real gap that someone in Mexico can fill.
- Triaging issues: reproduce a bug, ask for the missing detail, close duplicates.
- Design: icons, screenshots, a clearer landing page.
- Answering questions in the forum, on Discord or in the project's issues.
Where do you find a project?
The best project to start with is one you already use, because you understand the problem and will notice what is missing. GitHub recommends exactly that, plus four routes (GitHub Docs):
- The
good first issueandhelp wantedlabels. Maintainers put them on tasks meant for newcomers. - Topics. At
github.com/topics/<topic>you find projects by area, for example agents, MCP or language models. - Trending. The day's popular repositories.
- Explore. If you already have activity on GitHub, it suggests projects based on what you have done.
If you are into AI agents, a good place is the Model Context Protocol ecosystem, an open standard with SDKs and reference servers on GitHub. What is MCP explains how it works.
What should you check before your first contribution?
Before writing a line, check three things about the project (Open Source Guides):
- License. If the project has no license, it is not open source.
- CONTRIBUTING file. It tells you how they want changes: templates, tests, style. Read all of it.
- Activity. Look at recent commits and whether issues and pull requests get answers. A project with no activity in months will probably not review your change.
And one rule that saves frustration: for a big change, open an issue first and ask. Pull requests are for small fixes or for work you already agreed with the maintainers.
How do you make a good first pull request?
A good first pull request is small, solves one thing and explains why.
- One thing per pull request. One bug, one documentation page, one translation.
- Link the issue you are solving and describe how you tested the change.
- Follow the project's style, even if you would do it differently.
- Respond to review without taking it personally. Being asked for changes is the normal way of working.
- Do not send AI-written changes without reviewing them. If you use an assistant, understand and test every line before asking someone else to review it.
What about your hackathon project?
Your hackathon project can be open source too. Several Hacktoberfest México 2026 teams published their repos, among them Bench-Engine, which measures how much energy open models use (repo), and DocAPILab, which turns API documentation into local sandboxes (repo).
So that yours can receive contributions:
- Add a license (MIT or Apache 2.0 are common).
- Write a README with what it does, how to run it and a screenshot.
- Open two or three issues with what is missing and label them
good first issue. - Add a short CONTRIBUTING file on how to propose changes.
How to keep the pace
The pace holds with little: one small contribution a week to the same project. By week four you know the code, the maintainers recognize your name and more interesting tasks start coming your way.
If you would rather build with others than alone, hackathons and meetups are the shortcut; if you have never been to one, start with what is a hackathon. To hear about Mobil3's next calls in Mexico, join our subscription list.
Sources
Frequently asked questions
- Can I contribute to open source without coding?
- Yes. GitHub's open source guide says it is a common misconception that you need to contribute code; documentation, translation, design, triaging issues and answering questions are contributions too.
- Where do I find beginner issues?
- Look for the good first issue and help wanted labels on GitHub, browse github.com/topics and start with software you already use.
- What should I check before my first pull request?
- That the project has a license, a CONTRIBUTING file and recent activity in commits, issues and pull requests.
- Did Hacktoberfest 2026 count pull requests?
- Not as before. In 2026 Hacktoberfest stopped being a pull request challenge and became an event you take part in by building, with more than 500 in-person Fests.