Epic: GitHub "Governance" Processes

[loujaybee]

An issue to help improve visibility on how GitHub issues are triaged, how roadmapping works, how labels are applied etc. Please use this issue to share thoughts and suggestions on how we can improve the GitHub contributing experience.

Challenges

• How do we ensure that we're not only replying to issues when they first arrive, but ensure we follow up when the action is on Gitpodders.
• How do we effectively engage with the community, without the teams spending hours doing GitHub admin.
• How do we triage into each team, but ensure that each issue has a team assigned and that it's acknowledged by the team?
• How do we ensure that issues are acknowledged, but also followed up on? Could we have a label to address impact / severity to help with triage processes?
• Another challenge, how do we answer questions like: "how can a customer see what work Gitpod is doing towards security and compliance?"

Suggested ideas/thoughts

• Add a channel on Discord to "bump" issues for update
• Improve automation on issues without teams labels
• Clarify process of triage/assignment to teams (e.g. front)
• Clarify role of certain issue labels, such as priority: highest
• Clarification on expectations on how long to receive responses on issues, what to do if there is no response, etc.
• How to understand when issues might get picked up/completed.
• Clarification on how issues relate to roadmaps
• Clarification on team boards, how to read them, and how they work

Relates to contributor experience epic: #6466

[loujaybee]

I'm hoping that this small docs clarification #8120 and a full commitment to the inbox process for teams should be sufficient here. I think we also need to ensure that all folks doing issue triage also fully utilise the inbox process and that becomes the one and only way of ensuring an official update to any issue.