Introducing Reviewer Roulette, an easy way to find a GitLabber for your Merge Request.

Title: Introducing Reviewer Roulette, an easy way to find a GitLabber for your Merge Request.

Summary: As GitLab continues to grow at a rapid pace, it can be difficult to figure out who's who, especially when you need to find the right person to review your Merge Requests. I started Reviewer Roulette in the spirit of our "Do it yourself" Collaboration value, to try and help engineers (and soon, the entire company!)

Keywords, themes: Collaboration, merge requests

Outline:

• Introduction
  • Idea came up in Frontend weekly call
    • Tim: Everyone is a reviewer
    • Microservice from Luke Bennett shut down
    • Could this be useful for others, not just FE team?
• Core value -> Collaboration -> Do it yourself Our collaboration value is about helping each other when we have questions, need critique, or need help. No need to brainstorm, wait for consensus, or do with two what you can do yourself.
  • Team is keen on contributing!
• Originally intended for engineering, but it can help the entire company out. (https://gitlab.com/dennistang/reviewer-roulette/issues/12)
  • Can be useful for coffee chats, especially during the onboarding process (10 calls)
• Brief technical overview
  • Slack command
  • Express/Node application
  • Simple, "boring" solution, not so much about the tech, more about being enabled to create something that will benefit yourself as well as the company.
• Next steps
  • More features! (https://gitlab.com/dennistang/reviewer-roulette/issues)
  • Employ GitLab CI/CD (future post)
  • Move to FE GCP cluster
  • Open to public as official Slack command (?)
• Conclusion
  • Contribute! (https://gitlab.com/dennistang/reviewer-roulette/)

Screenshots:

Notes: Linked to @leipert's post about next steps for Reviewer Roulette and the hackathon that he and I will do next week to learn how to use GitLab for CI/CD.