Document code review tips/guidelines

We have a barebones ["code review process" section](https://github.com/roostorg/.github/blob/main/CONTRIBUTING.md#code-review-process) in our CONTRIBUTING.md, but I think we could expand this to explain a bit more about the purpose and norms of code review for ROOST projects.

Relevant prior art:

- GNOME [Change Submission](https://handbook.gnome.org/development/change-submission.html) docs
- The Open Source Way: [From Users to Contributors](https://guidebook.theopensourceway.org/growing-contributors/from-users-to-contributors)
- elementary Contributor Guide: [Reviewing Code](https://docs.elementary.io/contributor-guide/development/reviewing-code)

Navigation Menu

Uh oh!

Document code review tips/guidelines #89

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Uh oh!

Document code review tips/guidelines #89

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions