Document how 2i2c engineers should respond to PRs opened by community representatives

[yuvipanda]

Context

We currently get PRs opened on this repo by community representatives, but don't really have any written guidelines about how 2i2c engineers should respond to them.

Proposal

We should have guidelines for:

• Who is authorized to open PRs for a community?
• What kinda PRs can be immediately merged by any 2i2c engineer?
• What's the process for prioritizing more complex PRs?

Updates and actions

No response

[jmunroe]

Here's some copy to be reworked and placed in the appropriate section of either team-compass or the infrastructure guide:

Authorized PR Submitters

Some communities are authorized to submit PRs directly against our infrastructure repository for configuration files related to specific clusters/hubs.

Look up Authorized PR Submitter

We record which hubs specific individuals are authorized to submit PRs against in this Authorized PR Submitters AirTable interface. Information about the who is Authorized PR Submitter is also available from this Communities interface.

Update Authorized PR Submitter

To add a new 'Authorized PR Submitter' to a community, that individual first needs to exist in the Contacts table and have a Github ID filled in. Then, by selecting record for that contact, a Community Partner can be added can be added under the 'Authorized PR Submitter' field. Alternatively, the new Authorized PR Submitter can to a record in the Communities table . Either method is acceptable.