Automated, reproducible metrics for Apache Cassandra Analytics.
Metrics for Apache Cassandra Analytics. Definitions follow CHAOSS where one exists.
CHAOSS Starter Project Health metrics model
Computed for Apache Cassandra Analytics from two venues, shown separately: GitHub PR time to first review and JIRA time to first response.
JIRA
1.4 h Aug 2026 · n=6 backfill pending
Based on: CHAOSS: Time to First Response, CHAOSS: Responsiveness practitioner guide
dev@ is shared across all Apache Cassandra subprojects. See Apache Cassandra →
Computed for Apache Cassandra Analytics from two venues, shown separately, since reviewed changes are committed via JIRA as well as GitHub: GitHub pull requests, and JIRA issues entering Patch Available (Apache Cassandra Analytics's patch-submission equivalent of a change request).
This project's existing contributor_absence_factor metric: the smallest number of contributors whose combined trailing-12-month commits reach 50% of all commits.
This project's existing release_frequency metric: count of GA releases (collectors/release.py: git tags, excluding alpha/beta/rc) in the trailing-24-month window ending each completed month.
| Line | Next targeted version | CI |
|---|
n/a n/a
Code and contributor health: sustainability, review capacity, and responsiveness.
+43 more metrics
n/a
Mailing-list metrics, computed from metadata only — never message content.
Mailing-list metrics are shared across all Apache Cassandra subprojects — see Apache Cassandra's Conversations page.
Per-commit facts from the public record — reviewers, CI evidence, checkstyle.
Governance compliance tracking and the ASF PMC roster are maintained once for the whole Apache Cassandra project — see Apache Cassandra's Governance page.