GitHub issues

While the primary focus of the GitHub issues is to keep a live product backlog.

Maintainers accept support questions on GitHub as new issues if they can be turned into product improvements. In this case, we add the support: question labels on the GitHub issue.

Support - Tier 1

This is about routing the incoming new community issues and PRs to the right person in our team. It’s about not notifying everybody but giving ownership to individuals: ‣.

KPIs for success:

To help with **[Responsible: React Community Engineer of the team + Engineers](https://mui-org.notion.site/Responsible-of-the-team-Engineers-4bf1e9e750b84527bafd610a203603c4) (0 GitHub issues/PRs with no labels)
- Issues without labels: 0 https://tools-public.mui.com/prod/pages/3eVYIR_
- PRs without labels: 0 https://tools-public.mui.com/prod/pages/tn213hge
To help with [Responsible: React Community Engineer of the team + Engineers](https://mui-org.notion.site/Responsible-of-the-team-Engineers-adae6dc666ca4a58ab3fff3bddda9f06) (0 GitHub issues: "status: waiting for maintainer" label)
- Issues without product scope label: 0 https://tools-public.mui.com/prod/pages/y923hoo
- ”status: waiting for maintainer” issues without assignee: 0 https://tools-public.mui.com/prod/pages/hl63hwf
To help with Community: unique contributors per month 📊 (Community: unique contributors per month) This number is a bit unclear, since it i\ncludes a lot of open PRs that come from the renovate bot and are outdated.
- Open PRs without reviewers: 35 https://tools-public.mui.com/prod/pages/1t353h04

Issue status

See how the state of the GitHub issue matches with ‣ shared terminology:

New.
Open. Have the label status: waiting for maintainer until the issue is categorized
Pending. We use the label status: waiting for author
On-hold. There is no specific handling, no label.
Solved. The issue is closed.
Closed. We rarely lock issues, but sometimes we do when the community needs to be directed to a different place.

Automation

https://github.com/mui/material-ui/blob/master/.github/workflows/ensure-triage-label.yml automates the transition from New to Open. It adds the right label to new issues if the developer bypasses the issue template