First of all, thanks for trusting this project and for all the contributions you have made. I apologize if I haven't been the most diligent dealing with open PRs and Issues, and as such I want to consult with the community what they think should be the objective for a next major release.

Based on my own ideas and what I've seen in the Issue tracker I think the requirements are the following:

• Remove support for Python 2 and Python 3.4 or earlier, as those versions are no longer supported.
• Remove included git hooks, as these are not platform agnostic.
• Remove default configuration and bundled linters. Static analysis is thankfully evolving quite fast, so providing and maintaining an up-to date and comprehensive list of linters, is much more work that a single person could handle. Also, it makes the testing much slower and fragile, as dependencies are usually changing. The idea would be to have a wiki with user contributed recipes. Or alternatively a way of pulling recipes from github. Something like git-lint-configure @sk-/git-lint-pylint @user/git-lint-eslint.
• Add types to codebase.
• Improve cache management. Detect when config changed, and allow to skip the cache.
• Improve command line. Better options and documentation flags, plain output for CI, etc.
• Improve calling api, so that it's easier to integrate with CI systems.
• Provide base Github action. One would need to extend it to install the linters used in the project Would it be possible to create a GitHub Action for git-lint? #139
• Change the config declaration file. I find yaml to be quite inadequate for this purposes as ones needs to escape some characters and multiline support is not the best.

Let me know what you think and how you are using the project.