kraken-devtools has a great plugin architecture. A lot of the issues and PRs are related to changing the built-in plug-ins specifically, as opposed to any changes or issues with the core functionality. As such, it would make sense to externalize the plugins and only focus on core functionality issues in this repository.
Things on the way to making this a reality:
create repos/modules for each existing built-in plugin
establish both a naming convention and a test approach to use in external modules
create a list of available plugins and maintain it in this repo's wiki or TBD
kraken-devtools has a great plugin architecture. A lot of the issues and PRs are related to changing the built-in plug-ins specifically, as opposed to any changes or issues with the core functionality. As such, it would make sense to externalize the plugins and only focus on core functionality issues in this repository.
Things on the way to making this a reality: