Pick a track, understand the codebase, and make a useful contribution to privacy-first AI with less friction.
COMMUNITY
Open source works best when newcomers can find the right repo, understand the expectations, and get feedback quickly.
Developers
learning and shipping
Open tracks
hushhTech and Research
Review loops
feedback and recognition
Issues
for first PRs and deeper work
OPEN SOURCE
You do not need to know the whole Hushh ecosystem on day one. Choose the track that matches what you want to learn, then make one clear contribution.
CONTRIBUTOR PROMISE
We want contributors to understand the why behind the work, not just push code. Good issues, clear PR notes, tests, and respectful review keep the community moving.
GOOD FIRST WORK
Docs fixes, test coverage, UI polish, issue reproduction, and small bug fixes all count when they make the repo easier for the next builder.
PR WRITE-UP
Include the problem, your approach, screenshots for UI changes, test results, and any follow-up work you intentionally left out.
PROJECT TRACKS
Both tracks matter. The difference is whether you want to ship product code or go deeper into research, protocols, and applied AI ideas.
TRACK 1
Best for contributors who want to work on product surfaces, frontend experience, APIs, repo hygiene, testing, performance, and documentation.
You might contribute
TRACK 2
Best for contributors who want to explore consent protocol, agent experiments, product research, and applied AI workflows.
You might contribute
GET STARTED
This is the beginner path. Follow it once and your next contribution will feel much easier.
STEP 1
Start from the GitHub repo, create your fork, and keep your branch focused on one change.
STEP 2
Skim the setup notes, repo structure, and contribution guide before you write code.
STEP 3
Choose a beginner-friendly issue, bug, doc gap, or small improvement you can explain clearly.
STEP 4
Follow the existing style, keep the diff small, and avoid unrelated cleanup in the same PR.
STEP 5
Test the path you touched, look for privacy or security risk, and note what you verified.
STEP 6
Share the problem, your approach, screenshots when useful, and anything reviewers should check.
WHAT WE VALUE
One problem, one solution. Smaller PRs get reviewed faster and are easier to improve.
Match the existing patterns, name things clearly, and leave the next contributor less confused.
hushh is consent-first, so every data flow, permission, and log deserves careful attention.
Cover the behavior you changed and include manual verification notes when UI is involved.
If setup, behavior, or architecture was unclear to you, improve the docs for the next person.
Ask questions, respond to feedback, and keep the discussion focused on making the work better.
SUPPORT & RECOGNITION
Recognition is here to encourage good work, but the main goal is to build useful, understandable, privacy-first open source.
RECOGNITION
COMMUNITY
GROWTH
If you are stuck, ask for context early. A thoughtful question is often the start of a strong contribution.
COMMUNITY
Browse demo recordings and project walkthroughs from Hushh contributors.
View on Google DriveShare short demos, lessons learned, and behind-the-scenes notes so future contributors can follow the path.
Watch on InstagramJOIN US
Pick one track, read the repo notes, and open a focused PR. If you are stuck choosing where to start, reach out.