Dojo to Angular: Maintenance Portlet
Open
Nobody has claimed this yet.
stale
Team : Modernization
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Rebuild the Maintenance portlet from Dojo to Angular with PrimeNG. Largest migration — 7 tabs: Cache, Index, Tools, Log Files (SSE tailing), System Info, Threads, Logged Users, and System Jobs (SSE monitoring). Mix of real-time, destructive, and diagnostic operations.
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 by locating the existing Dojo Maintenance portlet and the Angular/PrimeNG portlet patterns in the repository. Map the Cache, Index, Tools, Log Files, System Info, Threads, Logged Users, and System Jobs areas, including SSE tailing or monitoring and destructive or diagnostic operations. Done means the Maintenance portlet has been rebuilt in Angular with all listed areas covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100