Batchspawner maintenance?

Hi,

I'm wondering if we could discuss how to make sure that batchspawner is maintained in the future. Currently, there are lots of PRs open that need review, and it seems that development waits until I make a personal integration branch and that gets merged at once. Without an updated master, it's hard to have a dev target.

We've got different people making pull requests. If we could have someone from the JupyterHub organization watching and reviewing, we could probably make better progress. They don't have to be experts in batch systems themselves (I and others who are commenting here can do that, plus no one knows all the batch systems), but someone with good knowledge of JH would be able to give us the most important feedback, merge, and keep things going.

For my part, I've spent enough time that I can give a good first review, but things that involve JupyterHub internals definitely need more eyes on it. My next development push will probably be within a few weeks, so having some way to progress then would be good.

Does anyone (especially from jupyterhub) have any comments?