This discussion is around defining the requirements for a dashboard for tracking the health of the repository. Here is a list of questions we want to answer with the dashboard and proposals for charts that would help with it.

1. Is the number of newly created issues growing over time?

• How to get the information: Line chart - number of new issues per day over time
• What we will gain: We will see trends of when the number of new issues increases/decreases. Is the number of new issues per day growing over time

2. How fast are we handling issues/Are there enough resources for it?

• How to get the information? Line Chart - number of open issues per date
• What we will gain? We will see trends of growing issues over time/whether we need to increase the time spend for handling issues.

3. Which areas of the codebase need improvements?

• How to get the information? Pie Chart - number of open issues per label that contain thebug label
• What we will gain? We will see which areas of the codebase have the biggest number of bugs reported so far.

4. Which areas of the codebase need better documentation?

• How to get the information? Pie Chart - number of issues per label that contain thesupport label
• What we will gain? We will see which areas of the codebase have the biggest number of support requests so far, which should indicate that we need better documentation for them.

Feel free to leave more suggestions below.