-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: update the docs of community membership
- Loading branch information
Showing
2 changed files
with
20 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,28 @@ | ||
# KusionStack Community Roles | ||
|
||
**Note**: This document is a work in progress. | ||
|
||
This document describes the set of roles individuals may have within the KusionStack community. | ||
|
||
## User | ||
## Member | ||
|
||
A ***user*** is someone who uses KusionStack. They contribute to KusionStack projects by providing feedback to developers in the form of bug reports and feature suggestions. Users participate in the KusionStack community by helping other users. | ||
A ***member*** is someone who uses KusionStack. They contribute to KusionStack projects by providing feedback to developers in the form of bug reports and feature suggestions. Users participate in the KusionStack community by helping other users. | ||
|
||
## Contributor | ||
|
||
A ***contributor*** is a user who contributes to the project in the form of code or documentation. They take extra steps to participate in a project, are active in the community, participate in discussions, and provide patches, documentation, suggestions, and criticism. | ||
|
||
## Approver | ||
|
||
An ***approver*** has the ability to merge code into the KusionStack project, who needs to be an active contributor and responsible for major features. | ||
|
||
## Maintainer | ||
|
||
A Maintainer has the ability to merge code into the KusionStack project. Maintainers are active Contributors and participants in the projects. In order to become a Maintainer, you must be nominated and approved by the established Maintainers. Maintainers have write access to the KusionStack repos on GitHub. | ||
A ***maintainer*** is typically in a relatively small group of decision makers, who needs to have a deep understanding of the technical goals and directions. In order to become a maintainer, you must be nominated and approved by the established maintainers. Maintainers have write access to the KusionStack repos on GitHub. | ||
|
||
| Role | Responsibilities | Requirements | | ||
| ---- | ---------------- | ------------ | | ||
| Member | Use KusionStack projects and provide feedback | Use KusionStack projects and participate in the community | | ||
| Contributor | Active participation in the community | Submitted 1 coding PR or 3 doc PRs and sponsored by 2 approvers | | ||
| Approver | Review and approve code and doc contributions | Submitted 10 coding PRs, reviewed 20 `feature`/`bug` labelled PRs, and sponsored by 2 maintainers without objections from other maintainers | | ||
| Maintainer | Make and set technical design decisions and directions | Sponsored by the majority of maintainers (2/3) | |