Get Involved

You don't need to be a software engineer to contribute. Health professionals, crisis responders, writers, and testers are just as valuable as developers.

Ways to Contribute

Pick the path that fits your skills — all of them matter.

Develop

Write code, fix bugs, build features. Our stack varies by project — Python, JavaScript, and more. All skill levels welcome.

  • Pick up a good first issue label
  • Fix reported bugs
  • Build new features from open issues
  • Improve test coverage
Browse repositories

Document

Good documentation is the difference between a tool people adopt and one they ignore. Clear writing is a high-impact contribution.

  • Improve README files
  • Write installation guides
  • Create user tutorials and how-tos
  • Translate content into other languages
Find doc issues

Test

Try features, find edge cases, and report what breaks. Testing by non-developers is especially valuable — you find usability problems engineers miss.

  • Test new features before release
  • Report bugs with clear reproduction steps
  • Review UI and UX for usability
  • Test on mobile and low-bandwidth connections
Report an issue

Domain Expertise

If you work in healthcare, emergency response, or humanitarian aid — your knowledge is our most valuable resource. We build better tools when domain experts are in the room.

  • Review tools for real-world accuracy
  • Propose new projects based on field gaps
  • Connect us with organizations that could use our tools
  • Validate workflows against actual practice
Start a discussion

Ideate

Have an idea for a tool that doesn't exist yet? Seen a problem in your field that software could help solve? We want to hear it — even (especially) if you can't build it yourself.

  • Open a feature request
  • Propose a new project
  • Share research or case studies
  • Connect problems to potential solutions
Share your idea

Spread the Word

Share our projects with people who could use them. Star repos you find valuable. Tell colleagues in healthcare and crisis management that these tools exist.

  • Star repos you find useful
  • Share with your professional network
  • Write about JigsawFlux on your blog
  • Introduce us to organizations with relevant needs
Visit our GitHub

Making Your First Contribution

New to open source? Here's the path from zero to merged PR.

1

Find a project

Browse our repositories and find one that interests you. Read the README to understand what it does and whether it matches your skills.

2

Find an issue

Look for issues labelled good first issue or help wanted. These are intentionally scoped to be approachable. Comment on the issue to let others know you're picking it up.

3

Fork and clone

Fork the repository to your own GitHub account, then clone it locally. Create a new branch for your change — never commit directly to main.

4

Make your change

Implement the fix or feature. Follow any coding standards mentioned in CONTRIBUTING.md. Run existing tests to make sure nothing is broken.

5

Open a pull request

Push your branch and open a PR against the original repository. Describe what you changed and why. Reference the issue number (e.g. Closes #42). A maintainer will review it within a few days.

Our Community

JigsawFlux is committed to a welcoming, inclusive environment. We work across disciplines — engineers, clinicians, aid workers, researchers — and that diversity is our strength.

All contributors are expected to follow our Code of Conduct: treat others with respect, assume good faith, and focus on the work rather than the person.

Open to All skill levels
Response time Within a few days
License MIT / Apache 2.0