Contributor Ladder

Contributors to Allstar are documented in MAINTAINERS.md.

Appeals will be discussed as an agenda item in the OpenSSF Scorecard project meetings.

Changes

This section briefly details key differences between the OpenSSF Scorecard contributor ladder and the legacy Allstar contributor ladder.

Active legacy "Contributors" who are not OpenSSF GitHub organization members are now "Community Members"
- Community Members are eligible for OpenSSF GitHub organization membership. Outside collaborator access should never be granted.
Existing OpenSSF GitHub organization members who are actively reviewing content can be granted Triagers access
Legacy "Maintainers" and "Leaders" are now considered equivalent access levels
Existing OpenSSF Scorecard maintainers may be granted Maintainer access, based on need

This section exists for historical purposes to detail the legacy Allstar contributor ladder, which is no longer in use.

Name	Prerequisites: Indicators to look for before promotion	Expectations	Recognition, Access, Effect of access
Contributors	One of: 1. Regular PRs for code/docs. 2. Regular feedback on discussion topics in issues/slack 3. Regular meeting attendance and contribution. For a period of time: 30 days or more.	Continue pre-req.	Added as GitHub Outside Collaborator to repo with read permissions. Tests on PRs run automatically without approval
Maintainers	Regular PRs for code/docs of moderate to substantial impact. Participates in many high-level proposals and discussions.	Available to have PRs assigned to them for review: Will review within 3 business days, otherwise notifies team when unable to review (ooo, etc.) Responds to requests for input/discussion over issues and slack	Added as GitHub Outside Collaborator to repo with write/push access. Approves and merges PRs
Leaders	Consistently drives the project through code, proposals, project direction, leadership, etc.	As a group, responds and makes final decisions through consensus on all large proposals, features, architecture changes, design, documentation of project	Full access and ownership. Creates releases, and finalizes changelog updates, sends project update announcements.