Skip to content

About

Automation to collect Jira issues to generate the BoD reports

Resources

Security policy

Stars

3 stars

Watchers

0 watching

Forks

Repository files navigation

bod-report

Automation to collect Jira issues to generate the BoD reports

Web UI (Vite)

The static dashboard lives in web-ui/ and is deployed with GitHub Pages.

Local dev:

cd web-ui
npm install
npm run dev

Build:

cd web-ui
npm run build

For local tests, the dev server will try to load specs_20260107_182508.csv from the repo root before falling back to the deployed web-ui/public/latest.csv.

If you deploy to a custom domain, set BASE_URL=/ in the build or update web-ui/vite.config.js.

History and weekly digest

The history job of the Daily Data Fetch workflow stores one snapshot per spec per day (UTC) in the DynamoDB table adm-spec-dashboard-history (us-east-1; key spec + date, re-runs on the same day overwrite). Cancelled specs are skipped. An item with spec = "_index" lists the specs stored each day.

weekly-digest.py compares the latest snapshot with the one closest to 7 days earlier and writes web-ui/public/changes.json: changes in phase, projected quarter, ratification progress and next approval date, plus specs that appeared or disappeared. With fewer than 2 snapshots it writes an empty list and a note.

The job assumes the IAM role in the repo variable AWS_HISTORY_ROLE_ARN through GitHub OIDC. The role trusts main only and may only PutItem, BatchWriteItem, Query and GetItem on that table, so runs from other branches skip the history. Local run (with AWS credentials):

python snapshot-history.py web-ui/public/latest.csv
python weekly-digest.py --out web-ui/public/changes.json

Spec activity

spec-activity.py measures how active each spec was over the last 90 days and writes web-ui/public/activity.json, shown in the Activity column. Sources: Jira (approval steps, phase changes, comments), the spec's GitHub link, mailing list messages naming its extensions (cf Extensions field), its Ratification Plan page, and PRs in riscv-arch-test, sail-riscv and riscv-unified-db. A spec developed by a TG also gets the TG's list and Confluence space. RVI staff and bots, listed in staff.json, are left out. LFX meetings are not included yet.

It needs the GROUPSIO_USER and GROUPSIO_PASSWORD repo secrets; without them the discussion counts are 0.

About

Automation to collect Jira issues to generate the BoD reports

Resources

Security policy

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages