Request for Missy Davies to become a Merge Request Coach
Why you want to become a Merge Request Coach?
I came from the community! The MR Coach was always my first interaction on an MR. I always had a really positive experience where even if someone didn't know how to help immediately, they were extraordinarily happy, grateful, and helpful in finding someone to take over.
How much time you are planning to spend on it?
I could do a few reviews per week! I'm not sure how much time is required, but I would love to give back the time I took (gifted?) from MR coaches in the past.
Which duties you are focusing on (e.g. triage, finish stale MRs)?
I'm happy to focus on what's needed, but I'm most jazzed to:
- "Help contributors to get their merge requests to meet the contribution acceptance criteria."
- "Make it easy to contribute to GitLab even for people who are new to Ruby"
- "Triage merge requests"
Developer checklist
-
Title this MR Request for <Your Name> to become a Merge Request Coach
-
Add "Merge Request Coach" to your "departments" and "expertise" sections in your user file in data/team_members/person/
-
Add at least one project to your "projects" section in your user file -
Consider joining the #mr-coaching
and#gitter-contributors-room
Slack channels -
When this MR is ready, mention your manager and ask them to merge it. -
After this MR is merged, assign to an existing coach who will perform the next checklist. 👇
Coach (with Owner Permissions) checklist
-
After this MR is merged, add to the @gitlab-org/coaches group
/cc @gitlab-org/developer-relations/contributor-success
For gitlab-org/developer-relations/contributor-success/team-task#494 (closed)
Edited by Missy Davies