Refine kwalitee/ dashboard requirement and query the need of IMPL projects

[krvoigt]

We need to understand what the exact requirement is that kwalitee was ment as a solution for. What is the need?

• [ ] understand the requirement and solution
• [ ] prepare feature list
• [ ] consider whether it is an nice to have or if it belongs to the mvp
• [ ] ask the impl projects if kwalitee is useful

[paulpestov]

Short summary of ideas so far: It seems like there are two main uses cases for such a tool.

Monitoring This would extend the current existing draft of kwalitee which reads several status infos from repositories. Additionally this could be a place to output benchmarking results and compare those.

Configuring workflows Interactively guide users to create workflows upon their needs, informing about possibilies

Since the latter sounds quite ambitious and may require more resources we should focus for now on the first use case as most backend related topics are already solved. A frontend overhaul and some backend optimizations could create a first release increment.