Is your feature request related to a problem? Please describe
During the weekly operations meeting, there has been an ongoing question- how do we know if we are on track or not? Using release issues is focused on individual releases and there can be as many as 3 active release actions happening at once. Getting a good 'feel' for the project health doesn't have strong mechanisms
Describe the solution you'd like
There should be a place where the OpenSearch project can visualize projects and critical metrics about them. Number of stale issues/PRs. How many issues are untriaged. How many outstanding release specific issues are still unresolved.
Additional health metrics could include community engagement, incoming issue rate, or time since last release.
Is your feature request related to a problem? Please describe
During the weekly operations meeting, there has been an ongoing question- how do we know if we are on track or not? Using release issues is focused on individual releases and there can be as many as 3 active release actions happening at once. Getting a good 'feel' for the project health doesn't have strong mechanisms
Describe the solution you'd like
There should be a place where the OpenSearch project can visualize projects and critical metrics about them. Number of stale issues/PRs. How many issues are untriaged. How many outstanding release specific issues are still unresolved.
Additional health metrics could include community engagement, incoming issue rate, or time since last release.