feat: Contributor Ladder

[adambkaplan]

Changes

Document a contributor ladder for Shipwright, which serves the following purpose:

• Clarify the roles and responsibilities of community members.
• Identify levels of leadership within the community.
• Provide guidance and procedures for adding new maintainers and other roles that grant permissions for project behaviors/functions.
• Map project roles to security roles in GitHub.

This ladder was inspired by several contributor ladder documents in the CNCF, such as the CNCF Glossary project [1] and the OpenFeature project [2].

[1] https://glossary.cncf.io/contributor-ladder/
[2] https://openfeature.dev/community/contributor_ladder/

Assisted-by: Cursor
Generated-by: Cursor

Fixes #244

/kind feature

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Document contributor ladder

[ayushsatyam146]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[SaschaSchwarze0]

I see that you now also changed the permissions. Would not an approver also only need Write permission ? The difference to Contributor would be to be listed as approver in the OWNERS files. Maintainer would then have Maintain permission. Or, do you have use cases in mind where an approver would require maintain permissions ?

[adambkaplan]

I see that you now also changed the permissions. Would not an approver also only need Write permission ?

Taking a harder look at this, you are right that I should revert the defaults. Write permission is sufficient for an Approver across the board. Maintain is a middle ground between Write and Admin that covers a few admin tasks that we don't really need right now.

Also, Contributor should have the default role be Triage, since Write permission grants permission to create and edit releases. Unfortunately those with Triage permission can't manage GitHub action workflows - we simply need more Approvers to handle this!

[SaschaSchwarze0]

Unfortunately those with Triage permission can't manage GitHub action workflows - we simply need more Approvers to handle this!

Or a different perspective: if our tests would be fully free of flaky failures, we would not have that problem. However, that's complicated with all the external dependencies our tests have. Tekton and Knative are not better on that front.

[SaschaSchwarze0]

/approve

[sayan-biswas]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0, sayan-biswas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [SaschaSchwarze0]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[adambkaplan]

I am considering @sayan-biswas 's "/approve" the equivalent of "/lgtm", and will merge.