Skip to content

CONTRIBUTOR_LADDER.md

Latest commit

 

History

History
55 lines (35 loc) · 1.76 KB

CONTRIBUTOR_LADDER.md

File metadata and controls

55 lines (35 loc) · 1.76 KB
Raw

Contributor Ladder

A clear path from first PR to maintainer. Roles are earned by sustained, quality contribution — not tenure.

Rungs

Contributor

Anyone who opens a PR. To get merged:

  • Pick an issue (start with good-first-issue).
  • Follow CONTRIBUTING.md: one issue per PR, conventional commits, tests + lint + typecheck green.
  • Keep PRs scoped and reviewable.

Triager

Trusted to label, deduplicate, and route incoming issues.

  • Criteria: ~5 merged PRs, demonstrated good judgment in issue discussion.
  • Gains: triage label permissions; named in the contributors table.

Reviewer

Trusted to review and approve others' PRs in specific areas.

  • Criteria: ~15 merged PRs, consistent high-signal reviews, deep familiarity with at least one module (e.g. lib/stellar/*, lib/reputation/*, UI).
  • Gains: review/approve rights; listed in CODEOWNERS for their area (when adopted).

Maintainer

Trusted with merge rights and release responsibility.

  • Criteria: sustained reviewer track record, ownership of a subsystem, and the trust of existing maintainers.
  • Gains: merge rights, release tagging, roadmap input.

How promotion works

Any maintainer may nominate; promotion is by maintainer consensus, recorded in a GitHub Discussion. Roles can lapse with inactivity and be re-earned.

Recognition

Every merged contributor is added to the README contributors table and credited in release notes. Contributors merged during OSS week are named in the grant resubmission document.

Related