> 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/contributor-growth-path.md).

# Contributor Growth Path

You can contribute in three ways: build, review or test. Contributors and Reviewers who do consistently good work get invited to the **Trusted OS Contributors** group.

```mermaid
flowchart LR
    C["Contributor<br>Open to all"] -->|"5 accepted, low rework"| T["Trusted OS Contributors<br>Invite only"]
    R["Reviewer<br>Apply with prior work"] -->|"3 accepted, consistent quality"| T
    Q["QA<br>Open to all"]
```

| Track           | What you do                                                | How to join                                                                                        |
| --------------- | ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **Contributor** | Pick up a bounty, fix the AI's code, hand it to a Reviewer | Open to anyone. Start on Basic or Common.                                                          |
| **Reviewer**    | Review PRs for correctness, security and quality           | Share past review work from any codebase in the `goodbuilders` Telegram. Start on Basic or Common. |
| **QA**          | Test the changes, submit a structured report               | Open to anyone                                                                                     |

### Trusted OS Contributors

Contributors with 5 accepted contributions and a low rework rate, and Reviewers with 3 accepted reviews of consistent quality, can be invited by the GoodDollar team.

Members see Rare, Mythic and Legendary bounties before they open to everyone, and get offered time-sensitive bounties directly. We'll share how this works in the `goodbuilders` channel.

### Picking up bounties

New contributors start on Basic or Common. After that, you can take bounties up to one tier above the highest tier you've completed. New Reviewers also start on Basic and Common, and can review Rare and above after 3 accepted reviews.

If several people claim the same bounty, we pick based on track record for that kind of work. Newer contributors still get picked when their early work shows promise.

Don't open a PR until you're assigned. PRs opened before assignment are closed, and you won't be assigned to that bounty.

{% hint style="info" %}
Smart contract and funds work only goes to a vetted group within the Trusted OS Contributors, chosen by the GoodDollar team. Experience on app-level bounties doesn't count toward it.
{% endhint %}

#### If things stall

* No update on a bounty for 3 days: you'll get a notice. If you don't reply within 36 hours, it's reassigned.
* Reviewers should start within 3 days of a PR being ready and re-review within 48 hours of being tagged. The same notice and 36-hour window applies.
* Payment happens on merge. If your bounty is reassigned and the next person builds on your commits, the team splits the contributor share based on how much of the merged work each of you did.

### Rules

* You can hold different roles on different bounties, for example Contributor on one and Reviewer on another.
* On a single bounty, you hold one role only. The one exception is Reviewer + QA, and only when a bounty posts them as one combined role.
* You can join any track in any order.

***

### Ready to Start?

→ See the [Contibutor Role ](/for-developers/contributing/open-source-contributors/contributor-role.md) to learn the basics of contributing to Gooddollar

> → Browse open bounties on the [Bounties Board](https://github.com/orgs/GoodDollar/projects)

→ See the [Reviewer Role](/for-developers/contributing/open-source-contributors/human-reviewer-role.md) to understand what a good review looks like&#x20;

→ See the [QA Role](/for-developers/contributing/open-source-contributors/qa-role.md) to understand what a good QA report looks like&#x20;