From b2a7e2000e4eaae11d2d0cc4c572a3dc48a68deb Mon Sep 17 00:00:00 2001 From: Will Tsai <28876888+willtsai@users.noreply.github.com> Date: Tue, 20 Jan 2026 12:00:34 -0800 Subject: [PATCH] update community membership guidelines to include Contributor role Signed-off-by: Will Tsai <28876888+willtsai@users.noreply.github.com> --- community-membership.md | 49 ++++++++++++++--------------------------- 1 file changed, 17 insertions(+), 32 deletions(-) diff --git a/community-membership.md b/community-membership.md index c6a9537..992d8ff 100644 --- a/community-membership.md +++ b/community-membership.md @@ -5,32 +5,30 @@ This doc outlines the responsibilities of contributor roles in Radius. The Radiu | **Role** | **Responsibilities** | **Requirements** | **Defined by** | | ---------- | ----------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | +| Contributor | Contribute source code, documentation or blog posts | At least one merged PR in one of the Dapr repositories. | GtiHub contributors listed per repository | Member | Active contributor in the community. Reviewer of PRs | Sponsored by two approvers or maintainers. Multiple contributions to the project. | Radius GitHub org member | | Approver | Approve accepting contributions | Highly experienced and active reviewer and contributor to a subproject. | [CODEOWNERS](https://help.github.com/en/articles/about-code-owners) in GitHub | | Maintainer | Set direction and priorities for a subproject | Demonstrated responsibility and excellent technical judgement for the subproject. | [CODEOWNERS](https://help.github.com/en/articles/about-code-owners), GitHub Team and repo ownership in GitHub | - - -## Member +Role-specific expectations, responsibilities, and requirements are enumerated below. + +### Member Members are continuously active contributors in the community. They can have issues and PRs assigned to them. Members are expected to participate in community discussions and remain active contributors to the community. Defined by: Member of the Radius GitHub organization -### Requirements +#### Requirements - Enabled [two-factor authentication](https://help.github.com/articles/about-two-factor-authentication) on their GitHub account - Have made multiple contributions to the project or community. Contributions may include, but is not limited to: @@ -56,7 +54,7 @@ Defined by: Member of the Radius GitHub organization - Have your sponsoring reviewers reply confirmation of sponsorship: `+1` - Once your sponsors have responded, your request will be reviewed by the Steering & Technical Committee (STC). Any member of the Steering & Technical Committee can review the requirements and add Members to the GitHub org -### Responsibilities and privileges +#### Responsibilities and privileges - Responsive to issues and PRs assigned to them - Active owner of code contributed by them (unless ownership is explicitly @@ -66,10 +64,10 @@ Defined by: Member of the Radius GitHub organization - Addresses bugs or issues discovered after code is accepted - Members are encouraged to review and approve via the GitHub workflow. This review work, while not sufficient to merge a PR, does accrue toward the Member becoming an Approver. Merge approval and final review are performed by an Approver - Members can be assigned to issues and PRs, and people can ask members for reviews with a `/cc @username` - -## Approver + +### Approver Code approvers are able to both review and approve code contributions, as well as help maintainers triage issues and do project management. @@ -82,7 +80,7 @@ workflow](https://help.github.com/en/articles/about-code-owners). Approver status can be scoped to a part of the codebase. For example, critical core components may have higher bar for becoming an approver. -### Requirements +#### Requirements The following apply to the part of the codebase for which one would be an approver in the `CODEOWNERS` files: - Reviewer of the codebase for at least 1 month @@ -93,7 +91,7 @@ The following apply to the part of the codebase for which one would be an approv - Steering committee acts as the final resolution to any escalation - Done through PR to update the `CODEOWNERS` -### Responsibilities and privileges +#### Responsibilities and privileges The following apply to the part of the codebase for which one would be an approver in the `CODEOWNERS` files. @@ -107,14 +105,14 @@ The following apply to the part of the codebase for which one would be an approv - May approve code contributions for acceptance - Inactivity for more than 3 months leads to a removal vote by other maintainers/approvers and not an automatic removal -## Maintainer +### Maintainer Maintainers are the technical authority for a subproject in the Radius org. They *MUST* have demonstrated both good judgement and responsibility towards the health of that subproject. Maintainers *MUST* set technical direction and make or approve design decisions for their subproject - either directly or through delegation of these responsibilities. Defined by: GitHub organization ownership, permissions and entry in `CODEOWNERS` files. -### Requirements +#### Requirements The following apply to the project for which one would be an owner: @@ -126,21 +124,8 @@ The following apply to the project for which one would be an owner: - Initiating, contributing and resolving discussions (e.g. emails, GitHub issues, meetings) - Identifying subtle or complex issues in designs and implementation PRs - Directly contributed to the project through implementation and / or review - - - - -### Responsibilities and privileges +#### Responsibilities and privileges The following apply to the repos for which one would be an owner: