agones.dev/agones@v1.53.0/docs/governance/community_membership.md (about)

     1  # Community Membership
     2  
     3  This document outlines the responsibilities of contributor roles in Agones.
     4  
     5  This is based on the [Kubernetes Community Membership](https://github.com/kubernetes/community/blob/master/community-membership.md).
     6  
     7  There are currently two roles for this project, but that may grow in the future.
     8  
     9  | Role         | Responsibilities                 | Requirements                                                       | Defined by                                                              |
    10  |--------------|----------------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------------|
    11  | Collaborator | Can have tickets assigned        | Have one PR merged                                                 | Read access to the Agones repository                                    |
    12  | Releaser     | Create Agones releases           | Sponsored by 2 approvers                                           | Commit access to the Agones repository                                  |
    13  | Approver     | Review and approve contributions | Sponsored by 2 approvers and multiple contributions to the project | Commit access to the Agones repository and [OWNERS] file approver entry |
    14  
    15  
    16  ## New contributors
    17  
    18  New contributors should be welcomed to the community by existing members,
    19  helped with PR workflow, and directed to relevant documentation and
    20  communication channels.
    21  
    22  ## Established community members
    23  
    24  Established community members are expected to demonstrate their adherence to the
    25  principles in this document, familiarity with project organization, roles,
    26  policies, procedures, conventions, etc., and technical and/or writing ability.
    27  Role-specific expectations, responsibilities, and requirements are enumerated
    28  below.
    29  
    30  ## Collaborator
    31  
    32  For regular contributors that wish to have issues assigned to them, we have the collaborator role.
    33  
    34  To become a collaborator, create an issue using the 
    35  [become a repo collaborator issue template](https://github.com/googleforgames/agones/issues/new?assignees=thisisnotapril&labels=area%2Fcommunity&projects=&template=become-a-repo-collaborator.md&title=Collaborator+Request)
    36  and we will review it as a team.
    37  
    38  **Defined by:** Read access to the Agones repository.
    39  
    40  ### Requirements
    41  
    42  - Have at least one merged Pull Request.
    43  - Have reviewed the [contribution guidelines](https://github.com/googleforgames/agones/blob/main/CONTRIBUTING.md)
    44  - Have enabled [2FA on my GitHub account](https://github.com/settings/security)
    45  - Have joined the [Agones Slack workspace](https://join.slack.com/t/agones/shared_invite/zt-2mg1j7ddw-0QYA9IAvFFRKw51ZBK6mkQ)
    46  
    47  ## Releaser
    48  
    49  Releasers are engineers that are able to commit to the Agones repository with
    50  the express purpose of publishing Agones releases. They are **not** approvers
    51  and as such are not expected to perform code reviews or merge PRs. Using their
    52  commit privileges above and beyond creating releases is grounds for revoking
    53  commit access and being demoted from being a releaser.
    54  
    55  **Defined by:** Commit access to the Agones repository.
    56  
    57  ### Requirements
    58  
    59  - Enabled [two-factor authentication](https://help.github.com/articles/about-two-factor-authentication)
    60    on their GitHub account
    61  - Work at Google
    62      - This is due to some steps in the [release process](release_process.md) that require Google internal processes
    63  - Have read the [contributor guide](../../CONTRIBUTING.md)
    64  - Sponsored by 2 approvers. **Note the following requirements for sponsors**:
    65      - Unlike for the Approver role, sponsors should both be from Google
    66  - **[Open an issue](./templates/membership.md) against the Agones repo**
    67     - Ensure your sponsors are @mentioned on the issue
    68     - Label the issue with the `meta` tag
    69     - Complete every item on the checklist ([preview the current version of the template](./templates/membership.md))
    70     - There is no need to include any contributions to the Agones project
    71  - Have your sponsoring approvers reply confirmation of sponsorship: `+1`
    72  
    73  ### Responsibilities and privileges
    74  
    75  - Responsible for creating Agones releases
    76  - Granted commit access to Agones repo
    77  
    78  ## Approver
    79  
    80  Code approvers are able to both review and approve code contributions.  While
    81  code review is focused on code quality and correctness, approval is focused on
    82  holistic acceptance of a contribution including: backwards / forwards
    83  compatibility, adhering to API and flag conventions, subtle performance and
    84  correctness issues, interactions with other parts of the system, etc.
    85  
    86  **Defined by:** Commit access to the Agones repository and [OWNERS] file approver entry.
    87  
    88  **Note:** Acceptance of code contributions requires at least one approver.
    89  
    90  ### Requirements
    91  
    92  - Enabled [two-factor authentication](https://help.github.com/articles/about-two-factor-authentication)
    93    on their GitHub account
    94  - Have made multiple contributions to Agones.  Contribution must include:
    95      - Authored at least 3 PRs on GitHub
    96      - Provided reviews on at least 4 PRs they did not author
    97      - Filing or commenting on issues on GitHub
    98  - Have read the [contributor guide](../../CONTRIBUTING.md)
    99  - Sponsored by 2 approvers. **Note the following requirements for sponsors**:
   100      - Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating
   101        on issues, etc.
   102      - Sponsors must be from multiple companies to demonstrate integration across community.
   103  - **[Open an issue](./templates/membership.md) against the Agones repo**
   104     - Ensure your sponsors are @mentioned on the issue
   105     - Label the issue with the `meta` tag
   106     - Complete every item on the checklist ([preview the current version of the template](./templates/membership.md))
   107     - Make sure that the list of contributions included is representative of your work on the project
   108  - Have your sponsoring approvers reply confirmation of sponsorship: `+1`
   109  
   110  ### Responsibilities and privileges
   111  
   112  - Responsible for project quality control via code reviews
   113    - Focus on code quality and correctness, including testing and factoring
   114    - May also review for more holistic issues, but not a requirement
   115  - Expected to be responsive to review requests in a timely manner
   116  - Assigned PRs to review related based on expertise
   117  - Granted commit access to Agones repo
   118  
   119  [OWNERS]: https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md
   120