Rename "health" references in code and HTML to neutral "activity trends" language
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, javascript, python
- Domain
- full-stack
Research direction
Start with health.py and its compute_project_health() function, then trace the related references in site/index.html and site/project.html. Rename the writer, HTML IDs and classes, JavaScript variables, and project_health.json consistently; done means the Python writer and HTML fetchers use the new activity-trends names without remaining health references.
Written by the indexing model from the issue text.
Description
The docs and user-visible HTML headings have been updated to use "Activity Trends" instead of "Health" — the word "health" implies a judgment call, but we're just measuring metrics and trends.
However, there are still internal references to "health" in:
Python code
health.pyfilename and modulecompute_project_health()function name- Output file:
project_health.json
HTML/JS (element IDs and variable names)
site/index.html: element IDs likehealth-title,health-window,health-methodology,health-method-detail, CSS classes likehealth-ml-header,health-git-headersite/index.html: JS variableshealthData,healthResp,healthErr, functionfillHealthTable()site/project.html: fetchesdata/_cache/project_health.json
Proposed renames
health.py→trends.py(oractivity_trends.py)compute_project_health()→compute_activity_trends()project_health.json→activity_trends.json(needs coordinated update in HTML fetchers)- HTML element IDs:
health-*→trends-* - JS variables:
healthData→trendData, etc.
This is a coordinated rename — the JSON filename change means both the Python writer and the JS readers need to update together.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 19h 14m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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 apache/comdev-metrics
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
apache/comdev-metrics#8 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/comdev-metrics#7 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/comdev-metrics#4 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
apache/comdev-metrics#1 · 2 comments ·
All issues in apache/comdev-metrics
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100