dapr
/
community
mirror of https://github.com/dapr/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1 from yaron2/membership-1 

Add community membership
This commit is contained in:
Yaron Schneider 2020-09-02 11:27:29 -07:00 committed by GitHub
parent 75372b23ab 48391c8626
commit 81487a60b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 176 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

176
community-membership.md Normal file
View File

@ -0,0 +1,176 @@
# Community membership
This doc outlines the various responsibilities of contributor roles in
Dapr. The Dapr project is subdivided into subprojects under
(predominantly, but not exclusively) core runtime, CLI, Quickstarts, Docs and language-specific SDKs. Responsibilities for most roles are scoped to these subprojects (repos).
| **Role** | **Responsibilities** | **Requirements** | **Defined by** |
| ---------- | ----------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Member | Active contributor in the community. reviewer of PRs | Sponsored by two approvers or maintainers. multiple contributions to the project. | Dapr GitHub org member. |
| Approver | Approve accepting contributions | Highly experienced and active reviewer + 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 |
*Note: The Technical & Streeting Committee (TSC) referred to in this document is not yet established. The interim members are @msfussell, @sarahnovotny, @yaron2.*
## New contributors
New contributors should be welcomed to the community by existing members, helped
with PR workflow, and directed to relevant documentation and communication
channels.
## Established community members
Established community members are expected to demonstrate their adherence to the
principles in this document, familiarity with project organization, roles,
policies, procedures, conventions, etc., and technical and/or writing ability.
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 Dapr GitHub organization
### 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:
- Authoring or reviewing PRs on GitHub
- Filing or commenting on issues on GitHub
- Contributing to subprojects, or community discussions (e.g. meetings,
chat, etc.)
- [Joined the gitter channel ](https://gitter.im/dapr/community)
- Have read the [contributor
guide](https://github.com/dapr/dapr/blob/master/CONTRIBUTING.md)
- Actively contributing to 1 or more subprojects.
- Sponsored by two approvers or maintainers (sponsors). Note the following requirements for sponsors:
- Sponsors must have close interactions with the prospective member - e.g.
code/design/proposal review, coordinating on issues, etc.
- Sponsors must be approvers or maintainers in at least one CODEOWNERS file
in any repo in the Dapr org.
- [Open an
issue](https://github.com/dapr/community/issues/new?template=membership.md&title=REQUEST%3A%20New%20membership%20for%20%3Cyour-GH-handle%3E)
against the
[Dapr/community](https://github.com/dapr/community) repo
- Ensure your sponsors are `@mentioned` on the issue
- Complete every item on the checklist ([preview the current version of the
template](https://github.com/dapr/community/blob/master/.github/ISSUE_TEMPLATE/membership.md))
- Make sure that the list of contributions included is representative of your
work on the project.
- Have your sponsoring reviewers reply confirmation of sponsorship: `+1`
- Once your sponsors have responded, your request will be reviewed by the
Technical & Steering Committee. Any member of the Technical & Steering Committee can review the requirements and add
Members to the GitHub org.
### Responsibilities and privileges
- Responsive to issues and PRs assigned to them
- Active owner of code they have contributed (unless ownership is explicitly
transferred)
- Code is well tested.
- Tests consistently pass.
- 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`.
Note: members who frequently contribute code are expected to proactively perform
code reviews and work towards becoming an *approver* for the subproject that
they are active in. Acceptance of code contributions requires at least one
approver in addition to the reviews by *members.*
## Approver
Code approvers are able to both review and approve code contributions, as well
as help maintainers triage issues and do project management.
While code review is focused on code quality and correctness, approval is
focused on holistic acceptance of a contribution including: backwards/forwards
compatibility, adhering to API and conventions, performance and
correctness issues, interactions with other subprojects, etc.
Defined by: [CODEOWNERS
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
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.
- Reviewer for or author of at least 5 substantial PRs to the codebase,
with the definition of substantial subject to the maintainer's discretion
(e.g. refactors/adds new functionality rather than one-line pulls).
- Nominated by a maintainer
- With no objections from other maintainers.
- Done through PR to update the `CODEOWNERS`.
### Responsibilities and privileges
The following apply to the part of the codebase for which one would be an
approver in the `CODEOWNERS` files.
- Approver status may be a precondition to accepting large code contributions.
- Demonstrate sound technical judgement (may be asked to step down by a maintainer if they lose confidence of the maintainers).
- Responsible for project quality control via code reviews.
- Focus on holistic acceptance of contribution such as dependencies with other
features, backwards / forwards compatibility, API and conventions, etc.
- Expected to be responsive to review requests (inactivity for more than 1 month may result in suspension until active again)
- Mentor contributors and reviewers.
- May approve code contributions for acceptance.
## Maintainer
Maintainers are the technical authority for a subproject in the Dapr
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
The following apply to the subproject for which one would be an owner.
- Deep understanding of the technical goals and direction of the subproject.
- Deep understanding of the technical domain (specifically the language) of the
subproject.
- Sustained contributions to design and direction by doing all of:
- Authoring and reviewing proposals.
- Initiating, contributing and resolving discussions (emails, GitHub issues,
meetings).
- Identifying subtle or complex issues in designs and implementation PRs.
- Directly contributed to the subproject through implementation and / or review.
- Aligning with the overall project goals, specifications and design principles
defined by the Technical & Steering Committee. Bringing general questions and requests
to the discussions as part of specifications project.
### Responsibilities and privileges
The following apply to the subproject(repos) for which one would be an owner.
- Make and approve technical design decisions for the subproject.
- Set technical direction and priorities for the subproject.
- Define milestones and releases.
- Decides on when PRs are merged to control the release scope.
- Mentor and guide approvers and contributors to the subproject.
- Escalate *approver* and *maintainer* workflow concerns (i.e. responsiveness,
availability, and general contributor community health) to the TC.
- Ensure continued health of subproject:
- Adequate test coverage to confidently release.
- Tests are passing reliably (i.e. not flaky) and are fixed when they fail.
- Ensure a healthy process for discussion and decision making is in place.
- Work with other maintainers to maintain the project's overall health and
success holistically.