From 0cd32939c1316f7d2b5b3d9c44092d4ab74aff19 Mon Sep 17 00:00:00 2001 From: Ankit Ram Date: Sat, 26 Sep 2026 17:23:37 +0530 Subject: [PATCH 1/2] docs: add community contributor ladder guidelines (#6548) Add static contributor ladder documentation outlining community contributor tiers (Newcomer, Contributor, Core Contributor), roles, responsibilities, progression criteria, and GitHub organization membership requirements. Closes #6548 Signed-off-by: Ankit Ram --- .../contributor-ladder.md | 99 +++++++++++++++++++ 1 file changed, 99 insertions(+) create mode 100644 docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md diff --git a/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md b/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md new file mode 100644 index 0000000000..2b3a8e4cb9 --- /dev/null +++ b/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md @@ -0,0 +1,99 @@ +--- +title: "Contributor Ladder" +linkTitle: "Contributor Ladder" +weight: 5 +description: > + Community contributor tiers, roles, responsibilities, and progression guidelines for PipeCD. +--- + +The **PipeCD Contributor Ladder** outlines how community members can engage with the project, advance through contributor tiers, and take on greater responsibility within the PipeCD ecosystem. + +Every contribution makes a difference to PipeCD — whether fixing bugs, adding new features, improving documentation, assisting users in Slack, triaging issues, or enhancing test coverage. + +--- + +## Ladder Tiers + +The contributor ladder defines progressive tiers based on engagement, sustained contribution, and community trust: + +| Tier | Prerequisites | Description & Responsibilities | Privileges | +| :--- | :---: | :--- | :--- | +| 🌱 **Newcomer** | 1 merged PR | First-time contributor getting familiar with the codebase, submission workflows, and community norms. | Recognized community member; welcome to join community meetings and CNCF Slack. | +| 🛠️ **Contributor** | 2–4 merged PRs | Regular contributor actively submitting improvements, helping review issues, and participating in discussions. | Can be assigned issues directly; community peer recognition. | +| 🚀 **Core Contributor** | 5+ merged PRs | Experienced, trusted contributor with a sustained track record of quality contributions across the project. | Eligible to apply for `pipe-cd` GitHub organization membership; eligible for subproject reviewer roles. | + +--- + +## Role Details & Responsibilities + +### 🌱 Newcomer + +**Newcomers** are individuals who have taken their first step into contributing to PipeCD by getting their first pull request merged or actively assisting with community discussions. + +- **Requirements:** + - 1 merged pull request to any repository under the [`pipe-cd`](https://github.com/pipe-cd) organization. + - Agreement to uphold the CNCF and PipeCD [Code of Conduct](https://github.com/pipe-cd/pipecd/blob/master/CODE_OF_CONDUCT.md). +- **Responsibilities:** + - Adhere to the contribution guidelines, developer certificate of origin (DCO) sign-off, and PR submission templates. +- **Privileges:** + - Welcomed into the PipeCD contributor community. + - Access to community Slack channels and bi-weekly community meetings. + +--- + +### 🛠️ Contributor + +**Contributors** are community members who demonstrate continued active involvement across the PipeCD codebase, documentation, or tooling. + +- **Requirements:** + - 2 to 4 merged pull requests to [`pipe-cd/pipecd`](https://github.com/pipe-cd/pipecd) or associated subprojects. + - Familiarity with the project's architecture, test suite, and development workflow. +- **Responsibilities:** + - Submit well-tested pull requests that follow project code style and design patterns. + - Participate in issue discussions and help clarify bugs or feature requests. +- **Privileges:** + - Issue assignment upon request. + - Peer review participation on related pull requests. + +--- + +### 🚀 Core Contributor + +**Core Contributors** are established community members who have consistently delivered high-impact contributions and demonstrated dedication to the project's health and roadmap. + +- **Requirements:** + - At least 5 merged pull requests to repositories in the `pipe-cd` organization. + - Demonstrated understanding of PipeCD's core design (Control Plane, Piped agent, plugins). + - Attendance at one or more [PipeCD Community Meetings](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00). +- **Responsibilities:** + - Author and review substantial features, bug fixes, or architecture documentation. + - Help guide and mentor newcomers and contributors in Slack and PR reviews. + - Actively participate in project discussions and roadmap planning. +- **Privileges:** + - Eligible to request official membership in the [`pipe-cd`](https://github.com/pipe-cd) GitHub organization. + - Organization member badge on GitHub. + - Pathway toward becoming an official Reviewer or Subproject Maintainer. + +--- + +## GitHub Organization Membership + +Once a contributor reaches the **Core Contributor** tier, they are encouraged to apply for membership in the `pipe-cd` GitHub organization. + +### How to Apply: +1. Verify that you meet the requirements: + - At least **5 merged PRs** in `pipe-cd` repositories. + - Attendance at least one community meeting. +2. Open an issue or reach out to the project maintainers in the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/) or during a community meeting. +3. Two existing maintainers will sponsor and approve the membership invitation. + +--- + +## Getting Started + +Ready to climb the ladder? Here are great ways to begin: + +- Explore beginner-friendly issues labeled [**good first issue**](https://github.com/pipe-cd/pipecd/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). +- Read the [Documentation Contribution Guide](../contributing-documentation/) to contribute to our guides and tutorials. +- Review the [Contributing Guide](../contributing/) for details on local environment setup, testing, and DCO sign-offs. +- Join the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/) and introduce yourself! From f74b0cfa48d7cba8620d3c7ea689b38c39c29c11 Mon Sep 17 00:00:00 2001 From: Ankit Ram Date: Sat, 26 Sep 2026 23:34:57 +0530 Subject: [PATCH 2/2] docs: address review feedback on contributor ladder wording - Remove misleading claim that Slack/community meeting access is a Newcomer privilege (it is open to the public) - Clarify Contributor privileges: issue assignment means maintainers can officially assign GitHub issues to the contributor, enabling them to take clear ownership of work items - Fix Core Contributor privileges: organization member badge is not automatically granted on reaching 5 PRs; it is granted at maintainer discretion after a successful membership application - Remove mention of 'sponsor' requirement for org membership; per CONTRIBUTING.md no sponsors are required, just a ping in Slack or at a community meeting - Add explicit note that PR counts are minimums and maintainers retain final judgment on tier progression and membership - Align membership requirements section directly with CONTRIBUTING.md Signed-off-by: Ankit Ram --- .../contributor-ladder.md | 54 +++++++++---------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md b/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md index 2b3a8e4cb9..89e6d2da67 100644 --- a/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md +++ b/docs/content/en/docs-dev/contribution-guidelines/contributor-ladder.md @@ -10,17 +10,17 @@ The **PipeCD Contributor Ladder** outlines how community members can engage with Every contribution makes a difference to PipeCD — whether fixing bugs, adding new features, improving documentation, assisting users in Slack, triaging issues, or enhancing test coverage. +> **Note:** PR counts listed for each tier are minimums. Maintainers retain final judgment on tier progression and GitHub organization membership, based on overall contribution quality and community engagement. + --- ## Ladder Tiers -The contributor ladder defines progressive tiers based on engagement, sustained contribution, and community trust: - -| Tier | Prerequisites | Description & Responsibilities | Privileges | -| :--- | :---: | :--- | :--- | -| 🌱 **Newcomer** | 1 merged PR | First-time contributor getting familiar with the codebase, submission workflows, and community norms. | Recognized community member; welcome to join community meetings and CNCF Slack. | -| 🛠️ **Contributor** | 2–4 merged PRs | Regular contributor actively submitting improvements, helping review issues, and participating in discussions. | Can be assigned issues directly; community peer recognition. | -| 🚀 **Core Contributor** | 5+ merged PRs | Experienced, trusted contributor with a sustained track record of quality contributions across the project. | Eligible to apply for `pipe-cd` GitHub organization membership; eligible for subproject reviewer roles. | +| Tier | Merged PRs (minimum) | Description | +| :--- | :---: | :--- | +| 🌱 **Newcomer** | 1 | First-time contributors who have had their first pull request merged. | +| 🛠️ **Contributor** | 2–4 | Community members actively and regularly contributing to the project. | +| 🚀 **Core Contributor** | 5+ | Established contributors with a sustained track record, eligible to apply for `pipe-cd` GitHub organization membership. | --- @@ -28,16 +28,15 @@ The contributor ladder defines progressive tiers based on engagement, sustained ### 🌱 Newcomer -**Newcomers** are individuals who have taken their first step into contributing to PipeCD by getting their first pull request merged or actively assisting with community discussions. +**Newcomers** are individuals who have taken their first step into contributing to PipeCD by getting their first pull request merged. - **Requirements:** - 1 merged pull request to any repository under the [`pipe-cd`](https://github.com/pipe-cd) organization. - Agreement to uphold the CNCF and PipeCD [Code of Conduct](https://github.com/pipe-cd/pipecd/blob/master/CODE_OF_CONDUCT.md). - **Responsibilities:** - - Adhere to the contribution guidelines, developer certificate of origin (DCO) sign-off, and PR submission templates. -- **Privileges:** - - Welcomed into the PipeCD contributor community. - - Access to community Slack channels and bi-weekly community meetings. + - Adhere to the contribution guidelines, [DCO sign-off](https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md), and PR submission templates. +- **Recognition:** + - Listed on the PipeCD contributors roster as a recognized community member. --- @@ -51,9 +50,9 @@ The contributor ladder defines progressive tiers based on engagement, sustained - **Responsibilities:** - Submit well-tested pull requests that follow project code style and design patterns. - Participate in issue discussions and help clarify bugs or feature requests. -- **Privileges:** - - Issue assignment upon request. - - Peer review participation on related pull requests. +- **Recognition:** + - GitHub issues can be directly assigned to you upon request, so you can officially take ownership of work items. + - Peer acknowledgment within the community for sustained contributions. --- @@ -63,29 +62,30 @@ The contributor ladder defines progressive tiers based on engagement, sustained - **Requirements:** - At least 5 merged pull requests to repositories in the `pipe-cd` organization. - - Demonstrated understanding of PipeCD's core design (Control Plane, Piped agent, plugins). - - Attendance at one or more [PipeCD Community Meetings](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00). + - Attended at least one [PipeCD Community Meeting](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00). + - Demonstrated understanding of PipeCD's core design and contribution workflows. - **Responsibilities:** - Author and review substantial features, bug fixes, or architecture documentation. - Help guide and mentor newcomers and contributors in Slack and PR reviews. - Actively participate in project discussions and roadmap planning. -- **Privileges:** - - Eligible to request official membership in the [`pipe-cd`](https://github.com/pipe-cd) GitHub organization. - - Organization member badge on GitHub. - - Pathway toward becoming an official Reviewer or Subproject Maintainer. +- **Recognition:** + - Eligible to apply for `pipe-cd` GitHub organization membership (see below). Membership is granted at maintainer discretion and is not guaranteed solely based on PR count. --- ## GitHub Organization Membership -Once a contributor reaches the **Core Contributor** tier, they are encouraged to apply for membership in the `pipe-cd` GitHub organization. +Once a contributor reaches the **Core Contributor** tier, they are encouraged to apply for membership in the `pipe-cd` GitHub organization. Membership is helpful if you want to contribute over a long period or take responsibility for a feature. + +### Minimum Requirements (per [CONTRIBUTING.md](https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md#join-our-team-on-github)): +1. At least **5 merged PRs** in repositories under the `pipe-cd` organization. +2. Attendance at at least one [PipeCD Community Meeting](https://zoom-lfx.platform.linuxfoundation.org/meeting/96831504919?password=2f60b8ec-5896-40c8-aa1d-d551ab339d00). + +> **Note:** These are minimum requirements. Maintainers will use their judgment to evaluate overall engagement, contribution quality, and community participation before granting membership. ### How to Apply: -1. Verify that you meet the requirements: - - At least **5 merged PRs** in `pipe-cd` repositories. - - Attendance at least one community meeting. -2. Open an issue or reach out to the project maintainers in the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/) or during a community meeting. -3. Two existing maintainers will sponsor and approve the membership invitation. +- Attend a community meeting and introduce yourself, **or** +- Reach out in the `#pipecd` channel on [CNCF Slack](https://slack.cncf.io/). ---