Maintenance Czarring

For background, a group of people working at various companies donate 20-25% of their time to maintain the various Dask issue trackers Each Tuesday, one of those ~suckers~ contributors volunteers to be the "maintenance czar" who is in principle responsible for making sure that things run smoothly. This involves ...

1. Handling new issues
2. Being first reviewer on new PRs
3. Being kind and welcoming, while also firmly directing novices towards time-efficient behavior
4. Making sure that existing issues and PRs progress to a done state
5. Corralling other maintainers as necessary, but not depending entirely on them

It's an intense and time consuming job, even when you know what you're doing. And it's actually pretty hard to know what you're doing because this jobs requires a broad set of technical and social expertise:

1. Moderate understanding of the Dask project
2. Broad (but not deep) understanding of all of the PyData stack (numpy, pandas, scikit-learn, jupyter) as well as other technologies like AWS, kubernetes, HPC deployments, SSL, and so on.
3. Social and interpersonal skills to handle people in an efficient but sensitive manner
4. Organizational skills to not let things get left behind, and to stay responsive to dozens of simultaneous conversations

Being Czar builds these skills, but it's painful to start, both for the czar, and for the community, who probably gets sub-optimal response that week.

Recently (maybe because of at-home quarantine?) we have a growth in both demand and supply.

1. There seems to be an increase in issues and PRs
2. We have more ~suckers~ contributors donating their time

As a result Czarring has become more intense (at least for me). I would like to suggest that we start co-czarring, intentionally combining someone who is familiar with this task, and someone who is new. I also think that we should figure out a steady practice (daily video checkins?) that they do together to be productive both in handling the inbox, and also in knowledge transfer.

cc @TomAugspurger @jrbourbeau @quasiben @jsignell @jjhelmus @gforsyth @martindurant @jacobtomlinson @jcrist