Add "Authorized to Open PRs" information to AirTable

[jmunroe]

We need a list of the users/hub administrators who are authorized to open PRs against the 2i2c infrastructure repo. This is similar to the already existing 'Authorized Technical Contacts' that we maintain in AirTable for submitting FreshDesk tickets.

Tasks

Beta Give feedback

1. Create entries in AirTable for github user names
2. Add github user names to Authortized Technical Contacts airtable interface
3. Follow up on https://2i2c.freshdesk.com/a/tickets/1371 (motivating ticket)
4. Communicate this information back to Engineering

(Issue originated on internal 2i2c slack: https://2i2c.slack.com/archives/C028WU9PFBN/p1710943211509839)

[yuvipanda]

We should also add a bunch of people for the NASA VEDA hubs (nasa-veda, ghg, esdis): @batpad @freitagb @slesaad @wildintellect

[jmunroe]

There now an AirTable interface available for GitHub IDs who are authorized to submit PRs against specific communities:

https://airtable.com/appbjBTRIbgRiElkr/pagIiRawilmebyHbQ

Likewise, our list of communities has a new field that lists GitHub IDs for which PRs are authorized:

https://airtable.com/appbjBTRIbgRiElkr/pagog9egWRpeLyLGW

PRs are authorized at the level of 'Community' rather than a specific hub. I am making the assumption that if someone is allowed to submit PRs for one hub in a community, it would be acceptable for them to submit PRs for any hub associated with that community.

To add an 'Authorized PR Submitter' to a community, that individual first need to exist in our table of 'Contacts' and have the Github ID filled in. From their either a Community Partner can be added that to contact. Or, an Authorized PR submitter can be added to the Community Partner. Either method is acceptable.

To complete this issue, this still needs to be documented in Team Compass.

[yuvipanda]

I opened #3912 to track the documentation needed here. I don't think you need to fill out all the docs @jmunroe. I think next steps are for you to create a page in team-compass just documenting the airtable and work you've done, and the rest of the sections can be filled out later by engineering.

Thank you for working on this!

[jmunroe]

That works! I'll write something and place it in #3912 which will allow be to close this issue.

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.