{"id":2014,"date":"2024-04-03T23:23:46","date_gmt":"2024-04-03T23:23:46","guid":{"rendered":"https:\/\/www.aviator.co\/blog\/?p=2014"},"modified":"2025-09-25T11:04:39","modified_gmt":"2025-09-25T11:04:39","slug":"introducing-flexreview-teams-and-slo","status":"publish","type":"post","link":"https:\/\/www.aviator.co\/blog\/introducing-flexreview-teams-and-slo\/","title":{"rendered":"Introducing FlexReview Teams and SLO"},"content":{"rendered":"\n

Code reviews and code ownership are team based concepts. Building an efficient code review culture requires having a strong partnership between the authors and the reviewers. Additionally, to truly improve the code review cycle times, it\u2019s even more important for the individual responses to come quickly<\/a> than it is for the whole process to happen rapidly.<\/p>\n\n\n\n

FlexReview Teams<\/a> is built with those principles in mind. It provides a customizable framework for managing code review rules, assignments, and notifications, allowing teams to establish their own policies and objectives while facilitating inter-team best practices.<\/p>\n\n\n\n

\"flex
FlexReview Teams config<\/figcaption><\/figure>\n\n\n\n

Teams<\/h2>\n\n\n\n

At the core of the system is a Team representation. Each FlexReview Team is 1:1 mapped with a unique GitHub Team<\/a>, and it inherits the configuration from its parent team as specified in GitHub. That means, in a multi-level hierarchy of various engineering teams set up in GitHub, the configurations can be defined at any level, and be trickled down to all children teams.<\/p>\n\n\n\n

Code reviews SLO<\/h2>\n\n\n\n

Service level objective<\/a> (SLO) for code review defines the suggested time it should take the reviewer to respond to a code change. This is NOT<\/strong> the time it takes for a PR to be approved, but rather just getting a response. This helps the team focus on individual response times instead of focusing on the complete cycle times.<\/p>\n\n\n\n

Think of the code review SLO as an agreement between the author and the reviewer for a pull request. With this agreement, the author is incentivized to create smaller PRs that fall within the bounds of the SLO agreement, and reviewers are incentivized to stay on top of the PRs.<\/p>\n\n\n\n

Configuration<\/h2>\n\n\n\n

There are 3 core configurations for each FlexReview Team:<\/p>\n\n\n\n

1. Reviewer assignment<\/h3>\n\n\n\n
\"Review
Review assignment config<\/figcaption><\/figure>\n\n\n\n

FlexReview Teams support 3 different configurations for reviewer assignment:<\/p>\n\n\n\n