Code Review Improvements

Where we’re at:
PR process comes with approvals, organizationally enforced (not structurally enforced), on main branches.

Where I think we need to be:
Whole team needs to be proactive at code review.

Code review post-implementation (code inspections).

Ideas:
Code Review board? List PRs with description? Real or virtual.

Board should follow Google’s change lists? eng-practices/review/developer/cl-descriptions.md at master · google/eng-practices

Needs more comprehensive style guide to encourage reviews.

Ask developers to add more reviewers. <That might be a big win>

“Secondary reviewers” - please review this from lens X

Examples:

Kick-off optional code inspections? Maybe a brown-bag-lunch code review process? Choose a method or basic process and simply show the code on the main screen.