Open Source Contributors : Code Review & QA

This page introduces two paid contribution roles: Code Review and QA testing.

Your eye for quality is worth something. Reviews and QA slots are paid work.

You don't have to write new features to contribute meaningfully. Reviewing code and testing features is as important.

Two Roles

Code Reviewer — You read PRs, check logic, flag issues, and approve or request changes. A first-review trial applies: your first review is evaluated by a maintainer before payout is approved. One-time gate — once passed, you're treated as an established reviewer.

QA Tester — You test features against acceptance criteria, produce a demo video, and report bugs. No prior PRs required.

How to apply for Code Review?

Before applying for Code Review, please ensure you can respond to requests, changes, and pending issues within 48 hours.

To join the reviewer team, reach out in the Telegram group to get approved and added. Please include the following in your message: • Links to previous open-source contributions (PRs, reviews, or relevant projects) • Your availability — how many hours per week you can commit Template you can use: Hi everyone! I'd like to join the Code Reviewer team.

👤 Name: 🔗 Previous open-source contributions: 🕐 Availability (hrs/week):

Description	Code Reviewer	QA Tester	Both
What you do	Review PRs for correctness, security, and maintainability	Test features, produce demo video, write bug report	Review PRs and Test
Reward	20% of the bounty reward	10% of the bounty reward + 50,000 G$ per accepted bug	25% the bounty reward
How to start	Reach out in the Telegram group to get approved and added to the reviewer team	Pick an issue on GitHub	Reach out in the Telegram group to get approved and added to the reviewer team

💡 First-review trial: your first review is evaluated by a maintainer before payout is approved. This is a one-time gate. Once passed, you are treated as an established contributor going forward.