test/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2024-12-01 03:18:29 +08:00
Code Issues Actions 11 Packages Projects Releases Wiki Activity
753c2ff906
milvus/COMMUNITY.md
Jin Hai a57c97ddc3
[skip ci] Update COMMUNITY.md (#1862) 
Signed-off-by: jinhai <hai.jin@zilliz.com>
2020-04-03 11:28:19 +08:00

3.7 KiB
Raw Blame History

Community Roles

TSC Members

The Technical Steering Committee (TSC) functions as the core management team that oversees the Milvus community. The TSC decides the roadmap of the project and makes major decisions related to the community.

TSC members have the following responsibilities:

  • Coordinate the technical direction of the project.
  • Approve project or system proposals.
  • Decide on formal releases of the project's software.
  • Organize and remove sub-projects.
  • Coordinate any marketing, events, or communications regarding the project.

To become a TSC member, a committer must be sponsored by a TSC member and the sponsorship must be approved by 2/3 of all TSC members.

The TSC members are listed below:

Committers

Committers lead project feature discussions and oversee the overall project quality.

Committers have the following responsibilities:

  • Lead feature design discussions and implementation.
  • Ensure the overall project quality and approve PRs.
  • Participate in product release, feature planning, and roadmap design.
  • Have a constructive and friendly attitude in all community interactions.
  • Mentor reviewers and contributors.

To become a committer, a reviewer must have contributed broadly throughout the Milvus project. A reviewer must also be sponsored by a committer and the sponsorship must be approved by the TSC.

The committers are listed below:

Reviewers

Reviewers review new code contributions and ensure the quality of existing code.

Reviewers have the following responsibilities:

  • Participate in feature design discussion and implementation.
  • Ensure the quality of owned code modules.
  • Ensure the technical accuracy of documentation.
  • Quickly respond to issues and PRs and conduct code reviews.

To become a reviewer, a contributor must have provided continued and quality contribution to the Milvus project for at least 6 months and have contributed at least one major component where the contributor has taken an ownership role.

The reviewers are listed below:

Contributors

Contributors can be anyone who has successfully submitted at least one PR to the Milvus project.

The contributors are listed below: