In order to make the new robot better support the code review process, we recommend adding the OWNERS file.
OWNERS files are used to specify responsibilities for different parts of the code base. Use them to assign the reviewer and approver roles used in our two-phase code review process.

The velocity of a project that uses code review is limited by the number of people capable of reviewing code. The quality of a person's code review is limited by their familiarity with the code under review. Our goal is to address both of these concerns through the prudent use and maintenance of OWNERS files.

OWNERS files are in YAML format and support the following keys:

• approvers: a list of gitee usernames or aliases that can /approve a PR
• reviewers: a list of gitee usernames or aliases that are good candidates to /lgtm a PR
• options: a map of options for how to interpret this OWNERS file, currently only one:
  • no_parent_owners: defaults to false if not present; if true, exclude parent OWNERS files. Allows the use case where a/deep/nested/OWNERS file prevents a/OWNERS file from having any effect on a/deep/nested/bit/of/code

The above keys constitute a simple OWNERS configuration.

A typical OWNERS file looks like:

approvers:
  - alice
  - bob    
reviewers:
  - carol  

OWNERS files should be regularly maintained.
We should strive to:

• grow the number of OWNERS files
• add new people to OWNERS files
• ensure OWNERS files only contain organization members
• ensure OWNERS files only contain people are actively contributing to or reviewing the code they own
• remove inactive people from OWNERS files