Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Rename "health" references in code and HTML to neutral "activity trends" language

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement

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.py filename and module
  • compute_project_health() function name
  • Output file: project_health.json
HTML/JS (element IDs and variable names)
  • site/index.html: element IDs like health-title, health-window, health-methodology, health-method-detail, CSS classes like health-ml-header, health-git-header
  • site/index.html: JS variables healthData, healthResp, healthErr, function fillHealthTable()
  • site/project.html: fetches data/_cache/project_health.json
Proposed renames
  • health.pytrends.py (or activity_trends.py)
  • compute_project_health()compute_activity_trends()
  • project_health.jsonactivity_trends.json (needs coordinated update in HTML fetchers)
  • HTML element IDs: health-*trends-*
  • JS variables: healthDatatrendData, 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/comdev-metrics

All issues in apache/comdev-metrics

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.