Docs: Add a Contributor Ladder defining community roles and progression
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
Add a Contributor Ladder to the PipeCD community documentation that clearly outlines contributor roles, expectations, and paths for progression (e.g., contributor → reviewer → maintainer).
Why is this needed
A contributor ladder helps new and existing contributors understand:
- How to get involved
- What responsibilities come with each role
- How progression and recognition work in the project
This improves transparency, onboarding, and long-term contributor engagement.
References / Inspiration
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the PipeCD community documentation area and review the linked Gateway API, Cilium, OpenFeature, KubeStellar, and OpenSSF references for structure and terminology. Done means the documentation clearly describes contributor roles, expectations, responsibilities, recognition, and progression from contributor to reviewer to maintainer.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100