Welcome! This guide walks you through how to claim an issue, what to expect, and how payments/grants work for RemitX contributors.
- Claiming an Issue
- Expected Turnaround
- How Payment & Grants Work
- Development Setup
- Opening a Pull Request
- Code Style
- Need Help?
- Browse open issues at github.com/Northgate-Systems/RemitX/issues.
- Check the labels — look for
good-first-issue,bounty:free, orhelp-wantedto find contributor-friendly tasks. - Comment on the issue to express interest before starting work:
I'd like to work on this. Estimated completion: <date> - Wait for acknowledgment from a maintainer before investing significant time on large issues.
- One issue at a time — please don't claim multiple issues simultaneously until you have a merged PR.
Tip: Issues tagged
good-first-issueare specifically scoped for new contributors. They come with clear acceptance criteria and focused scope.
| Issue Type | Expected Turnaround |
|---|---|
| Documentation | 2–5 days |
| Bug Fix (minor) | 3–7 days |
| Feature (scoped) | 5–14 days |
| Feature (large) | 14–30 days |
- Communicate early if you need more time. Drop a comment on the issue — maintainers appreciate transparency over silence.
- Issues with no activity for 14 days after claiming may be reopened for other contributors.
RemitX uses a GrantFox-style contribution model:
- No monetary reward, but your work is credited in the repo and
CONTRIBUTORS.md. - Great for portfolio, learning, and OSS reputation.
- Accepted via standard pull request review.
- Bounty amount is listed in the issue title and description (e.g.,
[$50] Fix X). - Claim your work by commenting
/claimon the issue when your PR is ready for review. - Payment is released after the PR is merged and verified by a maintainer.
- Payment method will be coordinated via the contact in the issue or via the GrantFox platform linked in the issue.
- If no payment platform is linked, contact the maintainer directly via the issue or email listed in the README.
Important: Never send payment details (wallet addresses, bank info) in public comments. Maintainers will reach out privately.
# 1. Fork and clone the repo
git clone https://github.com/<your-username>/RemitX.git
cd RemitX
# 2. Install dependencies
npm install
# 3. Copy environment variables
cp .env.example .env.local
# Fill in your Supabase and other credentials
# 4. Run the development server
npm run dev
# App is available at http://localhost:3000- Node.js 18+
- npm 9+
- A Supabase project (free tier works fine for local dev)
- Optional: A Stellar testnet account for payment flow testing
- Create a branch from
mainwith a descriptive name:git checkout -b docs/contributor-onboarding-checklist git checkout -b fix/auth-redirect-loop git checkout -b feat/rate-display-component
- Make your changes and commit with a clear message:
git commit -m "docs: add contributor onboarding checklist" git commit -m "fix: correct auth redirect on logout"
- Push and open a PR targeting the
mainbranch ofNorthgate-Systems/RemitX. - Fill in the PR description — link the issue with
Closes #<issue-number>. - Respond to review comments promptly. Two rounds of feedback is the norm.
- TypeScript — all new code must be typed. Avoid
any. - Prettier — run
npm run formatbefore committing. - ESLint — run
npm run lintand fix all errors before opening a PR. - Component structure — follow existing patterns in
src/appandsrc/components. - Comments — explain why, not what. Code should be self-documenting where possible.
- Open a discussion on the GitHub Discussions tab.
- Comment on the issue you're working on — maintainers monitor all open issues.
- Check
FOUNDATION.mdfor a full breakdown of what's been built and what's stubbed out for contributors.
We appreciate every contribution, big or small. Thank you for helping build RemitX! 🚀