[core] no-response workflow - Next steps

[michelengelen]

• 1. Delete the needs triage label for MUI X: https://github.com/mui/mui-x/labels?q=need+triage
• 2. Update the needs triage KPI in for the whole org https://www.notion.so/mui-org/KPIs-1ce9658b85ce4628a2a2ed2ae74ff69c?pvs=4#c0c162d3503649c89b3ea97d8eb86c62
• 3. Fix the Toolpad apps Greg uses to do the first tier level supports that relies on this label https://www.notion.so/mui-org/GitHub-community-issues-PRs-Tier-1-12a84fdf50e44595afc55343dac00fca.
• 4. Update https://github.com/mui/material-ui, https://github.com/mui/mui-toolpad, https://github.com/mui/mui-private, https://github.com/mui/mui-public, https://github.com/mui/mui-design-kits to reflect this new workflow for the whole organization
• 5. Update notion about the renamed "needs triage" label, in https://www.notion.so/mui-org/Technical-support-80c9c7e0af614af68c1abb7120f634c8?pvs=4#ade93334755f49a58c51c2d2399eaf05, https://www.notion.so/mui-org/GitHub-labels-af1ef18d3f534f1dbc086aac87b819e8?p=1d641537fe044358b455837cba97031f&pm=s, etc.
• 6. Maybe? Document the support state machine that we have in place in https://www.notion.so/mui-org/Technical-support-80c9c7e0af614af68c1abb7120f634c8, like we have in https://www.notion.so/mui-org/Zendesk-de8ec63e1209475e8540dd5bb3097943
• 7. Update https://github.com/mui/material-ui, https://github.com/mui/mui-toolpad, https://github.com/mui/mui-private, https://github.com/mui/mui-public, https://github.com/mui/mui-design-kits with the new GitHub issue template

Additional (nit) tasks discovered:

• Update query, naming and title for this page in toolpad
• clean PRs without reviewers (especially all those bump PRs that haven't been merged)

Originally posted by @oliviertassinari in #10491 (comment)

Search keywords:

[oliviertassinari]

On 2. This would solve cases like #10967 where the status: needs triage comes back to MUI X from Material UI:

[oliviertassinari]

On 4. also applies to transferred issues, the bot struggles:

[michelengelen]

@oliviertassinari I guess we can move on with this. I haven't heard of any complains so far. Do you agree?

[oliviertassinari]

@michelengelen Let's go 🚀

[MBilalShafi]

There's a small complaint regarding the waiting for maintainer tag being added when the ticket author does a comment and close instead of only doing a comment (in this case the added tag doesn't make sense). It was reported by @LukasTy (example issue: #10657). Though IMO it's an edge case and not a blocker to move forward.

I'll make sure to update the action accordingly and update ASAP, @michelengelen maybe I can also take care of updating the workflow in other repos (point no. 4) afterward unless you already started doing so?

[michelengelen]

@MBilalShafi I was about to be handling this today, but when you are changing the workflow anyways feel free to handle the other repos as well.

I can take over again after the change has been applied then.

point 3. from the description above is already done, but only awaits an approval in mui/mui-public#136

[michelengelen]

@MBilalShafi thanks for taking care of the changes in the other repos! Much appreciated! 🙇🏼

[MBilalShafi]

You are welcome @michelengelen, thank you too for waiting for the change I had to make in the workflow. 🙏

The Point no 4 is merged to mui-x, material-ui, and mui-toolpad. For mui-public, mui-design-kits, and mui-private, the PRs are ready and have approval too, though I am not sure if it's fine to merge the PRs right now or if we should wait for another approval. Feel free to take over the merging, and taking over the issue on the next points.

[oliviertassinari]

I did an attempt as 6 in https://www.notion.so/mui-org/Technical-support-80c9c7e0af614af68c1abb7120f634c8.

[michelengelen]

@oliviertassinari nice one! Wanted to ask you what exactly you were expecting with that point to add it later. Thanks for picking this up!

[michelengelen]

All tasks done now! Thanks everyone!

[oliviertassinari]

I forgot mui-design-kits, fixed in: mui/mui-design-kits@db7ad44.