Make every development team triage 10 issues/MRs a week
I mentioned this at https://gitlab.com/gitlab-org/quality/team-tasks/issues/12#note_72619087
Maybe this shouldn't be a rotation, as rotation would require scheduling with people, which has some cost. Maybe it should just be a very small requirement for developers?
For example, suppose every developers triage 5 or 10 items (be issues or MRs) per week, that would be a lot in sum but not so many for each one. This week I've done 31 items (not including the last day) for the comparison.
I see that we're also trying to add issue triage into Reaction Rotation at gitlab-com/www-gitlab-com#2152 (closed) but I feel we could go with both. For Reaction Rotation we could go as deep as the issue description says, but I think some of the issues or merge requests, the most important thing is adding correct labels and pinging the right people.
Just adding labels and pinging people don't really take a lot of time, and it's going to be a very heavy (and annoying) work if we put this onto one person.
Before we allow non-members to add labels, and ping someone according to the labels automatically, I think we still need some people to do it.
@meks @markglenfletcher @rymai What do you think? I am not sure how to enforce/remind people this, but I feel this is the only way to scale up before we have automation for this.