volcano.sh/apis@v1.8.2/community-membership.md (about)

     1  
     2  # Volcano Community Membership
     3  
     4  **Note :** This document keeps changing based on the status and feedback of Volcano Community.
     5  
     6  This document gives a brief overview of the Volcano community roles with the requirements and responsibilities associated with them.
     7  
     8  | Role | Requirements | Responsibilities | Privileges |
     9  | -----| ---------------- | ------------ | -------|
    10  | [Member](#member) | Sponsor from 2 approvers, active in community, contributed to Volcano | Welcome and guide new contributors | Volcano GitHub organization Member |
    11  | [Approver](#approver) | Sponsor from 2 maintainers, has good experience and knowledge of domain, actively contributed to code and review  | Review and approve contributions from community members | Write access to specific packages in relevant repository |
    12  | [Maintainer](#maintainer) | Sponsor from 2 owners, shown good technical judgement in feature design/development and PR review | Participate in release planning and feature development/maintenance | Top level write access to relevant repository. Name entry in Maintainers file of the repository |
    13  | [Owner](#owner) | Sponsor from 3 owners, helps drive the overall Volcano project | Drive the overall technical roadmap of the project and set priorities of activities in release planning | Volcano GitHub organization Admin access |
    14  
    15  
    16  **Note :** It is mandatory for all Volcano community members to follow Volcano [Code of Conduct](./code_of_conduct.md).
    17  
    18  ## Member
    19  
    20  Members are active participants in the community who contribute by authoring PRs,
    21  reviewing issues/PRs or participate in community discussions on slack/mailing list.
    22  
    23  
    24  ### Requirements
    25  
    26  - Sponsor from 2 approvers
    27  - Enabled [two-factor authentication] on their GitHub account
    28  - Actively contributed to the community. Contributions may include, but are not limited to:
    29      - Authoring PRs
    30      - Reviewing issues/PRs authored by other community members
    31      - Participating in community discussions on slack/mailing list
    32      - Participate in Volcano community meetings
    33  
    34  
    35  ### Responsibilities and privileges
    36  
    37  - Member of the Volcano GitHub organization
    38  - Can be assigned to issues and PRs and community members can also request their review
    39  - Participate in assigned issues and PRs
    40  - Welcome new contributors
    41  - Guide new contributors to relevant docs/files
    42  - Help/Motivate new members in contributing to Volcano
    43  
    44  
    45  ## Approver
    46  
    47  Approvers are active members who have good experience and knowledge of the domain.
    48  They have actively participated in the issue/PR reviews and have identified relevant issues during review.
    49  
    50  
    51  ### Requirements
    52  
    53  - Sponsor from 2 maintainers
    54  - Member for at least 2 months
    55  - Have reviewed good number of PRs
    56  - Have good codebase knowledge
    57  
    58  
    59  ### Responsibilities and Privileges
    60  
    61  - Review code to maintain/improve code quality
    62  - Acknowledge and work on review requests from community members
    63  - May approve code contributions for acceptance related to relevant expertise
    64  - Have 'write access' to specific packages inside a repo, enforced via bot
    65  - Continue to contribute and guide other community members to contribute in Volcano project
    66  
    67  ## Maintainer
    68  
    69  Maintainers are approvers who have shown good technical judgement in feature design/development in the past.
    70  Has overall knowledge of the project and features in the project.
    71  
    72  ### Requirements
    73  
    74  - Sponsor from 2 owners
    75  - Approver for at least 2 months
    76  - Nominated by a project owner
    77  - Good technical judgement in feature design/development
    78  
    79  ### Responsibilities and privileges
    80  
    81  - Participate in release planning
    82  - Maintain project code quality
    83  - Ensure API compatibility with forward/backward versions based on feature graduation criteria
    84  - Analyze and propose new features/enhancements in Volcano project
    85  - Demonstrate sound technical judgement
    86  - Mentor contributors and approvers
    87  - Have top level write access to relevant repository (able click Merge PR button when manual check-in is necessary)
    88  - Name entry in Maintainers file of the repository
    89  - Participate & Drive design/development of multiple features
    90  
    91  ## Owner
    92  
    93  Owners are maintainers who have helped drive the overall project direction.
    94  Has deep understanding of Volcano and related domain and facilitates major agreement in release planning
    95  
    96  ### Requirements
    97  
    98  - Sponsor from 3 owners
    99  - Maintainer for at least 2 months
   100  - Nominated by a project owner
   101  - Not opposed by any project owner
   102  - Helped in driving the overall project
   103  
   104  ### Responsibilities and Privileges
   105  
   106  - Make technical decisions for the overall project
   107  - Drive the overall technical roadmap of the project
   108  - Set priorities of activities in release planning
   109  - Guide and mentor all other community members
   110  - Ensure all community members are following Code of Conduct
   111  - Although given admin access to all repositories, make sure all PRs are properly reviewed and merged
   112  - May get admin access to relevant repository based on requirement
   113  - Participate & Drive design/development of multiple features
   114  
   115  
   116  **Note :** These roles are applicable only for Volcano github organization and repositories. Currently Volcano doesn't have a formal process for review and acceptance into these roles. We will come-up with a process soon.
   117  
   118  
   119  [two-factor authentication]: https://help.github.com/articles/about-two-factor-authentication
   120