Metrics
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
In the interest of measuring success of KernelCI, other than tracking how often people refer to it with "Reported by" trailers in their patches, we could establish a framework for some based on KCIDB data, which would eventually lead to some insights about the potential of KernelCI tests and reports.
Perhaps we can get some inspiration from:
- https://gitlab.com/Linaro/lkft/triggers/lkft-stats
- https://stats.lkft.linaro.org/
Contributor guide
Research direction
No file, test, or entry point is named. Start by reviewing how the dashboard accesses KCIDB data and the linked LKFT stats examples; done would require an agreed metrics framework and a defined way to expose the resulting KernelCI insights.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100