<commit_before>---
title: "Google quarterly objectives"
permalink: google-okrs.html
hide_sidebar: true
hide_navtoggle: true
toc: false
---

Google plans work per-quarter, using the OKR (Objective/Key-Result) framework.

# Q4 2021

## O: Gerrit users' data and code are well protected and secure

### KR: Resolve data protection/security work in flight from Q3

A data migration has cleaned all traces of personal data (name, email) in review
metadata.

## O: Increase system stability and reduce latency of critical user journeys

### KR: Migrate to Caffeine for all caches

This is now possbile since we moved off of the old diff cache.

### KR: Investigate reasons for slow pushes, fix if possible

We want Git pushes where users currently bypass Gerrit to go through Gerrit as
well. We suspect that performance (pushes being slow) is the main reason for
bypassing. If so, we want to root cause slowness and fix it if possible.

## O: Improve Gerrit customer satisfaction from X% to Y%

### KR: Roll out composable submit requirements

Use them fully on gerrit-review.googlesource.com,
android-review.googlesource.com and chromium-review.googlesource.com.

### KR: Multi-change review: Implement MVP

Provide a page for reviewing multiple changes ("topics"), providing among others
batch actions and maybe diffs across projects/changes.

# Q3 2021

## O: Gerrit users' data and code are well protected and secure
<commit_msg>Publish publicly relevant Google OKRs for Q1 2022. <commit_after>---
title: "Google quarterly objectives"
permalink: google-okrs.html
hide_sidebar: true
hide_navtoggle: true
toc: false
---

Google plans work per-quarter, using the OKR (Objective/Key-Result) framework.

# Q1 2022

## O: Increase system stability and reduce latency of critical user journeys

### KR: Remove per-user state (drafts, stars) from the change index,
    improving write latencies


### KR: Speed up median diff rendering latency for views with many files

Use multiple fidelity modes and webworkers to speed up "expand all
diffs" and "large file with many diffs" use cases.

## O: Improve Gerrit customer satisfaction from X% to Y%

### KR: Roll out composable submit requirements

Use them fully on gerrit-review.googlesource.com,
android-review.googlesource.com and chromium-review.googlesource.com.

### KR: Multi-change review: Prototype and validate a new experience
    for managing and reviewing multiple, grouped changes

### KR: Reduce P50 code review start latency

Design browser-based push notifications to reduce review latency. Let
reviewers suggest rather than make edits, leading to less lost
approvals.

### KR: Addressing top Gerrit pain points

Fix JGit and CGit merge discrepancies.


# Q4 2021

## O: Gerrit users' data and code are well protected and secure

### KR: Resolve data protection/security work in flight from Q3

A data migration has cleaned all traces of personal data (name, email) in review
metadata.

## O: Increase system stability and reduce latency of critical user journeys

### KR: Migrate to Caffeine for all caches

This is now possbile since we moved off of the old diff cache.

### KR: Investigate reasons for slow pushes, fix if possible

We want Git pushes where users currently bypass Gerrit to go through Gerrit as
well. We suspect that performance (pushes being slow) is the main reason for
bypassing. If so, we want to root cause slowness and fix it if possible.

## O: Improve Gerrit customer satisfaction from X% to Y%

### KR: Roll out composable submit requirements

Use them fully on gerrit-review.googlesource.com,
android-review.googlesource.com and chromium-review.googlesource.com.

### KR: Multi-change review: Implement MVP

Provide a page for reviewing multiple changes ("topics"), providing among others
batch actions and maybe diffs across projects/changes.

## O: Reduce toil, increase developer velocity, and improve developer happiness

### KR: Migrate 33% of remaining frontend components to Lit, remove
     all of Polymer, and get rid of or re-implement all mixins

###  KR: Migrate frontend to client models and dependency injection.

client models will centralize state-management, making the UI more
dependable. Dependency injection avoids global variables, enabling
multiple changes on a single page


# Q3 2021

## O: Gerrit users' data and code are well protected and secure

{'fraction_non_alphanumeric': 0.06356126663607159, 'fraction_numerical': 0.008260670032124828, 'mean_word_length': 4.496847414880202, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '782085', 'n_tokens_mistral': 1260, 'n_tokens_neox': 1142, 'n_words': 604}