Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What are the responsibilities of the Maintainer role in the Kubernetes community

2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

This article mainly explains "What are the responsibilities of the Maintainer role in the Kubernetes community". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let Xiaobian take you to learn "What is the responsibility of the Maintainer role in Kubernetes Community"!

Community members are divided into member, reviewer, approver, and subproject owner.

Kubernetes/community: community-membership.md has very detailed instructions.

Below we briefly describe the responsibilities and requirements of each role.

member

A member is defined as an active community contributor. To be a member list member, in addition to making more contributions, you need two reviewer nominations.

requirements

GitHub account enables two-factor verification;

Many contributions have been made;

Join the kubernetes developer group on Google forums;

Read the Contributor Handbook;

Active contributors to one or more subprojects;

Nominated by 2 reviewers;

duties and rights

Responsible for resolving issues and handling PR;

Responsible for maintaining their own submitted code;

can accept inspection requests from others;

Self-submitted PR can automatically trigger automated testing without requiring approval;

You can specify PR to start automated testing, or you can turn PR off;

If you submit contributions frequently, you may be recruited as a member, and as a member you can be assigned PR, and your PR submitted by yourself will enjoy the privilege of automatic testing in advance (without requiring approval from others).

reviewer

The reviewer is responsible for reviewing code submitted by members, and the reviewer is usually the author or deep participant of a subproject.

requirements

Conditions for becoming a reviewer:

have been a member for at least 3 months;

As the primary reviewer of PRs, have reviewed at least 5 PRs;

Have reviewed or incorporated at least 20 PRs;

Familiarity with project code;

Nominated by an approver for a project;

Reviewers can be nominated by themselves or by approvers. If you have enough PR for me, the robot can also automatically nominate you.

duties and rights

Sufficient time to handle large code commits;

Responsible for the code quality of the project;

Responsible for PR inspection tasks;

Responsible for testing bugs in this project;

Issue a badge, visible when submitting PR and issue;

approver

Approver is responsible for approving whether code can be incorporated. Approver is usually a senior member of a subproject and an active reviewer.

requirements

At least 3 months as a reviewer;

Have participated in at least 10 PRs as a primary reviewer;

Have reviewed or submitted at least 30 PRs;

Nominated by subproject owner;

duties and rights

Sufficient time is required (to cope with large code contributions);

Guide reviewers and other contributors;

have the right to accept contributors 'code;

Duties and rights subproject owner

The subproject owner is responsible for the development direction of the subproject, the priority ranking of characteristics, etc., usually the core person of the subproject, not only has a high sense of responsibility, but also has sufficient technical sensitivity.

requirements

In-depth understanding of the objectives and direction of the sub-project;

In-depth understanding of sub-project technical areas;

Contribute continuously to sub-projects, including coding, review, discussion, etc.

duties and rights

Initiate or approve technical decisions for a subproject;

Guiding technical direction and project priorities;

Define milestones and release strategies;

Approvers, reviewers and contributors who guide the project;

Ensure the continuous evolution of the project;

Ensure a climate of communication and decision-making;

Responsible for cooperation with surrounding projects;

Maintainer

The Maintainer role was deprecated in 2018 and replaced by owner, i.e. the original Maintainer actually corresponds to the owner of one or more subprojects.

At this point, I believe everyone has a deeper understanding of "what is the responsibility of the Maintainer role in the Kubernetes community." Let's do it in practice! Here is the website, more related content can enter the relevant channels for inquiry, pay attention to us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report