[RFC] Formally track aspiring approvers as reviewers

Author: rkoster

toc/rfc/rfc-formal-aspiring-approvers-as-reviewers.md

@@ -0,0 +1,31 @@
+# Meta
+[meta]: #meta
+- Name: Formally track aspiring approvers as reviewers
+- Start Date: 2022-07-05
+- Author(s): @rkoster
+- Status: Draft <!-- Acceptable values: Draft, Approved, On Hold, Superseded -->
+- RFC Pull Request: https://github.com/cloudfoundry/community/pull/333
+
+
+## Summary
+
+Extend the working group yaml defenitions to optionally include a `reviewers` key with a list of contributors who like to become approvers.
+The github org automation should use this information to create a github team for the area with `-reviewers` suffix and __read__ permissions.
+
+This will later allow automatic assignment of PRs to be reviewed, which will help these contributors more easily statisfy the requirments to become approvers.
+
+## Problem
+
+Due to the way to cloudfoundy github organization is setup, contributors gain no additional access rights within the organization. 
+This prevents PRs to be assigned to them to be reviewed. 
+
+In addition, the current process for getting people approver status relies a lot on the decipline of contributors to rack up the [needed contribution points](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0006-approver-requirements.md).
+Ideally we create an opt-in low resistance path, to help contributors get to approver status quicker.
+A lack of enough approvers hinders our ability as a community to review and approve PRs in a timely manner.
+Improving the number of approvers should be the top priority of working group leads.
+
+## Proposal
+
+Allow tracking aspiring approvers as `reviewers` per working group area. Create a `*-reviewers` team per area with read access to the area's repos.
+
+