Include recent stats on the stats dashboard for all plugins
marccampbell opened this issue · 8 comments
The stats site is super interesting and helpful, thanks for creating and sharing this data publicly.
Is it be possible to include a graph and stats for the plugin ecosystem that show trends and recency? Currently, all I can find is total download counts, but I think it would be useful to include a "number of downloads in the past (week/month)" column or way to sort the ecosystem this way too?
Ideally if there's a GitHub app that tracks that over time, it would be the best.
We track historical download stats for the Krew itself. I am not sure if the approach would scale well to hundreds of repos (given underlying repos change names etc).
Let's discuss.
If I understand correctly, you are looking for a moving average similar to what brew does. The data for that should be there, it's only a question how easy it is to make the respective graphs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
@marccampbell are you still interested in this functionality? Otherwise we should close this issue.
@corneliusweig I do still like this and think it would be useful. If it's something I can contribute and agreeable, I'm happy to take this issue.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-contributor-experience at kubernetes/community.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.