Improve dashboard reliability and development procedures
@nuclearcat is already working on this.
Since Sep 17, 2026.
Assessment
This issue has not been assessed yet.
Description
This is actionable items for sysadmin team:
- Dashboard submissions should be backed up at earliest stage.
- Dashboard team need full visibility and monitoring of ingestion stage, same as dashboard stage
- Introduce consistency monitoring action at kernelci-pipeline for dashboard team.
- Setup mandatory independent review of ingester deployment
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kernelci/dashboard
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 64/100
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in kernelci/dashboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100