[Discovery] [Maintainership] Draft github issue triage process

[robrap]

Note: Devstack should have already been handled in this other ticket: TBD

AC:

• Draft and trial a new process based on answering questions.
• Ticket any automation work required.

Questions:

• Should the whole team or on-call do initial triage?
• How are tickets triaged? Labels? Project custom fields? Other?
• Can we draft a runbook?
• Do we want automation to move tickets to our board?
  • See [Discovery] [Maintainership] Draft github issue triage process #291 (comment)
• Do we need a separate process for catching up vs new issues? Can we put new issues through the process while still not being caught up, in order to keep the problem from growing once we have a process?

[robrap]

Note: We'll probably want to share with fed-bom and arbi-bom at a minimum, and may want to share more widely.

[rgraber]

This was the ticket, but options weren't documented on it: #184. The documentation ended up here: https://openedx.atlassian.net/wiki/spaces/AC/pages/3710451733/How+to+have+issues+and+pull+requests+added+to+GitHub+Projects

[robrap]

@dianakhuang: When you break out the devstack triage into a different ticket, can you provide a link in this one? Also note Becca's comment above, which may help in choosing how to implement for devstack.