> For the complete documentation index, see [llms.txt](https://docs.gooddollar.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gooddollar.org/for-developers/contributing/open-source-contributors.md).

# Open Source Contributors

Human contributors and reviewers turn AI-generated bounty PRs into production-ready changes. You do not need to write the first draft. You need to own the final quality. \
How the Workflow is structured:

#### Every bounty follows the same path:

```
Bounty posted → AI opens PR → Contributor fixes AI code → Reviewer checks → QA tests → Maintainer sign-off → Merge & payout
```

| Stage               | Who                   | Responsibility                                                  |
| ------------------- | --------------------- | --------------------------------------------------------------- |
| AI solution         | AI                    | Opens the initial PR                                            |
| Contribution        | Contributor           | Takes the AI's code, fixes issues, and gets it ready for review |
| Review              | Reviewer              | Validates logic, correctness, and codebase fit                  |
| QA                  | QA contributor        | Tests real behavior and files structured bug reports            |
| Maintainer sign-off | GoodDollar maintainer | Approves the final merge                                        |

{% hint style="info" %}
For Basic and Common bounties, one person often handles both review and QA. For Rare and higher tiers, these roles are usually split.
{% endhint %}

***

### The Roles

#### Contributor

You take the AI-generated PR and make it production-ready. You run the branch locally, validate the implementation against the issue requirements, and fix anything blocking approval — not just comment on it.

Typical checks include: logic and correctness, security and edge cases, tests, style, and codebase consistency.

→ [Read the full Contributor  guide](/for-developers/contributing/open-source-contributors/contributor-role.md)

#### Reviewer

You review the Contributor's corrected version. You validate that the fixes are sound, nothing was missed, and the PR is ready for QA.

#### Becoming a  Reviewer

* Have prior code review or open-source experience
* Message the [`GoodBounties`](https://t.me/gooddollarbounties/4115) Telegram group to request access
* Share links to past open-source work and your weekly availability

Use this template to request access:

```
Hi everyone! I'd like to join the Contributor + Reviewer pool.

Name:
Previous open-source contributions:
Availability (hours/week):
```

Access is granted manually within 24–48 hours. Once approved, you are added to the pool and can receive assignments. Reviewers are expected to respond within 48 hours to requests, changes, and follow-ups.

> Your first review is evaluated by a maintainer before payout is approved. This is a one-time check — after that, accepted work follows the normal flow.

→ [Read the full Code Review guide](/for-developers/contributing/open-source-contributors/human-reviewer-role.md)

#### QA Contributor

You test the approved changes in a real environment. You document what you tested, what passed, and what failed. If you find bugs, you file structured reports with evidence.

Typical checks include: acceptance criteria from the issue, runtime behavior and regressions, UI behavior on real devices or browsers.

### Join as a QA Contributor

* Pick up an open QA bounty 
* Test the PR in a local or preview environment
* Submit a structured QA report as a comment on the PR

Once approved, you join the contributor pool for QA assignments. Assignments can be delegated to another approved contributor when needed.

→[ Read the full QA Process guide](/for-developers/contributing/open-source-contributors/qa-role.md)

***

### What Counts as Accepted Work

Reviews and QA reports only count when they are substantive.

* **Contributor/ Reviewer:** You ran the branch locally, made fixes or validated the implementation, and left clear findings
* **QA:** Your report is reproducible, scoped to the PR changes, and backed by evidence

Rubber-stamp approvals and vague reports are rejected and do not qualify for payout.

→ [See Payments for Contributions, Review and QA](/for-developers/contributing/open-source-contributors/payments-for-reviews-contributors-and-qa.md)

{% hint style="info" %}
Your first review is evaluated by a maintainer before payout is approved.

This is a one-time check. After that, accepted reviews follow the normal flow.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gooddollar.org/for-developers/contributing/open-source-contributors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.