Bringing on a co-maintainer

As I'm returning from PyCon I'm realizing I've done a pretty bad job maintaining this project when there's clearly demand and interest.

Right now I don't have the time and mental energy to support this project as much as I'd like to (realpython.com keeps me plenty busy.)

So I'm looking to bring on one or more co-maintainers that can help me respond to open issues and PRs, and to help take this project into a sensible direction.

I've always believed that the main value of Schedule is simplicity. I'm looking for someone who gets that. I don't want to try to include everything and the kitchen sink into this project, and that's why I've resisted adding features like job persistence and so on (also, the PRs that proposed it so far have included shitty / fundamentally broken implementations.)

The biggest danger I see to this project is turning it into a sprawling sea of half-assed features. I'm totally fine with pointing people to `cron` or `APScheduler` if it fits their needs better.

The person(s) I'm looking to bring on as a co-maintainer should be experienced enough to understand that. It also helps if you've been burned by overwhelming emerging complexity in your own projects ;-)

Start by reviewing the repository's open issues and pull requests to understand the maintenance backlog and the project's current direction. Compare proposed work with the stated goal of keeping Schedule simple rather than adding broad feature sets. Done would mean establishing a co-maintainer relationship and taking responsibility for ongoing issue and PR support.

Written by the indexing model from the issue text.