Project: Sermant (Orchestration & Management / Service Mesh)
File: community-membership.md

Note : This document keeps changing based on the status and feedback of Sermant Community. This document gives a brief overview of the Sermant community roles with the requirements and responsibilities associated with them. | Role | Requirements | Responsibilities | Privileges | | --| - | | -| | | Sponsor from 2 approvers, active in community, multiple contributions to Sermant | Active contributor in the community | Sermant GitHub organization Member | | | Sponsor from 2 maintainers, highly experienced and knowledge of domain, actively contributed to code and review | Review and approve contributions from community members | Write access to specific packagies in relevant repository | | | Sponsor from 2 maintainers, shown good technical judgement in feature design/development and PR review, helps drive the overall Sermant project | Participate in release planning and feature development/maintenance. Drive the overall technical roadmap of the project and set priorities of activities in release planning | Top level write access to relevant repository. Name entry in Maintainers file of the repository. One of the maintainers also has Sermant GitHub organization Admin access | Note : It is mandatory for all Sermant community members to follow Sermant . Members are active participants in the community who contribute by authoring PRs, reviewing issues/PRs or participate in community discussions on slack/mailing list. Note: If you meet the following requirements, welcome to and apply to become a Sermant Organization member! Sponsor from 2 approvers Enabled [two-factor authentication] on their GitHub account Actively contributed to the community. Contributions may include, but are not limited to: Authoring PRs Reviewing issues/PRs authored by other community members Participating in community discussions on slack/mailing list Participate in Sermant community meetings Open an issue against the Sermant/community repo Have your sponsoring reviewers reply confirmation of sponsorship: +1 Once your sponsors have responded, your request will be reviewed by the org owners Member of the Sermant GitHub organization Can be assigned to issues and PRs and community members can also request their review Participate in assigned issues and PRs Welcome new contributors Guide new contributors to relevant docs/files Help/Motivate new members in contributing to Sermant Approvers are active members who have good experience and knowledge of the domain. They have actively participated in the issue/PR reviews and have identified relevant issues during review. Has overall knowledge of the project and features in the

Sponsor from 2 maintainers Member for at least 1 month Have reviewed good number of PRs Have good codebase knowledge Review code to maintain/improve code quality Acknowledge and work on review requests from community members May approve code contributions for acceptance related to relevant expertise Have 'write access' to specific packages inside a repo, enforced via bot Continue to contribute and guide other community members to contribute in Sermant project Maintainers are approvers who have shown good technical judgement in feature design/development and have helped drive the overall project direction in the past. Has deep understanding of Sermant and related domain and facilitates major agreement in release planning Sponsor from 2 maintainers Approver for at least 2 months Good technical judgement in feature design/development Not opposed by any project maintainer Helped in driving the overall project Nominated by a project maintainer Participate in release planning Maintain project code quality Ensure API compatibility with forward/backward versions based on feature graduation criteria Analyze and propose new features/enhancements in Sermant project Demonstrate sound technical judgement Mentor contributors and approvers Have top level write access to relevant repository (able click Merge PR button when manual check-in is necessary) Name entry in Maintainers file of the repository Participate & Drive design/development of multiple features Make technical decisions for the overall project Drive the overall technical roadmap of the project Set priorities of activities in release planning Guide and mentor all other community members Ensure all community members are following Code of Conduct Although given admin access to all repositories, make sure all PRs are properly reviewed and merged May get admin access to relevant repository based on requirement Participate & Drive design/development of multiple features Members are continuously active contributors in the community. A core principle in maintaining a healthy community is encouraging active participation. It is inevitable that people's focuses will change over time and they are not expected to be actively contributing forever. Therefore members with an extended period away from the project with no activity will emeritus or be removed from the Sermant GitHub Organizations and will be required to go through the org membership process again after re-familiarizing themselves with the current state. Inactive members are defined as members of one of the Sermant Organizations with no contributions across any organization within 12 months. This is measured by the Sermant [Insights]. Note: Devstats does not take into account non-code contributions. If a non-code contributing member is accidentally removed this way, they may open an issue to quickly be re-instated. After an extended period away from the project with no activity those members would need to re-familiarize themselves with the current state before being able to contribute effectively.