Expert

The main goal of a Merge Request Coach is to help merge requests from the community get merged into GitLab.

Responsibilities

• Triage merge requests labeled ~"Community contribution" according to the Wider Community Merge Request Triage policy.
• Close merge requests that we don’t want, with a clear explanation on the reasons why, so that people don’t feel discouraged but incentivized that they can make a difference next time.
• Help contributors to get their merge requests to meet the contribution acceptance criteria.
• Act on the merge requests assigned to you on the daily newly created community contribution merge requests triage report.
• Help find and assign merge requests to available reviewers.
• If the contributor is unresponsive or if they are unable to finish it, finish their merge requests. Also, see the closing policy for merge requests.
• Make it easy to contribute to GitLab even for people who are new to Ruby, JavaScript, Golang, etc. or programming entirely. For example, you can add any hints or possible fixes on issues that are open for community contribution.
• Join and actively follow the internal #mr-coaching Slack channel and the external GitLab Community Discord to assist contributors and fellow MR Coaches when they need help or to discuss best practices for collaboration.
  • You can also use the #gitter-contributors-room Slack channel which tunnels all conversations between Gitter and Slack.
• Ensure the content on the MR Coaches handbook pages stays relevant, up-to-date and keeps evolving.
• Participate in the discussion and voting for the release post MVP.

Specialties

We are working on adding the following Merge Request Coach Specialties

A Reliability Expert is expert in the reliability of a service or set of features (from here on, we’ll just call it service for brevity).

Reliability Experts typically help to develop the service (in which they may be Specialists) but with explicit attention to the reliability of the service in production. This is measured by the availability and performance of the service on GitLab.com, its impact on the availability and performance of GitLab.com as a whole, and feedback from customers on the reliability of the service on their on-premises installations.