How can BOM squads get proper access to all repos?

[rgraber]

While doing some DEPR work, I ran into the following two issues:

openedx/edx-notes-api#350

• Required approval from openedx/content-aurora
  feat: remove JWT_AUTH_REFRESH_COOKIE depr190 openedx/enterprise-access#294
• The base branch restricts merging to authorized users.

Note that another enterprise repo did not have this issue.

Questions:

• Would the owners refuse to provide more access to BOM squads, or does this just require tuning github settings?
• Do we have recommendations for how to best tune the settings for our teams?
• If we won't get more access, what is the simplest process for getting our needs met?
  • It is probably to follow the Maintenance Board GitHub Project process, but that feels like a lot of work, especially for one-line PRs.
  • I wonder if more of the Maintenance Board Github process could be automated, so that you could add a unified label (e.g. “needs maintainer attention”) and maybe a comment about what is needed, and the rest of the fields could be filled in automatically, so no one has to lookup the owner of each repo (as an example).

Next step:
Move relevant details into edx/open-source-process-wg#129

[robrap]

I loved the relevant information to edx/open-source-process-wg#129 (comment). I guess I'll close this ticket.