project health - its time to fix, archive, or fork.

as this point the time commit to chalice appears to be closer to 1 hr every few month of maintainer time, at which point it does seems worthwhile to raise archiving the project to prevent more pain to innocent adopters. alternatively given aws doesn't allow external contributors/maintainers on repos in its org, an actual community fork, that doesn't have to be limited to 1hr of attention every few months. either way.. the current situation is pretty sad. I doubt the time commit is getting better, so archive or let's encourage a fork that can leverage the extant community of adopters.

This issue is a project-health discussion rather than a scoped code task. Start by reviewing the 24-comment thread and the repository status; done would require a maintainer decision to archive Chalice or encourage a community fork.

Written by the indexing model from the issue text.