When triaging web issues follow the following process:

• Make sure there are no unassigned P0 and P1 issues.
• Make sure there are no P1 issues outside the backlog.
• Make sure there are no P3 issues in the backlog.
• Make sure all assigned issues are either P0 or P1 (if you‘d like to become a regular Flutter Web contributor, please ping yjbanov on Discord to be added to this list, and we’ll watch that your issues are properly triaged):
  • harryterkelsen
  • kevmoo
  • mdebbar
  • yjbanov
  • flutter-zl
• All P0 issues are assigned and being worked on.
• The list of P1 issues should be manageable (<30 issues)
• Number of open PRs should be manageable (<15):
  • flutter/flutter
  • flutter/packages
    • Remove the triage-web label when the PR is approved.
    • If you are the last reviewer, add the autosubmit label.
• Triage untriaged issues

Additional resources

• flutter-zl/web-triage: One triager's longer-form notes on routing, priority, and labeling, with logs from past sessions.