Skip to content

Commit

Permalink
Merge branch 'main' into scorecard-mv
Browse files Browse the repository at this point in the history
Signed-off-by: Jeff Mendoza <[email protected]>
  • Loading branch information
jeffmendoza committed May 29, 2024
2 parents c635d4b + 3dc172e commit cf650ed
Show file tree
Hide file tree
Showing 3 changed files with 44 additions and 36 deletions.
6 changes: 4 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,11 @@ Conduct.](https://openssf.org/community/code-of-conduct/)
* When contributing large features, upate [whats-new.md](whats-new.md)
* All git commits must have [DCO](https://wiki.linuxfoundation.org/dco)

## Contribitor Ladder
## Contributor Ladder

[contributor-ladder.md](contributor-ladder.md)
Allstar follows the [OpenSSF Scorecard contributor ladder](https://github.com/ossf/scorecard/blob/main/CONTRIBUTOR_LADDER.md).

Details on the previous Allstar contributor ladder can be found [here](/contributor-ladder.md).

## Community

Expand Down
23 changes: 23 additions & 0 deletions MAINTAINERS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Maintainers

## `allstar-maintainers`

- @jeffmendoza

## Contributors

- @coheigea
- @danielbankhead
- @five510
- @justaugustus
- @markdboyd
- @naveensrinivasan
- @olivekl
- @yorinasub17

## Emeritus

Former maintainers are listed here.
Thanks for your contributions to Scorecard!

-
51 changes: 17 additions & 34 deletions contributor-ladder.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,29 @@
# Contributor Ladder

| 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. |

## Promotion Process

Please submit a PR to this file with the promotion proposed, and include
evidence of the proposed member meeting the prerequisites. The proposed member
must agree to uphold the expectations of the new level. The existing
Maintainers and Leaders will reach consensus that the prerequites are met and
merge the PR.

### Appeals
***Allstar follows the [OpenSSF Scorecard contributor ladder](https://github.com/ossf/scorecard/blob/main/CONTRIBUTOR_LADDER.md).***

Appeals will be discussed as an agenda item in the [OpenSSF Scorecard project meetings](https://github.com/ossf/scorecard#connect-with-the-scorecard-community).

## Current list

### Contributors
Contributors to Allstar are documented in [MAINTAINERS.md](/MAINTAINERS.md).

- @coheigea
- @danielbankhead
- @five510
- @justaugustus
- @markdboyd
- @naveensrinivasan
- @olivekl
- @yorinasub17
## Changes

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

### Leaders
- *Active* legacy "Contributors" who are not OpenSSF GitHub organization members are now ["Community Members"](https://github.com/ossf/scorecard/blob/main/CONTRIBUTOR_LADDER.md#community-members)
- Community Members are eligible for [OpenSSF GitHub organization](https://github.com/ossf) membership. Outside collaborator access [***should never be granted***](https://github.com/ossf/tac/blob/main/policies/access.md#teams-not-individuals).
- Existing OpenSSF GitHub organization members who are actively reviewing content can be granted [Triagers access](https://github.com/ossf/scorecard/blob/main/CONTRIBUTOR_LADDER.md#triagers)
- Legacy "Maintainers" and "Leaders" are now considered equivalent [access levels][maintainers-access]
- Existing OpenSSF Scorecard maintainers may be granted [Maintainer access][maintainers-access], based on need

- @jeffmendoza
[maintainers-access]: https://github.com/ossf/scorecard/blob/main/CONTRIBUTOR_LADDER.md#maintainers

## Notes
## Legacy contributor ladder

- Only "outside collaborator" access is included above. We would like
to determine OpenSSF GitHub Org membership requirements and add that
at the Maintainer level.
This section exists for historical purposes to detail the legacy Allstar contributor ladder, ***which is no longer in use***.

- Please suggest more recognition items for the Contributor level.
| 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. |

0 comments on commit cf650ed

Please sign in to comment.