Web UI Enhancements
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
web-ui is too simple (designed for Thorsten use; no separation for interested parties to limit view to only a subset they care about, like CI systems or subsystem mainliners; distinction between rough fixes on the list, ready for review fixes, and fixes that sit in -next; ugly, …)
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.
Research direction
Start with the existing web-ui through the dashboard linked in the repository description and document its current views and limitations. Clarify which audiences, filters, fix states, and visual improvements are required before choosing an implementation path. Done should mean the agreed audience-specific views, fix-state distinctions, and appearance improvements are available in the dashboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100