Free software. Mutual aid. Agents pointed at something useful.
The Andean people have a beautiful term: minga is a community coming together to do work that helps everyone. Roads, crops, schools, clinics, stuff that keeps life going. Its mutual aid.
This is that idea, aimed at free and open source software. Im not selling you a startup pitch. We just want to connect engineers, designers, writers, translators, organizers, students, and curious folks find useful projects and start helping.
Start here
The point is not to become a perfect open source contributor this weekend. The point is to lower the weird activation energy. Read the docs. Find the issue tracker. Figure out the code, or ask ai to figure it out. Leave the project better than you found it.
Use your normal engineering brain, test scaffolding, doc cleanup, and issue triage. boring stuff first builds trust, dont yeet out a subsystem
Hacker guide ->You can still help. Projects need translators, testers, writers, designers, screenshots, reproduction steps, accessibility notes, and onboarding polish. Also if you have agent credits from codex (chatgpt plus) you can still point it at a repo, but maybe find a nerd to review before PR
Non-hacker ->Project directory
Filter by cause, tech, or contribution style. Then use the prompts below to find one small, real thing to do.
For engineers
Don’t start by asking “what heroic thing can I build?” Start by asking what the maintainer already needs.
I'm looking at this FLOSS humanitarian project: [repo URL].
Act like a careful senior engineer onboarding me.
1. Summarize what the project does in plain English.
2. Identify the main languages, frameworks, test commands, and contribution rules.
3. Find 5 issues that look safe for a first contribution.
4. Reject issues that require production access, private context, or vague product decisions.
5. For the best issue, give me a tiny plan: files to inspect, commands to run, risks, and how to ask a good maintainer question.I'm not trying to write a big code change.
Look at this project: [site or repo URL].
Find 10 useful non-code contributions.
Prioritize docs, screenshots, translations, bug reproduction, accessibility, confusing onboarding steps, broken links, and issue triage.
For each one, explain exactly what I can do in under an hour.For non-coders
Open source runs on the boring glue. A clear bug report can save a maintainer an evening. A fixed setup guide can unblock the next ten contributors. A translation can make a tool usable by people who actually need it.
Why FLOSS matters
This is the practical version. Not a sermon. I ain't RMS i just resemble him when i havent shaved.
GNU is a long-running free software project and philosophy. The core idea is that users should be able to run, study, share, and modify the software they rely on.
The GPL is a license that keeps software free by requiring modified versions to preserve the same freedoms. It is one way to stop public-good code from being quietly enclosed.
Free and open source software means people can inspect it, repair it, adapt it, and keep it alive after vendors disappear or budgets collapse.
Mutual aid is people helping each other directly. In software, that can be translation, bug fixes, deployment help, docs, testing, maps, datasets, or just showing up reliably. You dont have to read Kropotkin to give your neighbor some soup.
Agentic coding setup
Codex, Claude Code, and similar tools are great at reducing friction. They are not maintainers, clinicians, disaster responders, or accountability.
Ask the agent to summarize architecture, contribution rules, tests, and safe entry points. Make it cite files.
One issue. One branch. One failing test. One fix. Avoid giant “AI refactors” unless maintainers ask for them.
Run tests. Read diffs. Check licenses. Remove generated nonsense. Humanitarian software deserves boring correctness.
Good PRs explain why, how tested, screenshots if relevant, and what you intentionally did not change.
About this list
Projects change. Some repos are more active than others. Some need code. Some need docs. Some need governance, money, translators, or patient issue triage. Check the project’s own contribution rules before charging in with a huge PR.
Directory descriptions are based on each project’s own public docs/sites where possible. Links go straight to the project or repo so people can verify before contributing.