Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Extend Commit Activity Stats Timeframe Without Overloading Dashboard #58

Open
onlydole opened this issue Mar 25, 2023 · 2 comments
Assignees
Labels

Comments

@onlydole
Copy link
Member

Issue Description

https://all.devstats.cncf.io/d/53/projects-health-table?orgId=1

The current commit activity display compares commits in the last (n) months to the previous (n) months. This statistic is valuable for understanding trends in commit activity over time. However, extending this timeframe to cover a more extended period without overloading the dashboard would be beneficial.

Proposed Solution

  1. Implement a feature that allows users to select custom timeframes for commit activity comparison (e.g., last six months vs. previous six months, last 12 months vs. previous 12 months, etc.).
  2. Ensure that the extended commit activity stats do not clutter or overload the dashboard by optimizing the display or providing options for users to toggle between different timeframes.

Benefits

  • Provides users with more in-depth insights into commit activity trends.
  • Enables users to analyze commit activity over custom timeframes.
  • Maintains a clean and user-friendly dashboard while adding more detailed statistics.
@onlydole onlydole added the enhancement New feature or request label Apr 7, 2023
@tegioz
Copy link

tegioz commented Jan 18, 2024

Hi!

Should we transfer this issue to cncf/devstats?

/cc @lukaszgryglicki

@tegioz tegioz transferred this issue from cncf/landscape Apr 5, 2024
@lukaszgryglicki
Copy link
Member

We cannot support arbitrary "custom time range" we are pre-computing selected set of metrics and then UI only selects from already calculated values, we can eventually add a new set of possible selections - you would need to list them and eventually add a drop down allowing you to select one of them while hiding other ones. We need to keep this behaviour (pre-calculating all, not computing anyting on the fly from the raw data) to keep DevStats fast.

Also this kind of modification needs approval from @caniszczyk including approval of additional time-ranges and approach with drop-down to allow choosing which one should be displayed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants