no way to organise/categorise merge proposals

[Jamu Kakar]

Something we've been dealing with recently is bringing new people into
our team. We'd like to get them involved in reviews, since it's a
good way to explore the codebase and have conversations about the
activities that are going on. Something that comes up regularly in
this kind of situation is that the newcomers don't really know which
reviews they should look at. Despite suggestions that they should
just pick something, and that it's okay to do a review that involves
more questions than assertions about the code, people tend to be a bit
shy.

It'd be nice if we could tag merge proposals. This would make it
possible to add an 'easy' tag to merge proposals that are well suited
to newcomers. I notice that there's a "review type" that maybe is for
this kind of things? Anyway, it isn't clear to me what it's for and I
can't seem to specify it when I create a merge proposal (the field is
disabled which makes me wonder why it's even there).

[Martin Pool (mbp)]

I don't know if it ought to be solved by tags, but we also have
trouble in piloting community contributions with classifying them.
There are some that don't exactly need review, but rather need help.
There are others that are waiting on the contributor to follow up, but
should be finished off if they don't do that. One way to allow
communities to make their own classifications would be through tags.
Another would be to model these states explicitly.