This page outlines the responsibilities of different contributor roles in the Milvus project.
|Contributor||Contributor in the community||Made at least one contribution to the Milvus project||Listed in All contributors|
|Reviewer||Review contributions from other members||History of active contributions and reviews in any of the sub-projects of the Milvus project||
|Maintainer||Approve contributions to be merged||Experienced, active reviewer and contributor to any of the sub-projects of the Milvus project||
|TSC members||Ensure the continuous development of the Milvus project||Demonstrated a high sense of responsibility and an excellent technical judgment for the Milvus project|
The Milvus community welcomes all types of contributions. You can become a Milvus contributor as long as you have made contributions to the Milvus project or community.
Existing members ought to welcome new members, help them with their PR workflow, and direct them to relevant documents and communication channels.
Defined by: All contributors
If you made contributions but not on this list, file an issue to inform us.
Reviewers‘ duty is to review for correctness and quality on contributor's code in a certain part of a sub-project. They should have a profound knowledge about both the codebase and software engineering principles.
reviewers entry in the OWNERS file in any of the repositories owned by the Milvus project
An active contributor for at least 3 months
Review at least 5 PRs
Make over 20 commits to the codebase
Nominated by maintainers or TSC members
Maintainers are supposed to both review and approve code contributions. 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 flag conventions, subtle performance and correctness issues, interactions with other parts of the system, etc.
approvers entry in the OWNERS file in any of the repositories owned by the Milvus project
Main contributor to the codebase
Reviewer of the codebase for at least 3 months
Primary reviewer for at least 10 PRs to the codebase
Nominated by maintainers or TSC members owner
The TSC is elected by the community. The TSC’s work includes:
Ensure continuous development of the Milvus project
Set technical direction and priorities for the community
Nominate and mentor maintainers, reviewers, and contributors to the project
Defined by: https://github.com/orgs/milvus-io/teams/tsc