Add a section for becoming a maintainer.

[Ivorforce]

Maintainer tasks (pr reviews, responsive bug fixing, code ownership, critical evaluation of proposals) are still a major bottleneck.
As such, the main priority of the PR isn't actually to recruit people to become maintainers, but to further crowd-source the jobs usually done by maintainers.

This can mean people taking on these tasks in a casual manner; e.g. becoming very specialized code owners or prolific reviewers. If it means someone becomes reliable and active enough to become a maintainer, that's a plus!

[AThousandShips]

I think this is a good addition! Will take a look tomorrow in depth but at a glance it looks good

We might also want to emphasize that becoming a maintainer isn't an achievement or something people should strive for in its own right, will think of some ways to convey that, but I think it's important to dispel the idea that becoming a maintainer is some "achievement" or prestige position, and that it's more of a position of responsibility rather than privilege, that being one "just" means (it's not "just" but you get what I mean) that you are a trusted contributor with expertise in an area and that is responsible for that area

[Ivorforce]

We might also want to emphasize that becoming a maintainer isn't an achievement or something people should strive for in its own right, will think of some ways to convey that, but I think it's important to dispel the idea that becoming a maintainer is some "achievement" or prestige position, and that it's more of a position of responsibility rather than privilege, that being one "just" means (it's not "just" but you get what I mean) that you are a trusted contributor with expertise in an area and that is responsible for that area

Very good point. I'll see how I can put that into the PR.